Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Restart=on-failure without a limit is holding boot forever #5753

Closed
luizluca opened this issue Aug 18, 2021 · 2 comments
Closed

Restart=on-failure without a limit is holding boot forever #5753

luizluca opened this issue Aug 18, 2021 · 2 comments
Assignees
@aplopez
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.

Comments

@luizluca
Copy link
Contributor

Hello,

In OpenSUSE Tumbleweed, sssd-2.5.2-1.1 crashes and restarts endlessly (like when there is no keytab for a configured sssd-ad domain). However, it also holds the boot process and it never reaches the login screen (sddm or agetty). I have to mask sssd.service from kernel command line to workaround it.

I opened https://bugzilla.suse.com/show_bug.cgi?id=1188999 and the suggestion was to add StartLimitIntervalSec and StartLimitBurst to let it fail and the system boot. But they also asked to open this issue upstream.
@alexey-tikhonov
Copy link
Member

https://bugzilla.redhat.com/show_bug.cgi?id=1796466#c10

@aplopez aplopez self-assigned this Mar 23, 2022
aplopez added a commit to aplopez/sssd that referenced this issue Mar 23, 2022
@aplopez
systemd: only relaunch after crashes and do not retry forever
823b8b0 
Set Relaunch=on-abnormal to only relaunch after a crash. Systemd
will not try to relaunch sssd if it returned with an error code,
for instance, on a wrong configuration file.
Use StartLimitIntevalSec and StartLimitBurst to limit the number of
times it is relaunched. Avoid blocking the boot process.

Resolves: SSSD#5753
@pbrezina
Copy link
Member

Pushed PR: #6075

  • master
    • a049ac7 - systemd: only relaunch after crashes and do not retry forever

@pbrezina pbrezina added the Closed: Fixed Issue was closed as fixed. label Mar 29, 2022
stbenjam added a commit to stbenjam/installer that referenced this issue Apr 5, 2022
@stbenjam
gather: collect sssd journal logs
b778ad4 
This adds sssd to the list of services we collect logs from. Currently,
vsphere and metal are failing to bootstrap and there's some evidence
collected from manual runs that we're hitting an issue in sssd[1].

Note, this also alphabetizes the list of services we collect logs from.

[1] SSSD/sssd#5753
@stbenjam stbenjam mentioned this issue Apr 5, 2022
Merged
stbenjam added a commit to stbenjam/installer that referenced this issue Apr 5, 2022
@stbenjam
gather: collect sssd journal logs
afb5c3e 
This adds sssd to the list of services we collect logs from. Currently,
vsphere and metal are failing to bootstrap and there's some evidence
collected from manual runs that we're hitting an issue in sssd[1].

Note, this also alphabetizes the list of services we collect logs from.

[1] SSSD/sssd#5753
clnperez pushed a commit to clnperez/installer that referenced this issue Apr 21, 2022
@stbenjam @clnperez
gather: collect sssd journal logs
e8dd344 
This adds sssd to the list of services we collect logs from. Currently,
vsphere and metal are failing to bootstrap and there's some evidence
collected from manual runs that we're hitting an issue in sssd[1].

Note, this also alphabetizes the list of services we collect logs from.

[1] SSSD/sssd#5753
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aplopez aplopez

Labels
Bugzilla Closed: Fixed Issue was closed as fixed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@luizluca @aplopez @pbrezina @alexey-tikhonov