You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have had a regression between 41.20241216 and 41.20241230.1 w.r.t. SSSD, similar to Issue 1818 but not EXACTLY the same this time.
SSSD once again fails to start:
root@bazzite:~# systemctl status sssd
× sssd.service - System Security Services Daemon
Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf, 50-keep-warm.conf
Active: failed (Result: exit-code) since Mon 2024-12-30 13:26:53 EST; 6min ago
Invocation: 205bfdef18344c6aac6f47c7eb176ee3
Process: 1936 ExecStartPre=/bin/chown -f -R root:sssd /etc/sssd (code=exited, status=0/SUCCESS)
Process: 1938 ExecStartPre=/bin/chmod -f -R g+r /etc/sssd (code=exited, status=0/SUCCESS)
Process: 1940 ExecStartPre=/bin/sh -c /bin/chown -f sssd:sssd /var/lib/sss/db/*.ldb (code=exited, status=0/SUCCESS)
Process: 1942 ExecStartPre=/bin/chown -f -R sssd:sssd /var/lib/sss/gpo_cache (code=exited, status=0/SUCCESS)
Process: 1944 ExecStartPre=/bin/sh -c /bin/chown -f sssd:sssd /var/log/sssd/*.log (code=exited, status=1/FAILURE)
Process: 1946 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} (code=exited, status=1/FAILURE)
Main PID: 1946 (code=exited, status=1/FAILURE)
Mem peak: 11.7M
CPU: 203ms
Dec 30 13:26:47 bazzite sssd_be[1949]: Starting up
Dec 30 13:26:47 bazzite sssd[1950]: exec_child_ex command: [/usr/libexec/sssd/ldap_child] /usr/libexec/sssd/ldap_child --dumpable=1 --debug-microseconds=0 --debug-timestamps=1 --debug-f>
Dec 30 13:26:49 bazzite sssd_be[1951]: Starting up
Dec 30 13:26:49 bazzite sssd[1952]: exec_child_ex command: [/usr/libexec/sssd/ldap_child] /usr/libexec/sssd/ldap_child --dumpable=1 --debug-microseconds=0 --debug-timestamps=1 --debug-f>
Dec 30 13:26:53 bazzite sssd_be[1953]: Starting up
Dec 30 13:26:53 bazzite sssd[1954]: exec_child_ex command: [/usr/libexec/sssd/ldap_child] /usr/libexec/sssd/ldap_child --dumpable=1 --debug-microseconds=0 --debug-timestamps=1 --debug-f>
Dec 30 13:26:53 bazzite sssd[1946]: Exiting the SSSD. Could not restart critical service [<my cool domain name>].
Dec 30 13:26:53 bazzite systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE
Dec 30 13:26:53 bazzite systemd[1]: sssd.service: Failed with result 'exit-code'.
Dec 30 13:26:53 bazzite systemd[1]: Failed to start sssd.service - System Security Services Daemon.
The permissions on /etc/sssd and /etc/sssd/sssd.conf are incorrect, though this can be manually fixed. And the capabilities on the file /usr/libexec/sssd/selinux_child are no longer correct.
I think the root of the issue is likely just the capabilities on /usr/libexec/sssd/selinux_child since the service chown's the folders and files in /etc/sssd at start-up.
What did you expect to happen?
The SSSD service should start and run after updating to the latest build of bazzite, 41.20241230.1.
Describe the bug
We have had a regression between 41.20241216 and 41.20241230.1 w.r.t. SSSD, similar to Issue 1818 but not EXACTLY the same this time.
SSSD once again fails to start:
The permissions on /etc/sssd and /etc/sssd/sssd.conf are incorrect, though this can be manually fixed. And the capabilities on the file /usr/libexec/sssd/selinux_child are no longer correct.
BEFORE UPGRADE:
AFTER UPGRADE:
I think the root of the issue is likely just the capabilities on /usr/libexec/sssd/selinux_child since the service chown's the folders and files in /etc/sssd at start-up.
What did you expect to happen?
The SSSD service should start and run after updating to the latest build of bazzite, 41.20241230.1.
Output of
rpm-ostree status
Hardware
root@bazzite:~# cat /sys/devices/virtual/dmi/id/product_name
Standard PC (Q35 + ICH9, 2009)
I've recreating the issue in a VM.
Extra information or context
No response
The text was updated successfully, but these errors were encountered: