[outages] NTP Issues Today

[Jeremy Chadwick]

Colin,

Signal 15 = SIGTERM, so something intentionally shut ntpd down on your
side.  The logs I'd be interested in would be prior to what you've
provided, i.e. what lead to the SIGTERM.

Also, no timezone is mentioned anywhere in your timestamps, so please
provide that (UTC offset would be best).

-- 
| Jeremy Chadwick                                   jdc at koitsu.org |
| UNIX Systems Administrator                http://jdc.koitsu.org/ |
| Mountain View, CA, US                                            |
| Making life hard for others since 1977.             PGP 4BD6C0CB |

On Tue, Nov 20, 2012 at 05:02:06PM +0000, Colin Johnston wrote:
> 
> On 20 Nov 2012, at 15:38, Jeremy Chadwick <jdc at koitsu.org> wrote:
> 
> > I'm still waiting for someone who was affected by this to provide
> > coherent logs from ntpd showing exactly when the time change happened.
> > Getting these, at least on an *IX system, is far from difficult folks.
> > 
> 
> from firewall ntp logs
> Nov 19 09:58:06 [192.168.0.1.128.176] 2012:11:19-09:58:06 ntpd[21385]: ntpd exiting on signal 15
> Nov 19 09:58:19 [192.168.0.1.128.176] 2012:11:19-09:58:19 selfmonng[3503]: W check Failed increment ntpd_running counter 3 - 3
> Nov 19 09:58:22 [192.168.0.1.128.176] 2012:11:19-09:58:22 selfmonng[3503]: W NOTIFYEVENT Name=ntpd_running Level=INFO Id=147 sent
> Nov 19 09:58:22 [192.168.0.1.128.176] 2012:11:19-09:58:22 selfmonng[3503]: W triggerAction: 'cmd'
> Nov 19 09:58:22 [192.168.0.1.128.176] 2012:11:19-09:58:22 selfmonng[3503]: W actionCmd(+):  '/var/mdw/scripts/ntp restart'
> Nov 19 09:58:25 [192.168.0.1.128.176] 2012:11:19-09:58:25 ntpd[24120]: ntpd 4.2.4p8 at 1.1612-o Tue Feb  2 21:46:54 UTC 2010 (1)
> Nov 19 09:58:25 [192.168.0.1.128.176] 2012:11:19-09:58:25 selfmonng[3503]: W child returned status: exit='0' signal='0'
> Nov 19 09:58:35 [192.168.0.1.128.176] 2012:11:19-09:58:35 ntpd[24121]: kernel time sync status change 0001
> 
> was sync'd to 84.25.175.98, stratum 2 at the time I believe
> 
> Colin