-
Notifications
You must be signed in to change notification settings - Fork 19.9k
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
Geth won't shutdown properly when started from a systemd file. #24416
Comments
Geth might need quite a bit of time to shut down, but looking at the docs here, I think If this is a shutdown-hang which eventually is hard-killed, there should be a stacktrace. I don't suppose you have any such stacktrace somewhere? |
Please post the logs for what happens around that time |
Please try with |
Alternatively, it might suffice to set |
But please make sure to set the timeout to at least 3 minutes. Geth might want to write 1+GB on shutdown into leveldb, which can take a while. |
After the timeout it was just sending the SIGKILL signal to all process
Weirdly I rebuilt Geth after that from the latest commit and it didn't happened again for the first time in 5-6 months. I'll close the issue for now but I've added the |
System information
Geth version: 1.10.15-stable
OS & Version: Ubuntu 21.10 server
Commit hash : latest
Expected behaviour
Clean shutdown with SIGTERM or SIGINT while using systemd
Actual behaviour
After using
systemctl stop geth
the service start stopping and then search for peers instead of fully shutting down. It doesn't show as an unclean shutdown when started again but it'll resync from ~2 days prior with the messageHead state missing, repairing
Backtrace
and it goes on like this until a timeout is reached
systemd file:
The text was updated successfully, but these errors were encountered: