Quote from: SVK Noko on July 18, 2018, 02:40:55 PM

Quote from: Waves Plus on July 18, 2018, 02:12:16 PM

So I've had this happen once before and can't remember what I did to fix it....

After restarting my sancs post-crash, all but one went to "ENABLED" pretty quickly. One has been stuck in "PRE_ENABLED" for about 4-5 hours now. I tried issuing a "start alias" again 90 minutes ago or so to no avail. I can't remember for the life of me how I fixed this before, but I think last time it happened it was "PRE_ENABLED" for something like 18 hours, and wouldn't fix itself...anyone remember what to do with a stuck node?

Do you have the same wallet version on both of them?

WATCHDOG EXPIRED

Stop the biblepay server:
cd biblepay/src
./biblepay-cli stop

Delete 2 files:
   mncache.dat
   mnpayments.dat

Start/reindex biblepay program
   ./biblepayd -daemon -reindex

Wait for the full resync to the latest block. You can check with
   ./biblepay-cli getinfo

Then run:
   ./biblepay-cli masternode status

You should see:
   Masternode successfully started

You can also run masternode list-conf from your controller wallet, the status of the masternode should show Enabled. Also check the status in another wallet under the "All Sanctuaries" tab.

If the above doesn't work within a couple of hours, try rebooting the server/machine and do it all again.