Bug 1967971 - systemd-timesyncd fails to start on boot
Summary: systemd-timesyncd fails to start on boot
Keywords:
Status: CLOSED DUPLICATE of bug 1965720
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-04 15:20 UTC by Jan Vesely
Modified: 2021-06-07 06:55 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-07 06:55:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Vesely 2021-06-04 15:20:17 UTC
Description of problem:
Process: 1002 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)

Version-Release number of selected component (if applicable):
$ systemctl --version
systemd 248 (v248.3-1.fc34)
+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified

How reproducible:
always


Steps to Reproduce:
1. reboot
2. check for failure
3.

Actual results:
systemd-timesyncd fails to start. there's an AVC denial reported by auditd:

Jun 03 15:29:04 XXXXXXXX audit[978]: AVC avc:  denied  { watch } for  pid=978 comm="systemd-timesyn" path="/run/dbus" dev="tmpfs" ino=45 scontext=system_u:system_r:systemd_timedated_t:s0 tcontext=system_u:object_r:system_dbusd_var_run_t:>

Expected results:
systemd-timesyncd starts ok


Additional info:
The service starts ok if restarted manually after boot

Comment 1 Christian Kujau 2021-06-06 22:36:29 UTC
duplicate of bug 1965720 ...?

Comment 2 Zbigniew Jędrzejewski-Szmek 2021-06-07 06:55:40 UTC

*** This bug has been marked as a duplicate of bug 1965720 ***


Note You need to log in before you can comment on or make changes to this bug.