[opensuse-support] systemd-timesyncd failure (with solution)
Hi list, just noticed my time was off - and found systemd-timesynced wasn't running woodstock:~ # systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-06-25 16:04:16 WEST; 11s ago Docs: man:systemd-timesyncd.service(8) Process: 4615 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=238/STATE_DIRECTORY) Main PID: 4615 (code=exited, status=238/STATE_DIRECTORY) If you experience the same, Arch Wiki[1] had the solution: # rm -rf /var/lib/systemd/timesync # rm -rf /var/lib/private/systemd/timesync After that it starts again. [1] https://wiki.archlinux.org/index.php/Systemd-timesyncd#systemd-timesyncd_fai... -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Carlos E. R. wrote:
On 25/06/2019 17.16, Peter Suetterlin wrote:
Hi list,
just noticed my time was off - and found systemd-timesynced wasn't running
You could have chrony running instead.
Or ntpd. But that's not the topic ;^> -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 26/06/2019 16.10, Peter Suetterlin wrote:
Carlos E. R. wrote:
On 25/06/2019 17.16, Peter Suetterlin wrote:
Hi list,
just noticed my time was off - and found systemd-timesynced wasn't running
You could have chrony running instead.
Or ntpd.
But that's not the topic ;^>
I don't know, on one machine I found both running and disabled systemd-timesynced. Time was off, so I restarted chrony and everything was ok. I mean, maybe the correct or default status for systemd-timesynced is off. Reading again your first post, it seems that you had it set to run, yet it did not. Is that it? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
I don't know, on one machine I found both running and disabled systemd-timesynced. Time was off, so I restarted chrony and everything was ok.
I mean, maybe the correct or default status for systemd-timesynced is off.
Yes, it is. Vendor default: disabled. So it might not affect too many people. But for a laptop it is a very reasonable choice (IMHO). On permanently running machines I still prefer ntpd.
Reading again your first post, it seems that you had it set to run, yet it did not. Is that it?
Yep. And systemd did an update that is not update-safe, as runtime-generated files from previous versions prevent the new version from starting. :( So I thought I mention it on the list, in case others are looking for solutions.... -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 26/06/2019 19.03, Peter Suetterlin wrote:
Carlos E. R. wrote:
...
Reading again your first post, it seems that you had it set to run, yet it did not. Is that it?
Yep. And systemd did an update that is not update-safe, as runtime-generated files from previous versions prevent the new version from starting. :( So I thought I mention it on the list, in case others are looking for solutions....
I understand now, thanks. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
26.06.2019 20:03, Peter Suetterlin пишет:
Yep. And systemd did an update that is not update-safe, as runtime-generated files from previous versions prevent the new version from starting. :( So I thought I mention it on the list, in case others are looking for solutions....
Considering you never mentioned your distribution version it is unclear how effective it is. Did you file openSUSE bug report? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Wed, 2019-06-26 at 20:24 +0300, Andrei Borzenkov wrote:
26.06.2019 20:03, Peter Suetterlin пишет:
Yep. And systemd did an update that is not update-safe, as runtime-generated files from previous versions prevent the new version from starting. :( So I thought I mention it on the list, in case others are looking for solutions....
Considering you never mentioned your distribution version it is unclear how effective it is. Did you file openSUSE bug report?
There has been one for about three weeks now: https://bugzilla.opensuse.org/show_bug.cgi?id=1137341 Cheers. -- Atri Bhattacharya Thu 27 Jun 11:37:44 CEST 2019 Sent from openSUSE Tumbleweed 20190623 on my laptop. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Atri B -
Carlos E. R. -
Peter Suetterlin