Open gStart9 opened 2 years ago
Tagged support people in case you guys have input. Added Matt for sanity checking / alternative viability / scoping / prior knowledge / further assignment purposes.
Tagged support people in case you guys have input. Added Matt for sanity checking / alternative viability / scoping / prior knowledge / further assignment purposes.
At this time, protocol is to assign the service owner, in this case @dr-bonez I believe, and then you can pass the link on for comment. We want to avoid having multiple assignees. I think this is slated for the v24 update / refresh.
Prerequisites
Describe the Feature Request
Some of our users (including me) are still experiencing this. This feature will allow bitcoind to get out of its endless restart loop. If peers.dat is corrupt when bitcoin starts, it shuts down (presumably usually caused by a power outage/unplugging of the pi while peers.dat is being written). Since embassyd trys to restart stopped containers, bitcoind just goes into and endless restart loop:
Log excerpt from restart loop:
Describe the Use Case
Bitcoin and all other services dependent on bitcoin are dead in the water until peers.dat is deleted and bitcoin can start syncing again.
Describe Preferred Solution
Detect the corrupt peers.dat in the log file, and automatically delete it if it's corrupt. This will require less human intervention and attention, so it's much better than the alternative solution.
Describe Alternatives
"Delete peers.dat" option under Services > Bitcoin Core > Actions