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
{{ message }}
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.
The webworker seems to crash and/or hang after running for some time. Currently stuck at 565 DAOs with the most recent being "specialbank", compared to scouts reported 635 with most recent being "violeto"
The text was updated successfully, but these errors were encountered:
lkngtn
changed the title
Webworker crashes
Cannot connect to eth node
Aug 1, 2019
2019-08-01T17:52:07.591130+00:00 app[worker.1]: info: Started
2019-08-01T17:52:08.382943+00:00 app[worker.1]: redux-saga error: uncaught at main
2019-08-01T17:52:08.382959+00:00 app[worker.1]: at main
2019-08-01T17:52:08.382962+00:00 app[worker.1]: at blockFetcher
2019-08-01T17:52:08.382965+00:00 app[worker.1]: Error: CONNECTION ERROR: Couldn't connect to node on WS.
Seems this is due to a failure to connect to the ethnode. Looking at the Infura stats, it appears that this process went way over the daily limit on the 31st, and now is unable to connect.
It also seems like the usage for "catch up" is quite high, but should be significantly lower under normal operation. It may make sense, once initially caught up to create backups to avoid the need to resync fully in the future.
The webworker seems to crash and/or hang after running for some time. Currently stuck at 565 DAOs with the most recent being "specialbank", compared to scouts reported 635 with most recent being "violeto"
The text was updated successfully, but these errors were encountered: