[ntp:questions] NTP not working after server crash

Andrew Kilham andrewkilham at iinet.net.au
Tue Aug 17 10:17:25 UTC 2010


  Hi,

I have a server running VMWare Server, which contains a number of  
virtual machines. The host VM and guest VM's are all running CentOS 5 64bit.

I installed NTP about a year ago and got it working on all of the 
virtual machines on this server, and it was working fine. However, I've 
just noticed that the time on one of my virtual servers is out, but it 
is still working fine on all of the other virtual machines.  I checked 
the NTP log file on the virtual machine that is having problems and it 
just stopped doing anything in April:

> 16 Apr 12:34:49 ntpd[680]: no servers reachable
> 16 Apr 12:43:28 ntpd[680]: synchronized to 192.168.15.1, stratum 3
> 16 Apr 12:49:45 ntpd[680]: time reset +119.777502 s
> 16 Apr 12:55:03 ntpd[680]: synchronized to 192.168.15.1, stratum 3
> 16 Apr 13:30:30 ntpd[680]: time reset -0.350146 s
> 16 Apr 13:34:54 ntpd[680]: synchronized to 192.168.15.1, stratum 3
> 16 Apr 14:39:21 ntpd[680]: no servers reachable
> 16 Apr 14:50:03 ntpd[680]: synchronized to 192.168.15.1, stratum 3
> 12 Aug 16:26:08 ntpd[2187]: ntpd exiting on signal 15
> 12 Aug 17:52:39 ntpd[2440]: ntpd exiting on signal 15
> 12 Aug 20:35:29 ntpd[3009]: ntpd exiting on signal 15

I have verified that NTP is still running, and as you can see by the 
last three lines it is still logging to the log file when I restart it. 
My memory is a little sketchy, but I believe that on April 16th (the 
date NTP stopped working on this virtual machine), VMWare crashed and I 
had to do a forced reboot of the server (along with all the VM's). I'm 
not sure how or why this would cause the problem, but I assume that it 
is related.

Here is my /etc/ntp.conf file:
> # ntpd.conf
>
> tinker panic 0
> restrict 127.0.0.1
> #restrict default notrust nomodify nopeer
> server 192.168.15.1
>
> driftfile /var/lib/ntp/drift
> logfile /var/log/ntp.log

This config file is completely identical to all of the other virtual 
machines that do work. I have verified that the file permissions on 
/var/lib/ntp/drift are correct and I have confirmed that there is no 
firewall causing problems. Running "ntpq -p" on the broken VM returns:

>      remote           refid      st t when poll reach   delay   
> offset  jitter
> ==============================================================================
>  192.168.15.1    .INIT.          16 u    -   64    0    0.000    
> 0.000   0.000

And on one of the other VM's that is working:

>      remote           refid      st t when poll reach   delay   
> offset  jitter
> ==============================================================================
> *192.168.15.1    173.201.38.85    3 u  886 1024  377    1.263   
> 28.732  57.120

I have confirmed that I can ping 192.168.15.1 (which is the internal IP 
address for the host machine) from the VM that isn't working.

Does anyone know what could be wrong?

Cheers,

Andrew





More information about the questions mailing list