Hi That would be very hard to reproduce as we implemented a fix to our automation scripts, a fix that just sleeps for 60 seconds
-----Original Message----- From: [email protected] <[email protected]> On Behalf Of Miriam España Acebal Sent: 07 November 2024 10:55 To: Lucian Barboi <[email protected]> Subject: [Bug 2085518] Re: sssd service fails to restart Phishing Alert Caution, this email has been sent from an account outside of the Becrypt network. Please treat the email with caution, especially if you are requested to click on a link or open an attachment. If you think this is a phishing email, please report it to IT. Hi Lucian, Thanks for your reply. It is likely that the service is failing and systemd is trying to restart it repeatedly, so we need to figure out why that is happening. For this, we would need: - Look for something more in the journal from sssd_pam, sssd_nss and sssd_be (using journalctl -e -u <unit_name>). It would even be helpful if you could check the journal itself to see if anything elseis going on that might affect these units. - Could you provide the logs under /var/log/sssd/ ? What debug level have you set in /etc/sssd/sssd.conf? - Could you be so kind as to provide us with the mentioned conf file above -anonymized if necessary to not expose personal data-? - For Noble, we patched sssd due to the CVE-2023-3758. Before this patch was applied, did you experience this issue with version 2.9.4-1.1ubuntu6 too? - You mentioned an automation script. Could you also share it so that we can get a series of steps to reproduce the issue? The environment configuration or other quick set-up will be necessary later to process the bug as a Stable Release Upgrade (SRU) [1] as this affects a Long Term Support (LTS) series. I was also looking for similar issues upstream because it is weird to me that this kind of regression (if appropriate) isn't occurring more generally. I found this issue older than yours [2] - so it couldn't be related with the CVE applied- but with also a 60 timeout [3]. Do you put the timeout in the conf or through the script with a "sleep 60"? I will mark the bug as “Incomplete” while waiting to hear from you. Please, set it back to "New" when you provide the information requested so we can go further with this. [1] https://canonical-sru-docs.readthedocs-hosted.com/en/latest/ [2] https://github.com/SSSD/sssd/issues/6219 [3] https://github.com/SSSD/sssd/issues/6219#issuecomment-1502858787 ** Bug watch added: github.com/SSSD/sssd/issues #6219 https://github.com/SSSD/sssd/issues/6219 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3758 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/2085518 Title: sssd service fails to restart Status in sssd package in Ubuntu: New Bug description: sssd/noble-updates,noble-security,now 2.9.4-1.1ubuntu6.1 amd64 [installed,automatic] fails to restart after Active Domain realm join. A sleep 60 had to be introduced in our automation script to make "systemctl restart sssd" work in roder for sssd to reload the configuration /home/ubuntu# systemctl status sssd × sssd.service - System Security Services Daemon Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset: enabled) Active: failed (Result: start-limit-hit) since Tue 2024-10-22 16:21:05 BST; 4min 14s ago Duration: 20.155s Process: 7333 ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER} (code=exited, status=0/SUCCESS) Main PID: 7333 (code=exited, status=0/SUCCESS) CPU: 177ms Oct 22 16:20:45 lbarboi-02.testlab.local systemd[1]: Started sssd.service - System Security Services Daemon. Oct 22 16:21:05 lbarboi-02.testlab.local sssd_pam[7336]: Shutting down (status = 0) Oct 22 16:21:05 lbarboi-02.testlab.local sssd_nss[7335]: Shutting down (status = 0) Oct 22 16:21:05 lbarboi-02.testlab.local systemd[1]: Stopping sssd.service - System Security Services Daemon... Oct 22 16:21:05 lbarboi-02.testlab.local sssd_be[7334]: Shutting down (status = 0) Oct 22 16:21:05 lbarboi-02.testlab.local systemd[1]: sssd.service: Deactivated successfully. Oct 22 16:21:05 lbarboi-02.testlab.local systemd[1]: Stopped sssd.service - System Security Services Daemon. Oct 22 16:21:05 lbarboi-02.testlab.local systemd[1]: sssd.service: Start request repeated too quickly. Oct 22 16:21:05 lbarboi-02.testlab.local systemd[1]: sssd.service: Failed with result 'start-limit-hit'. Oct 22 16:21:05 lbarboi-02.testlab.local systemd[1]: Failed to start sssd.service - System Security Services Daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2085518/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085518 Title: sssd service fails to restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2085518/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
