Xen devel - Jan 2005 - ntpd crashing

Hello,

my NTP deamon is crashing almost every day. Any ideas how to fix this ?

Cheers
Bernhard

/var/log/ntp
=========== 5 Jan 00:54:53 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 01:30:12 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 01:54:40 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 09:10:09 ntpd[26805]: time reset -1.835962 s
 5 Jan 09:14:29 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 09:24:13 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 09:34:50 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 10:56:09 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 11:10:54 ntpd[26805]: time reset -12.880191 s
 5 Jan 11:16:13 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 11:25:55 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 11:28:04 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 11:47:19 ntpd[26805]: no servers reachable
 5 Jan 11:53:44 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 12:01:15 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 12:01:08 ntpd[26805]: time reset -6.980488 s
 5 Jan 12:06:31 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 12:33:28 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 13:32:07 ntpd[26805]: no servers reachable
 5 Jan 13:36:24 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 13:37:26 ntpd[26805]: time reset -1.176416 s
 5 Jan 13:42:47 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 13:50:18 ntpd[26805]: no servers reachable
 5 Jan 13:54:41 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 13:58:56 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 14:05:22 ntpd[26805]: time reset -2.373489 s
 5 Jan 14:09:38 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 14:32:10 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 14:42:00 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 14:58:14 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 15:01:05 ntpd[26805]: no servers reachable
 5 Jan 15:18:25 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 15:14:20 ntpd[26805]: time reset -244.633133 s
 5 Jan 15:34:43 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 15:43:20 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 15:46:07 ntpd[26805]: time reset -159.285423 s
 5 Jan 15:54:38 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 16:01:01 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 16:43:07 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 17:04:24 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 17:23:29 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 17:34:17 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 17:47:05 ntpd[26805]: time reset -0.232131 s
 5 Jan 17:53:36 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 18:04:18 ntpd[26805]: synchronized to 153.46.180.66, stratum 1
 5 Jan 18:18:15 ntpd[26805]: no servers reachable
 5 Jan 20:36:13 ntpd[26805]: synchronized to 153.46.53.58, stratum 1
 5 Jan 20:36:13 ntpd[26805]: time correction of -2577 seconds exceeds 
sanity limit (1000); set clock manually to the correct UTC time.
 5 Jan 20:20:16 ntpd[31353]: synchronized to 153.46.180.66, stratum 1
 5 Jan 20:20:16 ntpd[31353]: kernel time sync disabled 0041
 5 Jan 20:24:35 ntpd[31353]: kernel time sync enabled 0001
 5 Jan 20:37:34 ntpd[31353]: synchronized to 153.46.53.58, stratum 1
 5 Jan 20:47:15 ntpd[31353]: synchronized to 153.46.53.58, stratum 1
 5 Jan 20:54:40 ntpd[31353]: synchronized to 153.46.180.66, stratum 1
 5 Jan 21:17:15 ntpd[31353]: synchronized to 153.46.53.58, stratum 1
 5 Jan 21:19:23 ntpd[31353]: no servers reachable
 5 Jan 21:32:16 ntpd[31353]: synchronized to 153.46.180.66, stratum 1
 5 Jan 21:35:24 ntpd[31353]: time reset -6.039528 s
 5 Jan 21:39:40 ntpd[31353]: synchronized to 153.46.53.58, stratum 1
 5 Jan 21:48:18 ntpd[31353]: synchronized to 153.46.180.66, stratum 1
 5 Jan 21:54:49 ntpd[31353]: synchronized to 153.46.53.58, stratum 1
 5 Jan 22:00:04 ntpd[31353]: time reset -2.884600 s
 5 Jan 22:09:42 ntpd[31353]: synchronized to 153.46.53.58, stratum 1
 5 Jan 22:09:46 ntpd[31353]: no servers reachable
 5 Jan 22:14:06 ntpd[31353]: synchronized to 153.46.180.66, stratum 1
 5 Jan 22:15:12 ntpd[31353]: synchronized to 153.46.53.58, stratum 1
 5 Jan 23:15:33 ntpd[31353]: synchronized to 153.46.180.66, stratum 1
 5 Jan 23:15:33 ntpd[31353]: time correction of -1078 seconds exceeds 
