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
Node is syncing and accessible and there are no errors like that in logs: Apr 15 20:28:00 ip-10-10-0-1 geth[15961]: WARN [04-15|20:28:00.398] Served eth_getBlockByNumber conn=127.0.0.1:38060 reqid=1104250 t=10.007163615s err="context canceled"
Actual behaviour
a node can't be reached(Read timed out) and in logs I can see only these lines: Apr 15 20:28:00 ip-10-10-0-1 geth[15961]: WARN [04-15|20:28:00.398] Served eth_getBlockByNumber conn=127.0.0.1:38060 reqid=1104250 t=10.007163615s err="context canceled"
After a restart, the problem disappears
Steps to reproduce the behaviour
Run geth version 1.9.12-stable with light syncmode
System information
Geth version: 1.9.12-stable
OS & Version: Linux
Expected behaviour
Node is syncing and accessible and there are no errors like that in logs:
Apr 15 20:28:00 ip-10-10-0-1 geth[15961]: WARN [04-15|20:28:00.398] Served eth_getBlockByNumber conn=127.0.0.1:38060 reqid=1104250 t=10.007163615s err="context canceled"
Actual behaviour
a node can't be reached(Read timed out) and in logs I can see only these lines:
Apr 15 20:28:00 ip-10-10-0-1 geth[15961]: WARN [04-15|20:28:00.398] Served eth_getBlockByNumber conn=127.0.0.1:38060 reqid=1104250 t=10.007163615s err="context canceled"
After a restart, the problem disappears
Steps to reproduce the behaviour
Run geth version 1.9.12-stable with light syncmode
Backtrace
The text was updated successfully, but these errors were encountered: