Bible Pay

Read 64 times

  • oncoapop
  • Newbie

    • 28


    • 3
    • October 23, 2018, 12:31:17 pm
    more
Sanctuary suddenly come into an expired state
« on: March 28, 2019, 01:54:43 am »
My Sanctuary's status is "WATCHDOG EXPIRED" and I noticed that vin appears corrupted.

sanc1$ biblepay-cli masternode status
{
  "vin": "CTxIn(COutPoint(ddc40fa9f1f69496c66557ebaabdb3706c61d4cd4060ee401bfe5ce6f5f874c6, 1), scriptSig=)",
  "service": "45.62.239.188:40000",
  "payee": "BLLXYpT4cjN5gtmrS3s6Fp4ZufYyy629kY",
  "status": "Masternode successfully started"
}
sanc1$ ./watchman.py
biblepayd not synced with network! Awaiting full sync before running watchman.

biblepay-cli masternode list showed many with WATCHDOG_EXPIRED when I reported this observation but now only two (so it appears to be transient) and resolved by itself.

Restarted sanctuary and it is now in PRE_ENABLED state (only one in the network) and watchman.py does not give any output (assume ok)

biblepay-cli masternode status
{
  "vin": "CTxIn(COutPoint(ddc40fa9f1f69496c66557ebaabdb3706c61d4cd4060ee401bfe5ce6f5f874c6, 1), scriptSig=)",
  "service": "45.62.239.188:40000",
  "payee": "BLLXYpT4cjN5gtmrS3s6Fp4ZufYyy629kY",
  "status": "Masternode successfully started"

output still the same as before, although state is PRE_ENABLED.