When starting the bridge daemon after it has just been stopped, the syncing does not always seem to trigger. Although the eth client still receives and adds the new blocks, the code which does the IBD does not seem to run. As a result, our own custom code which determines when the bridge is completely synced always thinks the syncing still has to start, meaning it never gets passed this phase and the API is never registered
GlenDC
commented
5 years ago
When starting the bridge daemon after it has just been stopped, the syncing does not always seem to trigger. Although the eth client still receives and adds the new blocks, the code which does the IBD does not seem to run. As a result, our own custom code which determines when the bridge is completely synced always thinks the syncing still has to start, meaning it never gets passed this phase and the API is never registered