Its worthwhile putting a ntp sync somewhere in the post section of the kickstart... that has saved me many headaches.
spacewalk/satellite errors are in my experience not very verbal. This is a good example of where better more verbal error logging could help do more easily debug and fix problems. Regards > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:spacewalk-list- > [EMAIL PROTECTED] On Behalf Of David Nutter > Sent: 17 November 2008 11:05 > To: [email protected] > > Gerhardus, > > On Mon, 2008-11-17 at 09:41 +0000, [EMAIL PROTECTED] > travel.com > > wrote: > > > I had a similar problem which was caused by a clock difference > between > > > the spacewalk(satellite) server and the server being build. Its > probably > > > not your problem but worth while checking anyway. > > That could be an issue as though my spacewalk server knows it's x:yz > > UTC, my spacewalk appears to constantly think it's EST. I.e. my > server > > knows that it's in Brighton, but spacewalk thinks it's in San > Francisco. > > The time zone can be changed in the spacewalk web UI in the Locale > Preferences. Click "Preferences" then "Locale Preferences" in the grey > sidebar. Underneath spacewalk presumably uses UTC so a time mismatch > probably isn't the issue, assuming both your hosts are synchronizing > their clocks with NTP. > > Regards, ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
