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
Geth version: v1.101304.2
OS & Version: Linux
Commit hash : (if develop)
Expected behaviour
The node request is normal, and the node situation is also normal during the rpc request.
Actual behaviour
After receiving the request, geth uses very high CPU, causing the program to be killed and the data to be corrupted after restarting the node.
The situation is still the same after trying 2 times, version includes: v1.101305.0-rc.2
Steps to reproduce the behaviour
Backtrace
Dec 27 13:52:04 base-geth[170857]: INFO [12-27|13:52:04.784] Chain head was updated number=8,433,489 hash=72881a..a503f1 root=e5537a..07c421 elapsed="294.52µs"
Dec 27 13:52:17 systemd[1]: base.service: Main process exited, code=killed, status=9/KILL
Dec 27 13:52:17 systemd[1]: base.service: Failed with result 'signal'.
Dec 27 13:52:22 systemd[1]: base.service: Scheduled restart job, restart counter is at 1.
... start node
Dec 27 14:08:54 base-geth[190036]: WARN [12-27|14:08:54.116] State not available, ignoring new payload
Dec 27 14:09:04 base-geth[190036]: WARN [12-27|14:09:04.217] State not available, ignoring new payload
The text was updated successfully, but these errors were encountered:
System information
Geth version: v1.101304.2
OS & Version: Linux
Commit hash : (if
develop
)Expected behaviour
The node request is normal, and the node situation is also normal during the rpc request.
Actual behaviour
After receiving the request, geth uses very high CPU, causing the program to be killed and the data to be corrupted after restarting the node.
The situation is still the same after trying 2 times, version includes: v1.101305.0-rc.2
Steps to reproduce the behaviour
Backtrace
The text was updated successfully, but these errors were encountered: