[ntp:questions] panic_stop with ntpd v4.2.6p3

unruh unruh at invalid.ca
Wed Jan 30 18:23:27 UTC 2013


On 2013-01-30, John Connor <john.connor at gmail.com> wrote:
> Hi
>
> I'm running ntpd v4.2.6p3 on Solaris 8 (I know; necessity..) and recently it experienced a panic_stop event:
>
> 24 Jan 00:36:15 ntpd[244]: 82.219.4.30 961a 8a sys_peer
> 24 Jan 06:55:26 ntpd[244]: 0.0.0.0 0628 08 no_sys_peer
> 24 Jan 08:32:13 ntpd[244]: 82.219.4.30 961a 8a sys_peer
> 24 Jan 08:32:13 ntpd[244]: 0.0.0.0 0613 03 spike_detect -20.996956 s
> 24 Jan 08:49:32 ntpd[244]: 0.0.0.0 061c 0c clock_step -20.996729 s
> 24 Jan 08:49:11 ntpd[244]: 0.0.0.0 0615 05 clock_sync
> 24 Jan 08:49:13 ntpd[244]: 83.170.75.28 8014 84 reachable
> 24 Jan 08:49:13 ntpd[244]: 0.0.0.0 c618 08 no_sys_peer
> 24 Jan 08:49:13 ntpd[244]: 82.219.4.30 8024 84 reachable
> 24 Jan 08:49:13 ntpd[244]: 149.255.102.233 8024 84 reachable
> 24 Jan 09:08:47 ntpd[244]: 83.170.75.28 962a 8a sys_peer
> 24 Jan 09:43:30 ntpd[244]: 82.219.4.30 963a 8a sys_peer
> 24 Jan 13:49:52 ntpd[244]: 149.255.102.233 963a 8a sys_peer
> 24 Jan 14:07:29 ntpd[244]: 82.219.4.30 961a 8a sys_peer
> 24 Jan 18:29:46 ntpd[244]: 149.255.102.233 961a 8a sys_peer
> 24 Jan 19:05:49 ntpd[244]: 82.219.4.30 961a 8a sys_peer
> 24 Jan 23:47:44 ntpd[244]: 149.255.102.233 961a 8a sys_peer
> 25 Jan 00:39:38 ntpd[244]: 82.219.4.30 961a 8a sys_peer
> 25 Jan 03:54:29 ntpd[244]: 149.255.102.233 961a 8a sys_peer
> 25 Jan 04:09:41 ntpd[244]: 82.219.4.30 961a 8a sys_peer
> 25 Jan 09:41:09 ntpd[244]: 149.255.102.233 961a 8a sys_peer
> 25 Jan 11:31:32 ntpd[244]: 82.219.4.30 961a 8a sys_peer
> 25 Jan 19:17:19 ntpd[244]: 0.0.0.0 0628 08 no_sys_peer
> 25 Jan 21:19:03 ntpd[244]: 82.219.4.30 961a 8a sys_peer
> 25 Jan 21:19:03 ntpd[244]: 0.0.0.0 0617 07 panic_stop -741 s; set clock manually within 60 s.
>
> Config file as follows:
>
> # ntp.conf
> #
>
> restrict default nomodify notrap
> restrict 127.0.0.1
> restrict 62.60.123.0 mask 255.255.255.0
>
> server 0.uk.pool.ntp.org
> server 1.uk.pool.ntp.org
> server 2.uk.pool.ntp.org
> server 3.uk.pool.ntp.org
>
> driftfile /etc/ntp.drift
> logconfig=syncall +clockall +sysall +peerall
> logfile /data/ntp.log
> tinker panic 60
> #
>
> I have noticed a number of large spikes:
>
> 27 Jan 12:26:32 ntpd[21030]: 0.0.0.0 0613 03 spike_detect -20.998734 s
> 27 Jan 12:44:29 ntpd[21030]: 0.0.0.0 061c 0c clock_step -20.998740 s
> 28 Jan 14:49:43 ntpd[21030]: 0.0.0.0 0613 03 spike_detect +41.002124 s
> 28 Jan 15:25:10 ntpd[21030]: 80.93.163.202 961a 8a sys_peer
> 28 Jan 15:25:10 ntpd[21030]: 0.0.0.0 061c 0c clock_step +41.002456 s
>
> Any advice would be appreciated.

Get a better computer. 
Stop the other program that is resetting your clock from doing so.

You do not tell us anything about your system, but your clock is
suddenly jumping. As the above either a hardware of software fault. 

>
> Cheers
> JC



More information about the questions mailing list