Re my 'Time problem after update?' questions - I followed the steps below
and everything's working fine now.
D
Neritan Myftiu wrote:
> Hi all,
>
> After this update I have noticed a time reference problem. Other
> things work OK so far. I'm running Nuonce-BQ 3.5, BlueQuartz
> 0.20050818, fully 'yum' updated.
>
> For whatever reason the time was reset to 6 hours earlier (from 19:xx
> to 13:xx in my server) as soon as the the update completed.
>
> I rebooted the server to be sure everything would function.
>
> Admin UI kept reverting to this 6 hours difference until I changed
> "Time Zone Settings" to another zone and reverted back to my usual
> zone.
>
> Then, 'named' would use the same different time (-6 hrs) to stamp its
> log entries - a 'service named stop/start' cycle fixed it.
>
> In /var/log/messages I got this 'strange' alternating time stamps:
>
> --
>
> Aug 31 15:19:19 frontgate cced(smd)[7060]: client [0:3085] has admin
> rights Aug 31 21:19:22 frontgate ntpd: ntpd startup succeeded
> ...
> Aug 31 21:30:52 frontgate cced(smd)[7791]: client 6:[0:7789]: SET
> succeeded Aug 31 15:31:16 frontgate cced(smd)[7836]: client
> 6:[48:7058]: SET 1 . Time "deferCommit" "=" "0"
> Aug 31 21:31:16 frontgate cced(smd)[7836]: client 6:[48:7058]: SET
> succeeded
> Aug 31 15:31:16 frontgate cced(smd)[7838]: client [0:7837] has admin
> rights Aug 31 15:31:17 frontgate cced(smd)[7839]: client [0:7837] has
> admin rights Aug 31 21:31:17 frontgate cced(smd)[7839]: client
> 6:[0:7837]: SET 1 . Time ntpAddress = "europe.pool.ntp.org"