[cobalt-users] Named update/Reboot/Logs dead/Get's me Red

[David Thurman <dthurman@xxxxxxxxxxxxxxxxxxxx>]

Hello All,
We just installed the new Named update and this required a reboot of the
server. This seems to be a constant problem with a system reboot. Our logs
now do not rotate. I noticed that the clock moves forward 2 days. I have it
set with a NTP server that is rock solid. I also noticed that the system and
hardware clocks are now off. I resynced the clocks to each other but it
would not take. I went in this morning and was able to resync the clocks to
the correct time. We have 2 Raq3's and only one of them seems to act up. The
one with the problems is a stock unit that was upgraded by Sun-Cobalt. The
other with out issues was upgraded by us. I have had Tech support from sun
in this machine before for the same reason. My question is, since I have the
clocks resynced, will the cron now catch up and rotate the logs when it
reaches Nov 16th (this is the day that was showing)

When Tech Support was in the box they stated that the Raq3's had an issue
when rebooted and the clocks not syncing. What I feel is happening is that
once the clock is wrong the cron thinks it has already ran that date (Nov
16th) I argued with the tech stating this is what I think has happened and
they said no way. Well after looking at it he stated it looks like the cron
thinks it ran. So anyone else have this happen and then waited the required
days for the system to "Catch Backup" and all work okay. I really don't want
to pay them again and then wait to be credited back, when this is an on
going problem.

--
Thank you,
David E Thurman
The Web Presence Group
309.676.5688
dthurman@xxxxxxxxxxxxxxxxxxxx
http://www.webpresencegroup.net