sanity limit (1000); set clock manually to the correct UTC time.

/var/log/messages
================Jan  5 20:17:04 skyfire ntpdate[31344]: step time server
153.46.180.66
offset -2576.902436 sec
Jan  5 20:17:04 skyfire ntpd[31353]: ntpd 4.2.0a@1.1213-r Tue Apr  6
01:34:28 UTC 2004 (1)
Jan  5 20:17:04 skyfire ntpd[31353]: precision = 1.000 usec
Jan  5 20:17:04 skyfire ntpd[31353]: Listening on interface wildcard,
0.0.0.0#123
Jan  5 20:17:04 skyfire ntpd[31353]: Listening on interface lo,
127.0.0.1#123
Jan  5 20:17:04 skyfire ntpd[31353]: Listening on interface eth0,
10.23.154.10#123
Jan  5 20:17:04 skyfire ntpd[31353]: Listening on interface xen-br0,
10.23.154.10#123
Jan  5 20:17:04 skyfire ntpd[31353]: kernel time sync status 0040
Jan  5 20:17:04 skyfire ntpd[31353]: frequency initialized -137.342 PPM
from /var/lib/ntp/drift/ntp.drift
Jan  5 23:42:03 skyfire ntpdate[31679]: step time server 153.46.180.66
offset -1078.196195 sec
Jan  5 23:42:03 skyfire ntpd[31688]: ntpd 4.2.0a@1.1213-r Tue Apr  6
01:34:28 UTC 2004 (1)
Jan  5 23:42:03 skyfire ntpd[31688]: precision = 1.000 usec
Jan  5 23:42:03 skyfire ntpd[31688]: Listening on interface wildcard,
0.0.0.0#123
Jan  5 23:42:03 skyfire ntpd[31688]: Listening on interface lo,
127.0.0.1#123
Jan  5 23:42:03 skyfire ntpd[31688]: Listening on interface eth0,
10.23.154.10#123
Jan  5 23:42:03 skyfire ntpd[31688]: Listening on interface xen-br0,
10.23.154.10#123
Jan  5 23:42:03 skyfire ntpd[31688]: kernel time sync status 0040
Jan  5 23:42:03 skyfire ntpd[31688]: frequency initialized -0.567 PPM
from /var/lib/ntp/drift/ntp.drift



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

weird, it looks like your ntpd loses all access to your servers. 

It happens fast, right? 12 minutes in, and your ntpd is out of touch with 
the world.

For that amount of time, you could maybe try a tcpdump and see where the 
packets are disappearing too. Once it loses connection, you could see if 
you can get to those hosts at all. 

ron



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

> my NTP deamon is crashing almost every day. Any ideas how to fix this ?
No idea. I presume you''re running NTP in domain 0?

Does ntpd exit or crash?
It''s clearly not doing a very good job of keeping time even when
it is running.

What happens if you don''t run NTP? How rapidly does time diverge?

What kind of CPU do you have? What speed?

Ian


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

On Fri, Jan 07, 2005 at 06:02:47PM +0100, Bernhard Duebi wrote:
>  5 Jan 09:10:09 ntpd[26805]: time reset -1.835962 s
>  5 Jan 11:10:54 ntpd[26805]: time reset -12.880191 s
>  5 Jan 12:01:08 ntpd[26805]: time reset -6.980488 s
>  5 Jan 13:37:26 ntpd[26805]: time reset -1.176416 s
>  5 Jan 14:05:22 ntpd[26805]: time reset -2.373489 s
>  5 Jan 15:14:20 ntpd[26805]: time reset -244.633133 s
>  5 Jan 15:46:07 ntpd[26805]: time reset -159.285423 s
>  5 Jan 17:47:05 ntpd[26805]: time reset -0.232131 s
>  5 Jan 20:36:13 ntpd[26805]: time correction of -2577 seconds exceeds 
> sanity limit (1000); set clock manually to the correct UTC time.
Those numbers are all over the place! In the past i''ve always had it
shut down on me after it''s seen too many large deltas. So either your
clock is too far off, or there is a problem that is causing the deltas
to be all over the place.

sRp

-- 
Scott R. Parish



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel