apcupsd or rtkit - Caused time to go haywire on shutdown/reboot??
On Wed, Oct 19, 2011 at 14:46, Leonid Isaev <firstname.lastname@example.org> wrote:
> On (10/19/11 14:19), David C. Rankin wrote:
> -~> On 10/18/2011 04:33 PM, Leonid Isaev wrote:
> -~> >-~> That's 3 spontaneous reboots in 11 minutes. Something is
> really off.
> -~> >-~>
> -~> >-~> --
> -~> >-~> David C. Rankin, J.D.,P.E.
> -~> >
> -~> >Nothing puzzling here: the kernel is working correctly but your RTC
> is wrong
> -~> >(no idea how this could happen though). If by "spontaneous" you mean
> "no errors
> -~> >in the logs", then it's a hardware problem. As a first step, I would
> -~> >apcupsd and get rid of UPS.
> -~> No errors in the logs, to the RTC looks like the culprit. After
> -~> fixing the RTC, I haven't experienced any more of the reboots.
> -~> Bizarre... This box has run fine for years, then following the
> -~> power outage, the RTC went nuts. I think that was simply the
> -~> issue. However, I don't think we will ever explain why the RTC
> -~> became an issue that caused the reboots. Looking at all the logs,
> -~> the RTC has been all over the place this past month:
> -~> Oct 19 13:15:02 providence crond: time disparity of 301 minutes
> -~> Oct 18 12:42:00 providence crond: time disparity of -479 minutes
> -~> Oct 18 12:32:00 providence crond: time disparity of -479 minutes
> -~> Oct 18 11:19:01 providence crond: time disparity of -479 minutes
> -~> Oct 18 09:44:01 providence crond: time disparity of -478 minutes
> -~> Oct 12 09:24:01 providence crond: time disparity of -79 minutes
> -~> Oct 7 10:55:59 providence crond: time disparity of 253 minutes
> -~> Oct 5 07:55:57 providence crond: time disparity of 383 minutes
> -~> Oct 3 16:23:01 providence crond: time disparity of 301 minutes
> -~> 300 is correct for the 5 hour offset for CDT, I can't explain the
> -~> wild swings from Oct 3 to Oct 18. That is a 862 minute difference
> -~> between Oct 5 and Oct 18. init scripts? kernels?
> -~> The other box that experienced this problem had the following:
> -~> Oct 5 08:27:32 localhost crond: time disparity of -546 minutes
> -~> Sep 27 22:18:01 localhost crond: time disparity of -475 minutes
> -~> both those dates must have been kernel updates, because that is
> -~> the only time that box gets restarted. Strange, thanks for your
> -~> help.
> -~> --
> -~> David C. Rankin, J.D.,P.E.
> OK. But few remarks:
> (1) Crond or any other program including syslog must use
> the current timezone unless you specifically instructed it to use UTC, so
> offsets are not fine. The rtkit stuff IS A BUG related to chroot being
> to set a correct TZ.
> (2) Either your motherboard is hosed or the RTC battery is discharged. Do
> have a large time drift (like an hour per day) reported by the hwclock? If
> have time offsets only when rebooted, I think the second option is more
> Leonid Isaev
> GnuPG key ID: 164B5A6D
> Key fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Late to the party, but I just had a box jump off by 360 minutes. It was
used this morning then sat all day. Bios is set to utc, rc.conf is set for
utc, and time zone is correct.
Local time was 23:04 Nov 20, and the box showed 05:04 Nov 21. I updated the
box yesterday. Turns out there was an error in /etc/ntp.conf. I didn't
check file and line 37 [ Allow localhost ] caused ntpd to through a shoe.
Proof that laziness is not always the best policy.
This may be totally unrelated to your problem but thought I would pass this