| Summary: |
systemd-timesyncd fails to start on boot |
| Product: |
[Fedora] Fedora
|
Reporter: |
Jan Vesely <jan.vesely> |
| Component: |
systemd | Assignee: |
systemd-maint |
| Status: |
CLOSED
DUPLICATE
|
QA Contact: |
Fedora Extras Quality Assurance <extras-qa> |
| Severity: |
unspecified
|
Docs Contact: |
|
| Priority: |
unspecified
|
|
|
| Version: |
34 | CC: |
fedoraproject, filbranden, flepied, kasong, lnykryn, msekleta, redhat, ssahani, s, systemd-maint, yuwatana, zbyszek
|
| Target Milestone: |
--- | |
|
| Target Release: |
--- | |
|
| Hardware: |
Unspecified | |
|
| OS: |
Unspecified | |
|
| Whiteboard: |
|
|
Fixed In Version:
|
|
Doc Type:
|
If docs needed, set a value
|
|
Doc Text:
|
|
Story Points:
|
---
|
|
Clone Of:
|
|
Environment:
|
|
|
Last Closed:
|
2021-06-07 06:55:40 UTC
|
Type:
|
Bug
|
|
Regression:
|
---
|
Mount Type:
|
---
|
|
Documentation:
|
---
|
CRM:
|
|
|
Verified Versions:
|
|
Category:
|
---
|
|
oVirt Team:
|
---
|
RHEL 7.3 requirements from Atomic Host:
|
|
|
Cloudforms Team:
|
---
|
Target Upstream Version:
|
|
|
Embargoed:
|
|
| |
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