Re: [ntp:questions] NTP stops responding
A C wrote: I've got a separate question from the PPS issue. Has anyone experienced a situation where ntpd stops responding completely? I've never heard of that happening. However, ntpd will stop running if it appears that the local time is off by more than 1000 seconds. This can be disabled for the first setting. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP stops responding
On 8/21/2011 23:42, David Woolley wrote: > A C wrote: >> I've got a separate question from the PPS issue. Has anyone >> experienced a situation where ntpd stops responding completely? > > I've never heard of that happening. However, ntpd will stop running if > it appears that the local time is off by more than 1000 seconds. This > can be disabled for the first setting. The time was already within a few milliseconds of the available network clocks but I was using a GPS receiver as one of the available clocks. However, the PPS isn't working (see the other thread for that issue) so the log file was full of "kern PPS no signal" messages and eventually stopped doing anything. Logging stopped, responses to queries stopped, everything except an explicit kill. I removed the GPS refclock completely and so far it's fine. I'll see how it looks tomorrow but it seems like the two issues may be related. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Fwd: Re: NetBSD GPS/PPS using 4.2.6p3
On Sun, Aug 21, 2011 at 02:55:55PM -0700, A C wrote: > That is where I obtained the ppstest code and then later I > discovered the test code within the ntpd source distribution. The > NetBSD list also suggested that I compare kernel traces on the two > programs. It seems that ntpd's pps-api code behaves a bit > differently than ntpd itself when it interfaces with the kernel. I > can provide traces to anyone that would like them for both the > pps-api test program and ntpd 4.2.6p3. > 127.127.22.1 flag2 0 flag3 1 refid PPS\n\n > 11255 1 ntpd CALL ioctl(7,PPS_IOC_SETPARAMS,0x1052d204) > 11255 1 ntpd CALL ioctl(7,PPS_IOC_KCBIND,0xefffdf8c) A shot in the dark, have you tried removing "flag3 1" to disable the kernel PPS discipline? -- Miroslav Lichvar ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Fwd: Re: NetBSD GPS/PPS using 4.2.6p3
On 8/22/2011 07:45, Miroslav Lichvar wrote: On Sun, Aug 21, 2011 at 02:55:55PM -0700, A C wrote: That is where I obtained the ppstest code and then later I discovered the test code within the ntpd source distribution. The NetBSD list also suggested that I compare kernel traces on the two programs. It seems that ntpd's pps-api code behaves a bit differently than ntpd itself when it interfaces with the kernel. I can provide traces to anyone that would like them for both the pps-api test program and ntpd 4.2.6p3. 127.127.22.1 flag2 0 flag3 1 refid PPS\n\n 11255 1 ntpd CALL ioctl(7,PPS_IOC_SETPARAMS,0x1052d204) 11255 1 ntpd CALL ioctl(7,PPS_IOC_KCBIND,0xefffdf8c) A shot in the dark, have you tried removing "flag3 1" to disable the kernel PPS discipline? Yes but ntpd still doesn't see the PPS signal on DCD with or without flag3. So I'm lost on how to solve this problem. I know the PPS signal is there on the wire, I know DCD is being asserted and cleared. I know the test code can see it but for some reason I just can't make ntpd see it. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] NTP stops responding
On 8/22/2011 07:38, A C wrote: On 8/21/2011 23:42, David Woolley wrote: > A C wrote: >> I've got a separate question from the PPS issue. Has anyone >> experienced a situation where ntpd stops responding completely? > > I've never heard of that happening. However, ntpd will stop running if > it appears that the local time is off by more than 1000 seconds. This > can be disabled for the first setting. The time was already within a few milliseconds of the available network clocks but I was using a GPS receiver as one of the available clocks. However, the PPS isn't working (see the other thread for that issue) so the log file was full of "kern PPS no signal" messages and eventually stopped doing anything. Logging stopped, responses to queries stopped, everything except an explicit kill. I removed the GPS refclock completely and so far it's fine. I'll see how it looks tomorrow but it seems like the two issues may be related. I've let ntpd run twice as long as it did yesterday and there's no sign of it hanging. Therefore it appears that ntpd will hang when the GPS NMEA refclock is configured, kernel PPS (flag3) is enabled, and the PPS from the kernel isn't available for an extended period of time (this goes right back to my ongoing issue with PPS and ntpd). I'm going to leave flag3 off and make sure the refclock isn't blowing up on its own. I still want to get PPS working somehow but I just need to make sure ntpd is going to stay running. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
