State not saved after sync and shutdown?

General
1

Hi All,

I’ve been running two nodes and trying to get them to sync with the network. I used the latest state.jam file (16455) and sync was ok for both. After stopping the nodes, I re-synced them later (being careful not to use --state-jam again). Yet, it seems that the previous sync state was not saved - they started syncing from an older block state (~13500). Two questions:

  1. Is there a proper way to shutdown the nodes and save state?

  2. Does the --save-interval parameter affect this? What might have happened is that my nodes synced and shutdown, before a checkpoint was created.

1 Like
2

What cloud provider are you using, if any?

What persistence layer are you using?

1 Like
3

proper way to shutdown is to do exactly one Ctrl-C and then wait, may take time

2 Likes
4

Hi Casimir,

I’m running it in an ubuntu/bash environment, on a home server machine. To stop the nodes, I’ve realized I’m running kill -9. Pressing CTRL+C is actually equivalent to kill -2 (a more graceful shutdown). I’ll try this modification tonight when I get home from work.

1 Like
5

Killing the process will hose the state. Always SIGINT and wait for it to gracefully shut down.

1 Like
7

When I shut down my node, how can I ensure that the sync state is saved so it doesn’t revert to an older block height?

8

Does the --save-interval parameter guarantee state persistence, or should operators adjust it depending on hardware/network conditions?

9

control+c and wait for it to gracefully shut down

1 Like