I installed a fresh Fedora 38, installed Session Recording in Cockpit, enabled All recording and SSSD does not start anymore. The error is: Condition ConditionPathExists=/etc/sssd/sssd.conf was not met. I think previously it was booting up properly. I reported to Cockpit guys via Slack, I was told to create a bug for the Session Recording plugin so I did: https://github.com/Scribery/cockpit-session-recording/issues/157 It looks like this might be a bug in the systemd unit file: "The SSSD unit file should also have ConditionDirectoryNotEmpty=|/etc/sssd/conf.d/" So leaving a bugreport for you guys. Reproducible: Always Steps to Reproduce: 1. Enable Session Recording via plugin as described 2. Sssd will not start anymore 3.
Hi, (In reply to Lukas Zapletal from comment #0) > I installed a fresh Fedora 38, installed Session Recording in Cockpit, > enabled All recording and SSSD does not start anymore. The error is: > Condition ConditionPathExists=/etc/sssd/sssd.conf was not met. I think > previously it was booting up properly. > > I reported to Cockpit guys via Slack, I was told to create a bug for the > Session Recording plugin so I did: > > https://github.com/Scribery/cockpit-session-recording/issues/157 > > It looks like this might be a bug in the systemd unit file: > > "The SSSD unit file should also have > ConditionDirectoryNotEmpty=|/etc/sssd/conf.d/" It has: https://github.com/SSSD/sssd/blob/e217fa8262696d441de2eca9475a8eda87dfc16f/Makefile.am#L97 Could you please attach content of /var/log/sssd/sssd.log (or '/var/log/sssd/*)? It's better to clean this folder before reboot attempt.
and a relevant part of "journalctl -xeu sssd.service"
Hmmm interesting indeed: $ grep Condition /usr/lib/systemd/system/sssd.service ConditionPathExists=|/etc/sssd/sssd.conf ConditionDirectoryNotEmpty=|/etc/sssd/conf.d/ $ sudo cat /var/log/sssd/sssd.log | fpaste Uploading (66.2KiB)... https://paste.centos.org/view/a656e5f0 # tail -n200 /var/log/sssd/*log | fpaste Uploading (103.2KiB)... https://paste.centos.org/view/f858fc3d # journalctl -xeu sssd.service | fpaste Uploading (9.6KiB)... https://paste.centos.org/view/801023ab One idea - it could have been some syntax error in the snippet, attaching: # cat /etc/sssd/conf.d/sssd-session-recording.conf | fpaste Uploading (0.3KiB)... https://paste.centos.org/view/46c741b1
> [be[nssfiles]] [dp_module_open_lib] (0x0010): Unable to load module [proxy] with path [/usr/lib64/sssd/libsss_proxy.so]: /usr/lib64/sssd/libsss_proxy.so: cannot open shared object file: No such file or directory Do you have 'sssd-proxy' installed that provides '/usr/lib64/sssd/libsss_proxy.so'?
I don’t, that fixed the problem. I performed the installation/configuration through cockpit interface, so I guess that should be installed from there. Thanks for help
Hi Justin, can cockpit-session-recording require/install sssd-proxy if its usage configured?
(In reply to Alexey Tikhonov from comment #6) > Hi Justin, > > can cockpit-session-recording require/install sssd-proxy if its usage > configured? Yes, I will take care of this. Switching component and re-opening this BZ.