https://bugzilla.novell.com/show_bug.cgi?id=733626 https://bugzilla.novell.com/show_bug.cgi?id=733626#c0 Summary: NTP service dies a few minutes after bootup, leaving the clock one hour in the future Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: antoine.mechelynck@belgacom.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111129 Firefox/11.0a1 SeaMonkey/2.8a1 A few minutes after bootup, ntp.service goes dead, leaving the system clock one hour in the future. If at this point I do systemctl reload-or-restart ntp.service the clock is reset to the right time and the NTP service remains up indefinitely. Reproducible: Always Steps to Reproduce: 1. Bootup in default runlevel (multiuser with X11) 2. Wait a few minutes 3. systemctl status ntp.service Actual Results: - ntp.service is "inactive (dead)" - there is no ntpd process running - the clock is one hour in the future Expected Results: ntpd should go on running and the clock should be set right Additional info: If I start working on /dev/tty1../dev/tty6 rather than logging immediately into X, my workflow will be interrupted (maybe in the middle of typing a command at the shell prompt) by system messages telling me that ntpd.service was "successfully" turned off. I may then notice (e.g. by doing systemctl status for a service started shortly before the messages) that my clock had already been off by one hour for some time before that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.