Page 1 of 1
pcs loosing time/date
Posted: 03 Feb 2010 15:12
by mboehringer
i actually got some pcs, loosing date/time during the days; because of that the server can't switch bach @ the determined time and the gateway is lost forever without manual interaction... after correcting that item manually, this piece works fine again for weeks...
stupid IT-Stuff... ???
Posted: 04 Feb 2010 01:55
by frank
Are you using NTP ?
Are you in the same time zone of the main CPU ?
When you say you lose time during the day, does it reset to 1980 (meaning the bios is fucked up) or does it switch only hours without changing the minutes (meaning you probably have a bad setting in your time zone) ?
Posted: 04 Feb 2010 12:05
by mboehringer
the duplicated AS are running ntp-clients @ central area but the pcs are manually configured... could that be the reason for that mess? as far as i remember, the problems occured with the two (P)CS-2 @ Rel.9.0 which thought it was something like J2K... not quite sure about that as i paniced a bit during these situations...
thanks & best regards
markus
Posted: 23 Apr 2010 01:55
by frank
yeah, try to setup NTP in the PCS, this should save you.
Let us know if it works..
Posted: 29 Apr 2010 13:20
by sipmotor
Hi there,
you should use the main cpu as NTP Server for the PCS, should work fine...
but there may occure another Problem with date and time on your pcs:
If your bios time is wrong the adjtime systemprocess may have a problem. Check the System time with date and the bios time with hwclock.
If the bios time (hwclock) is wrong but System time is fine, set the bios time to system time by using
hwclock --systohc
If your bios time was wrong (normaly its 1992) you also have to check your logrotate.
Take a look at
/usr4/incid/logrotate.status
(for example with cat). If the year ist 1992, you have to edit your. logrotate.status file with vi.
Replace 1992 with any year since 2000 and it will work fine.
Check the reconfigurated logrotate with
logrotate -sd /DHS3dyn/incid/logrotate.status /DHS3data/incid/logrotate.conf
good luck
Posted: 05 May 2010 16:15
by frank
mboehringer
Did you fix it ?
Posted: 15 May 2010 10:57
by mboehringer
Hello Frank,
i was monitoring that item for a few months now and it seems that it must have been just an accidently "same time) problem with these three buds... looks, as if it was ok since weeks now.
thanks for your help mates...
best regards from germany