Avoid that seed nodes start a resync from the genesis block

[chimp1984]

A seed node from @Emzy got triggered a resync from genesis which takes a few hours and makes the seed node not fully available in that time.

We should find out what caused that CommunicationException which triggeres the resync. But beside that it seems the strategy to resync in case of 2 errors is not a good one.

We should not trigger a resync from the genesis block in such cases. In case of seed nodes a shut down (and resync from systemd) mighe be an alternative way how to deal with such exceptions.

The incident was not reported by the monitoring, which should be checked why, as in such a resync situation it is expected that the seed node does not serve requests well.

Here are the relevant logs:

Sep-15 10:29:40.490 [BlockNotificationWorker-5366] ERROR c.n.b.d.n.w.BlockNotificationWorker: << getRelatedEntity(..) / CommunicationException: fa
iled to receive block data from 'bitcoind' (hash: '0000000000000000001679d37a895eece3be610ce67c296d04ada6d25c6583e5'), message was: 'Error #100400
4: The operation failed due to an unknown IO exception.' 
Sep-15 10:29:40.491 [BlockNotificationWorker-5366] ERROR c.n.b.d.n.w.NotificationWorker: Throwable at NotificationWorker: e=NotificationHandlerExc
eption(super=com.neemre.btcdcli4j.daemon.NotificationHandlerException: Error #1004005: The operation failed due to an communication exception., er
ror=Errors(code=1004005, message=The operation failed due to an communication exception.), code=1004005), notification=0000000000000000001679d37a8
95eece3be610ce67c296d04ada6d25c6583e5 
Sep-15 10:29:40.492 [BlockNotificationWorker-5366] ERROR b.c.d.n.f.RpcService: NotificationHandlerException(super=com.neemre.btcdcli4j.daemon.Noti
ficationHandlerException: Error #1004004: The operation failed due to an unknown IO exception., error=Errors(code=1004004, message=The operation f
ailed due to an unknown IO exception.), code=1004004) 
Sep-15 10:29:40.498 [SeedNodeMain] ERROR b.c.d.n.f.FullNode: An error occurred: Error=bisq.core.dao.node.full.RpcException: NotificationHandlerExc
eption(super=com.neemre.btcdcli4j.daemon.NotificationHandlerException: Error #1004004: The operation failed due to an unknown IO exception., error
=Errors(code=1004004, message=The operation failed due to an unknown IO exception.), code=1004004) 
Sep-15 10:29:40.500 [SeedNodeMain] ERROR b.c.d.n.f.FullNode: Error type of NotificationHandlerException: Errors(code=1004004, message=The operatio
n failed due to an unknown IO exception.) 
Sep-15 10:29:40.501 [SeedNodeMain] INFO  b.c.d.s.DaoStateSnapshotService: applySnapshot from persistedBsqState daoState with height of last block 
594920 
Sep-15 10:29:40.501 [SeedNodeMain] WARN  b.c.d.s.DaoStateSnapshotService: We applied already a snapshot with chainHeight 594920. We will reset the
 daoState and start over from the genesis transaction again. 
Sep-15 10:29:40.501 [SeedNodeMain] INFO  b.c.d.s.DaoStateService: Apply snapshot with chain height 571747 
Sep-15 10:29:40.513 [SeedNodeMain] INFO  b.c.d.n.BsqNode: Start parse blocks:
   Start block height=571747
   Genesis txId=4b5417ec5ab6112bedf539c3b4f5a806ed539542d8b717e1c4470aa3180edce5
   Genesis block height=571747
   Block height=571747

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[chimp1984]

Still relevant

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

[stale]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.