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

Bisq seednode exits cleanly on fatal error, causing systemd to not automatically restart it #6225

Closed
wiz opened this issue May 25, 2022 · 0 comments · Fixed by #6230
Closed

Bisq seednode exits cleanly on fatal error, causing systemd to not automatically restart it #6225

wiz opened this issue May 25, 2022 · 0 comments · Fixed by #6230

Comments

@wiz
Copy link
Contributor

wiz commented May 25, 2022

In the /etc/systemd/system/bisq.service file I correctly enabled Restart=on-failure, but since Bisq exits with signal 0 on a fatal Out Of Memory heap error, systemd did not restart it and my seednode wizseeds was offline until I manually restarted it.

Bisq should exit with error code 1 if such fatal errors such as Out Of Memory occur so that systemd can automatically restart it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Pricenode: Add JVM flag ExitOnOutOfMemoryError
1 participant
@wiz