-
Notifications
You must be signed in to change notification settings - Fork 508
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
Issue and fix for failed systemd startup at boot. #70
Comments
It sounds like it is trying to start too early. Can you make the service depend on some standardized network target instead? |
The unit file I show is the one "installed" with installing iodine. I just added the StartLimit* lines. Yes, I could modify it for myself but I'm offering this intel to help fix others issues. :-) |
Sorry, let me clarify. I am for updating the unit file, but would prefer another strategy. As I understand it systemd has some standard unit for network activation, and by saying iodined should start after that is done it would also work for your case? It seems more stable than prolonging the crash-restart loop (other environments might need longer timeouts than you). |
@yarrick seems that it is done already |
@daxm can you provide any logs with failing attempts? |
Try this one. |
I encountered an issue with the systemd service failing to start and then failing to restart too fast. It appears that systemd, by default, attempts 5 times to restart and then quits. After the following changes I was able to get iodined.service to start up. (A little digging showed that my server needed 7 failures... just over the 5 that systemd permits by default.)
Here is the Unit file I got to work:
The only real difference is the StartLimit* lines. I think the only one that matters is the StartLimitBurst one but I've left both in there since it works consistently.
If it matters, I'm in a VM of Ubuntu 20.04 Desktop (gnome) with no modifications (basically a bare bones Ubuntu desktop install).
The text was updated successfully, but these errors were encountered: