On 18/12/13 08:45, Michael Calmer wrote:
Hi,
Am Mittwoch, 18. Dezember 2013, 08:16:40 schrieb Balint Szigeti:
Hello
I think, in the next or future release the Requiring Reboot should be
carried out an SQL query which examine the actual kernel.
I mean, the box was updated by Spacwalk, but restarted by hand.
The rhn client should refresh its data in SQL DB it uses the newest
kernel and therefore it shouldn't appear under the Requiring Reboot.
What do you guys think?
For me, the rebooted machine appearing under 'Requiring Reboot' is
disturbing.
I don't want to restart the machines with Spacewalk system again.
Does anybody know a workaround?
First try to run rhn_check after the reboot on the client.
This command updates the data on the spacewalk server including the uptime.
The problem: with rhnsd this is started 1-6 hours after the reboot for the
first time.
I provided a script which send the only the uptime data directly while
starting rhnsd, but this was rejected.
Another possible problem could be a timezone problem while comparing the
install date of affected packages with the uptime.
Also little differences in the time between client and server could be the
reason for your problem. Please use ntp if you are not yet doing it.
It's weird. Another machine disappeared from the list, after the
rhn_check command.....
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
