http://bugzilla.opensuse.org/show_bug.cgi?id=1074904 Bug ID: 1074904 Summary: chronyd fails to start on boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: patrick.schaaf@yalwa.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- For a while now, after reboot of tumbleweed VMs, I see chronyd failing to start. Starting it by hand once I notice, works fine. journal shows: Jan 07 11:46:51 HOSTNAME systemd[1]: chronyd.service: Start operation timed out. Terminating. Jan 07 11:46:51 HOSTNAME systemd[1]: chronyd.service: Unit entered failed state. Jan 07 11:46:51 HOSTNAME systemd[1]: chronyd.service: Failed with result 'timeout'. The issue is not reproducable - it just fails after some reboots. /etc/chrony.conf does not contain hostnames, just some (local) servers specified by IP address. -- You are receiving this mail because: You are on the CC list for the bug.