newgentechnologies
asked on
Red hat 3.4 time is not updating
The server was setup as a NTP client, but the time would drift to over 30 seconds after about 4 minutes. So, I setup it up as a NTP server by running the following commands:
# echo -e "server 192.36.143.150\nserver 129.132.2.21\nserver 130.149.17.21" > /etc/ntp.conf
# chkconfig --level 2345 ntpd on
# service ntpd stop
# ntpdate 129.132.2.21 192.36.143.150 130.149.17.21
# service ntpd start
The time still doesn't seem to update properly. Here are some of the findings I have found from troubleshooting:
remote refid st t when poll reach delay offset jitter
==========================
192.36.143.150 .PPS. 1 u 36 64 377 178.135 -92121. 49284.3
129.132.2.21 129.132.2.22 2 u 38 64 377 215.764 -37174. 31538.9
130.149.17.21 .PPS. 1 u 39 64 377 189.214 -15835. 47743.9
[root@PEMLINMAILNFS ~]# tail -f /var/log/messages
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: ntpd 4.2.0a@1.1190-r Sun Aug 13 01:49:12 CDT 2006 (1)
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: precision = 59.000 usec
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: Listening on interface wildcard, 0.0.0.0#123
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: Listening on interface wildcard, ::#123
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: Listening on interface lo, 127.0.0.1#123
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: Listening on interface eth0, 172.24.0.35#123
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: kernel time sync status 0040
May 26 08:41:36 PEMLINMAILNFS ntpd: ntpd startup succeeded
When I ran TCPDUMP UDP PORT 123, I was seeing packets going back and forth and I have turned off the local firewall.
It looks like it it is communicating properly to the the time servers, it just is not changing the time. I only have basic knowledge of Linux, so could use some help.
# echo -e "server 192.36.143.150\nserver 129.132.2.21\nserver 130.149.17.21" > /etc/ntp.conf
# chkconfig --level 2345 ntpd on
# service ntpd stop
# ntpdate 129.132.2.21 192.36.143.150 130.149.17.21
# service ntpd start
The time still doesn't seem to update properly. Here are some of the findings I have found from troubleshooting:
remote refid st t when poll reach delay offset jitter
==========================
192.36.143.150 .PPS. 1 u 36 64 377 178.135 -92121. 49284.3
129.132.2.21 129.132.2.22 2 u 38 64 377 215.764 -37174. 31538.9
130.149.17.21 .PPS. 1 u 39 64 377 189.214 -15835. 47743.9
[root@PEMLINMAILNFS ~]# tail -f /var/log/messages
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: ntpd 4.2.0a@1.1190-r Sun Aug 13 01:49:12 CDT 2006 (1)
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: precision = 59.000 usec
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: Listening on interface wildcard, 0.0.0.0#123
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: Listening on interface wildcard, ::#123
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: Listening on interface lo, 127.0.0.1#123
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: Listening on interface eth0, 172.24.0.35#123
May 26 08:41:36 PEMLINMAILNFS ntpd[2635]: kernel time sync status 0040
May 26 08:41:36 PEMLINMAILNFS ntpd: ntpd startup succeeded
When I ran TCPDUMP UDP PORT 123, I was seeing packets going back and forth and I have turned off the local firewall.
It looks like it it is communicating properly to the the time servers, it just is not changing the time. I only have basic knowledge of Linux, so could use some help.
rindi
Change the Server's mainboard battery. If that battery is spent the time will drift.
rindi is correct, after replacing the CMOS battery, however, make sure that the BIOS time is matching with the time you are showing in Linux (replacing/reseating the CMOS battery will reset the system time). The catch 22 comes in when Linux has the ability to change the BIOS time, and the BIOS hands off the time configuration to the operating system at the boot process. If you are having issues contacting the network the system will not update the time, thus, make sure the time locally checks out before proceeding.
clock -w
or
setclock
will help you manually override the BIOS time and set it to the Linux time.
Also resetting BIOS defaults and flashing BIOS has resolved similar issues in the past for me.
Good Luck!
clock -w
or
setclock
will help you manually override the BIOS time and set it to the Linux time.
Also resetting BIOS defaults and flashing BIOS has resolved similar issues in the past for me.
Good Luck!
ASKER
Didn't mention this, but it is a Virtual machine. So may have to do with the BIOS.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.