Reboot + reSync + full tx index + full address index
...wondering how long this would take on one of those legendary Arm nodes...
2019-09-12 06:07:58.980 [INF] BCHD: Version 0.14.7
Who wants some $BCHD tokens?
OUCH: ☠
TXid output 1eda05622b2f5ce509f396118087e78caceb3d76efc3cb03d142961db3ee2bc9:1 referenced from transaction 000bf24801c9ca1dc8e4e22a20f249601ebdeb8881c7f8aedefbcbdde71f709e:0 does not exist
BCHD reached their flipstarter goal! Congrats!
Apparently,
when BCHD misplaces something ephemeral,
the full-node system needs to be reSYNCed from zero.
This is the second time I have seen it.
Time wasted reSYNCing a full node is insane.
Apparently BCHCTL can quit working permanently:
":~$ bchctl getinfo
Post "https://localhost:8334": dial tcp [::1]:8334: connect: connection refused"
even if rpcuser/pass matches both .conf files
More fun:
...from peer 18.195.144.149:8333 (outbound), code: REJECT_NONSTANDARD, reason: bad-txns-nonfinal
2020-06-06 01:00:34.222 [WRN] PEER: Received reject message from peer 120.79.238.24:8333...
A few notes on the logfiles output by BCHD: