systemd ships with some default values, which include StartLimitIntervalSec and StartLimitBurst. Here are the values from a fresh, up-to-date, Jammy VM.
# grep -E 'StartLimitInterval|StartLimitBurst' /etc/systemd/system.conf #DefaultStartLimitIntervalSec=10s #DefaultStartLimitBurst=5 Is the proposal here to just increase StartLimitIntervalSec to 50s (following the upstream service file)? If so, I think this is not really worth SRUing. There might be scenarios where even 50s is not enough: I can imagine scenarios where the 5 failures are spaced apart enough so that they do not occur during the same 50s window. Even when testing this locally I was not able to reproduce this locally by just configuring sssd to point to a missing keytab, since the failures happen fast enough to trigger the StartLimitBurst. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2122722 Title: SSSD systemd service unit causes a boot loop in certain circumstances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2122722/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
