v0.1.45 stops refreshing mining works after error.

[terrancewong]

What happened?

after an error, node stop refreshing mining works.

log

head-work: 4572920066974532541, work-diff: 19319528017168032                                                                 
Added block to fork seq: 151390, head-seq: 163061, hash: 00000...59183, head-hash: 00000...1f6cb, work: 3978537089019078061, head-work: 4572920066974532541, work-diff: 594382977955454480                                                                
Finished syncing 10 blocks from yIfFGv4 (Cavalieri)                                                                          Starting sync from gqR48I8 (mumu). ours: 163066, theirs: 163112                                                              
Stopping sync from gqR48I8 (mumu) due to /<PATH>/ironfish/src/assert.ts:26                                      throw new Error(message || `Expected value not to be null`)                                                            
            ^                                                                                                                                                                                                                                             
Error: peer.head                                                                                                                 at Function.isNotNull (/<PATH>/ironfish/src/assert.ts:26:13)                                          
    at Syncer.findAncestor (/<PATH>/ironfish/src/syncer.ts:213:12)                                            at Syncer.syncFrom (/<PATH>/ironfish/src/syncer.ts:191:57)                                            
    at Syncer.startSync (/<PATH>/ironfish/src/syncer.ts:149:26)                                               at PeerNetwork.handleNewBlockMessage (/<PATH>/ironfish/src/network/peerNetwork.ts:1274:24)            
    at PeerNetwork.handleGossipMessage (/<PATH>/ironfish/src/network/peerNetwork.ts:654:7)                    at PeerNetwork.handleMessage (/<PATH>/ironfish/src/network/peerNetwork.ts:624:7)                      
    at async Promise.all (index 0)                                                                                               at Event.emitAsync (/<PATH>/ironfish/src/event.ts:69:5)                                               
Peer gqR48I8 (mumu) disconnected (DISCONNECTED) while syncing.                                                               Starting sync from yIfFGv4 (Cavalieri). work: +-19990588409006283, ours: 163066, theirs: 163113                              
Finding ancestor using linear search on last 3 blocks starting at 00000...5327a (163066) from peer yIfFGv4 (Cavalieri) at 163113                                                                                                                          
Found peer yIfFGv4 (Cavalieri) ancestor 00000...5327a, syncing from 163066 -> 163113 (47) after 1 requests                   Requesting 20 blocks starting at 00000...5327a (163066) from yIfFGv4 (Cavalieri)                                             
Peer yIfFGv4 (Cavalieri) disconnected (DISCONNECTED) while syncing.                                                          Starting sync from OqQysCW (xeno-vik). work: +-38876232459699412, ours: 163066, theirs: 163114                               
Finding ancestor using linear search on last 3 blocks starting at 00000...5327a (163066) from peer OqQysCW (xeno-vik) at 1631
14         

new blocks still being added.

Version

v0.1.45

Debug output

Database in use, skipping output that requires database.
Stop the node and run the debug command again to show full output.

Iron Fish version               0.1.45 @ src
Iron Fish library               0.0.22 @ src
Operating system                Linux x64
CPU model(s)                    Intel(R) Xeon(R) CPU E3-1245 v6 @ 3.70GHz
CPU threads                     8
RAM total                       30.78 GiB
Heap total                      4.01 GiB
Node version                    v16.15.0
ironfish in PATH                false
Garbage Collector Exposed       false
Telemetry enabled               false
Node name                       
Block graffiti                  bh9sqoCqIR3rDFstCCCw1g

Relevant log output

No response

Graffiti

bh9sqoCqIR3rDFstCCCw1g

[terrancewong]

no solutions, rolled back to 0.1.44.

[danield9tqh]

Hey @terrancewong what do you mean by the node stopped refreshing? The logs you provided looks like the node continued to sync after the error happened. Did it freeze after those logs or something? Thanks!

[terrancewong]

Stop sending new mining blocks to miner/blockTemplateStream request.

This issue still persists in v0.1.46

[holahula]

Closing due to staleness. If the issue persists in versions 1.0.0+ - please file a new issue