Author Topic: Clean shutdown of witness_node / avoiding object database recreation  (Read 1542 times)

0 Members and 1 Guest are viewing this topic.

Offline jbperez808

  • Newbie
  • *
  • Posts: 13
    • View Profile
Thanks for that tip.

There should be a countdown message after the first CTRL-C telling people that it is saving its internal state to disk.

Even on my modern i7 + SSD equipped machine, the clean shutdown takes around 10 minutes from CTRL-C to a proper exit and there is no clear indication that a clean shutdown is progressing.
« Last Edit: July 02, 2017, 07:03:49 pm by jbperez808 »

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
The link you quoted is for the old BTS-1.0 chain, I think.

Killing the witness_node with CTRL-C or sending SIGTERM will make it save its internal state to disk. Upon restart, it checks the disk contents, loads the data and resumes its operation.

You have to give it time to save the database. Don't hit CTRL-C more than once, and don't send SIGKILL.
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline jbperez808

  • Newbie
  • *
  • Posts: 13
    • View Profile
In

https://bitsharestalk.org/index.php/topic,8960.msg116880.html#msg116880

it says "if you kill BitShares, it will assume it crashed and offer to nuke the database for you when it starts up again. This is strictly optional, you do not have to do it; just click the "Continue Normally" button and it won't rebuild the database unless it detects corruption in it."

But when I run witness_node there's no such option. and I have to go through the long processo of what seems to be rebuilding the object database every time I stop witness_node via CTRL-C and restart.

What is the proper way to shutdown and/or avoid the long restart?