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.
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
Question: is systemd supposed to retry failed units at login? #15242
Comments
I dont have plymouth, or graphical.target. And it goes away if I remove/fix the above services. |
plymouth being (re)started is just another symptom of the same underlying issue caused by #14086 |
Yes, you are right. I answered before digging through the thread. Based on such external events your units might fail and stay dead or be retried. Cant tell if it's an regression however, the service in question just sometimes fails. Means I just might not have realized it earlier |
I guess we can close this given that #16149 was merged. |
systemd version the issue has been seen with
I dont get what logic is system applying to failed units, it seems that aslong as a single failed unit is in a target (eg. sysinit.target or multiuser.target) then after every new login:
Search for login in the text below to see that after this a row of services will be restarted/reevaluated.
Main culprits seem to be systemd-time-wait-sync.service and create-config.service, both wanted by sysinit.target.
The text was updated successfully, but these errors were encountered: