https://bugzilla.redhat.com/show_bug.cgi?id=2247777

Alexey Tikhonov atikhono@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(lzap@redhat.com)

--- Comment #1 from Alexey Tikhonov atikhono@redhat.com --- 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/M...

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.

https://bugzilla.redhat.com/show_bug.cgi?id=2247777

Lukas Zapletal lzap@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lzap@redhat.com) |

--- Comment #3 from Lukas Zapletal lzap@redhat.com --- 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

https://bugzilla.redhat.com/show_bug.cgi?id=2247777

Lukas Zapletal lzap@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTABUG Status|NEW |CLOSED Flags|needinfo?(lzap@redhat.com) | Last Closed| |2023-11-03 12:28:08

--- Comment #5 from Lukas Zapletal lzap@redhat.com --- 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

https://bugzilla.redhat.com/show_bug.cgi?id=2247777

jstephen@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jstephen@redhat.c | |om) | Status|CLOSED |ASSIGNED Priority|unspecified |medium Component|sssd |cockpit-session-recording Assignee|sssd-maintainers@lists.fedo |jstephen@redhat.com |raproject.org | Resolution|NOTABUG |--- Keywords| |Reopened

--- Comment #7 from jstephen@redhat.com --- (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.

https://bugzilla.redhat.com/show_bug.cgi?id=2247777

Aoife Moloney amoloney@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution|--- |EOL Last Closed|2023-11-03 12:28:08 |2024-05-31 08:52:53

--- Comment #9 from Aoife Moloney amoloney@redhat.com --- Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field.

If you are unable to reopen this bug, please file a new report against an active release.

Thank you for reporting this bug and we are sorry it could not be fixed.