Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

How do I stop nodeos gracefully? #4301

Closed
kein-S opened this issue Jun 23, 2018 · 2 comments
Closed

How do I stop nodeos gracefully? #4301

kein-S opened this issue Jun 23, 2018 · 2 comments

Comments

@kein-S
Copy link

kein-S commented Jun 23, 2018

The kill command causes the following error when it is executed again.

pkill -9 nodeos or kill -9 {pid}
database dirty flag set (likely due to unclean shutdown): replay required

And when I re-run nodeos, it is ignored using the --replay-blockchain command.

@kein-S
Copy link
Author

kein-S commented Jun 23, 2018

found it

This appears to be two different issues.

Startup after a crash or ungraceful shutdown nearly always fails due to corruption of the boost shared memory cache of the in-memory database. --resync is required to clean up the mess.

For normal shutdown, never kill with -9. Always use either the default (no argument) signal (which is SIGTERM) or SIGINT. Numerically, those are 15 and 2, respectively.

pkill nodeos | Safe
pkill -15 nodeos | Safe
pkill -2 nodeos | Safe
pkill -TERM nodeos | Safe
pkill -SIGTERM nodeos | Safe
pkill -INT nodeos | Safe
pkill -SIGINT nodeos | Safe
pkill -9 nodeos | Not Safe
pkill -KILL nodeos | Not Safe
pkill -SIGKILL nodeos | Not Safe

The core dump is a different problem. That looks like a corrupted network packet, specifically a signed_block_summary. Summary messages are being eliminated from the protocol, so this particular error will no longer be possible soon.

from @jgiszczak 's

@xiaopidanO
Copy link

hello,I tried this way , but When I exit , it still remind me that I have Suspended task

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants