-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/01/2012 03:42 PM, Leonid Isaev wrote: <snip> >> >> Aug 1 13:20:15 providence apcupsd[3477]: apcupsd shutdown succeeded >> Aug 1 13:20:15 providence kernel: [171092.364247] apcupsd[3477]: segfault >> at 0 ip 0805c706 sp bfcdfff0 error 4 in apcupsd[8048000+38000] > > Does apcupsd routinely segfault? > No, the segfault just started on July 30: [17:40 providence:/var/log] # grep apcupsd everything.log* | grep segfault everything.log:Jul 30 13:48:24 providence kernel: [603728.758431] apcupsd[3190]: segfault at 0 ip 0805e0fc sp bfe397c0 error 4 in apcupsd (deleted)[8048000+39000] everything.log:Aug 1 13:20:15 providence kernel: [171092.364247] apcupsd[3477]: segfault at 0 ip 0805c706 sp bfcdfff0 error 4 in apcupsd[8048000+38000] The only config change I can see in the apcupsd.conf.pacnew is: LOCKFILE /var/lock -> LOCKFILE /etc/apcupsd I can't see that causing a segfault, could it? >> Aug 1 13:20:15 providence ntpd[3454]: Listen normally on 6 eth0 >> 192.168.7.124 UDP 123 >> Aug 1 13:20:15 providence ntpd[3454]: peers refreshed >> Aug 1 13:20:15 providence ntpd[3454]: new interface(s) found: waking up >> resolver Aug 1 13:20:15 providence postfix/postfix-script[13735]: stopping >> the Postfix mail system >> Aug 1 13:20:15 providence postfix/master[3868]: terminating on signal 15 >> Aug 1 13:20:15 providence postfix/postfix-script[13738]: waiting for the >> Postfix mail system to terminate >> Aug 1 13:20:16 providence dhcpcd[424]: eth0: sending IPv6 Router >> Solicitation Aug 1 13:20:19 providence ntpd[3454]: ntpd exiting on signal 15 > > Your NTP behaves strangely... why would it refresh timeservers and then > shutdown at the same timestamp? It looks like your ntp did something funny and > incorrectly adjusted the HW clock. Now that you mention it, I don't know why it would refresh at shutdown. I think this is just a normal log event that occurred between the time the apcupsd shutdown was commanded at 13:20:15 and the ntpd refresh at 13:20:15. I just don't think ntpd had time to get the message yet... Thanks for your help. I occurred during a power event, so I guess we'll just chock it up to stray voltage that somehow zapped the month bit in the bios ahead by 1..... Sounds screwy, but I don't know the system/kernel/bios well enough to know how else it could have occurred or what even interfaces with the hardware clock for that matter. System time was fine up until the time of restart... - -- David C. Rankin, J.D.,P.E. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAZssUACgkQZMpuZ8CyrcgM6gCfcqf+TsykvukqW/ca0La2l6Tc lIYAn1YizdUmq9+lCD0Ns5jEDd02NwXf =d3sE -----END PGP SIGNATURE-----
