Closed YuXiaoCoder closed 3 months ago
So here are the facts: your node's RPC server is exposed publicly. The gas cap is set to unlimited. So anyone can send arbitrarily complex eth_call requests to your node. Also your admin and personal namespace are exposed. Very bad. It's very easy for someone to stop your RPC server.
Either you or someone else have been sending (it seems) many parallel requests to the node. Some of them heavy too (e.g. last one is taking 400ms). Your setup is asking for it.
However if you do have access to the request bodies I can offer to investigate and see if there is anything in there that can cause a memory blowup.
Answered by @s1na , closing
System information
Geth version:
geth version 1.14.5-stable-0dd173a7
CL client & version:prysm@v5.0.4
OS & Version: Linux DockerExpected behaviour
The nodes are synchronised properly without OOM so that my validator can submit proofs and propose blocks properly
Actual behaviour
The program is killed and the node stops synchronising, causing the block to fall behind
Steps to reproduce the behaviour
I've been running the node normally for over 2 years and this is the first time I've encountered this issue
Backtrace
Many of my nodes went OOM from Sun Jul 21 03:40:00 2024 UTC+8 to Sun Jul 21 04:20:00 2024 UTC+8 with the following node logs: