You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yesterday (19 Sept 2024) an automation tried to shut down erigon (running on gnosis) gracefully and didn't succeed after several attempts so it resorted to shut it down not gracefully. Log excerpt is hereby attached. Erigon was running from main, commit f62360c (29Aug). After restart, erigon was able to recover successfully.
That might be a bug (so I used the bug label) or erigon was particularly busy with some heavy internal process. erigon_gnosis_excerpt.txt
The text was updated successfully, but these errors were encountered:
also such bugs hard to reproduce - so, it will be very useful if can grab erigon output (at least 200 first lines of crush and 100 lines of logs before crush) - to understand in which state erigon was.
Yesterday (19 Sept 2024) an automation tried to shut down erigon (running on gnosis) gracefully and didn't succeed after several attempts so it resorted to shut it down not gracefully. Log excerpt is hereby attached. Erigon was running from main, commit f62360c (29Aug). After restart, erigon was able to recover successfully.
That might be a bug (so I used the
bug
label) or erigon was particularly busy with some heavy internal process.erigon_gnosis_excerpt.txt
The text was updated successfully, but these errors were encountered: