Help user if a large reorg is detected #161

Open
opened 2 months ago by duke · 0 comments
duke commented 2 months ago
Owner

Example error message from debug.log

2024-02-15 13:23:21 *** A block chain reorganization has been detected that would roll back 1068 blocks!!! This is larger than the maximum of 99 blocks, and so the node is shutting down for your safety.

Reorganization details:
- Current tip: 0002b1b5528b43eff9fcfa6597a1e7ee491f9cb5d4864b4c1ec23d711a23bcd6, height 1099313, work 0000000000000000000000000000000000000000000000000000001abc44d32a

- New tip:     00005b772f6a3bd88b4b5152c447e3e965dfccf38bcacc1c6401be1de852e184, height 1098432, work 0000000000000000000000000000000000000000000000000000001abc452080

- Fork point:  DRAGONX 000045b93bdb8e1a4cdf6455f65263d96dfca327a08451c7ae8f4fc3bf5f5a3c, height 1098245

Please help me, wise human!
if you launch with -maxreorg=1078 it might be able to resolve this automaticallyError: A block chain reorganization has been detected that would roll back 1068 blocks!!! This is larger than the maximum of 99 blocks, and so the node is shutting down for your safety.

Reorganization details:
- Current tip: 0002b1b5528b43eff9fcfa6597a1e7ee491f9cb5d4864b4c1ec23d711a23bcd6, height 1099313, work 0000000000000000000000000000000000000000000000000000001abc44d32a

- New tip:     00005b772f6a3bd88b4b5152c447e3e965dfccf38bcacc1c6401be1de852e184, height 1098432, work 0000000000000000000000000000000000000000000000000000001abc452080

- Fork point:  DRAGONX 000045b93bdb8e1a4cdf6455f65263d96dfca327a08451c7ae8f4fc3bf5f5a3c, height 1098245

Please help me, wise human!

One thing we could do is restart the full node with the recommended -maxreorg CLI option, which would help GUI-only users. This may be challenging to test.

Example error message from debug.log ``` 2024-02-15 13:23:21 *** A block chain reorganization has been detected that would roll back 1068 blocks!!! This is larger than the maximum of 99 blocks, and so the node is shutting down for your safety. Reorganization details: - Current tip: 0002b1b5528b43eff9fcfa6597a1e7ee491f9cb5d4864b4c1ec23d711a23bcd6, height 1099313, work 0000000000000000000000000000000000000000000000000000001abc44d32a - New tip: 00005b772f6a3bd88b4b5152c447e3e965dfccf38bcacc1c6401be1de852e184, height 1098432, work 0000000000000000000000000000000000000000000000000000001abc452080 - Fork point: DRAGONX 000045b93bdb8e1a4cdf6455f65263d96dfca327a08451c7ae8f4fc3bf5f5a3c, height 1098245 Please help me, wise human! if you launch with -maxreorg=1078 it might be able to resolve this automaticallyError: A block chain reorganization has been detected that would roll back 1068 blocks!!! This is larger than the maximum of 99 blocks, and so the node is shutting down for your safety. Reorganization details: - Current tip: 0002b1b5528b43eff9fcfa6597a1e7ee491f9cb5d4864b4c1ec23d711a23bcd6, height 1099313, work 0000000000000000000000000000000000000000000000000000001abc44d32a - New tip: 00005b772f6a3bd88b4b5152c447e3e965dfccf38bcacc1c6401be1de852e184, height 1098432, work 0000000000000000000000000000000000000000000000000000001abc452080 - Fork point: DRAGONX 000045b93bdb8e1a4cdf6455f65263d96dfca327a08451c7ae8f4fc3bf5f5a3c, height 1098245 Please help me, wise human! ``` One thing we could do is restart the full node with the recommended -maxreorg CLI option, which would help GUI-only users. This may be challenging to test.
duke added the
feature
label 2 months ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.