Op bnb node stopped syncing in mainet after network capping in server

[cl-co-dr]

System information

Network: mainnet

if you are running a local node, please provide the following information:
op-node version: ./op-node --version op-node version untagged-44a0fedd-1764150652
op-geth version: op-geth version 0.5.9-stable-54c9f248
OS & Version: Ubuntu

Expected behaviour

Node should sync us usual and keep up with chain head

Actual behaviour

Node has stopped syncing and op-node keeps throwing below error in logs

May 06 16:45:30 a-sgp op-node[720133]: t=2026-05-06T16:45:30+0000 lvl=warn msg="failed to notify engine driver of new L2 payload" err="context deadline exceeded" id=0x545f35d9189055701c5ccf144fcaf49eb310393c95ec1a27a66498ce520a432d:139875698 May 06 16:45:31 a-sgp op-node[720133]: t=2026-05-06T16:45:31+0000 lvl=warn msg="failed to check for unsafe L2 blocks to sync" err="too busy with P2P results/requests: context deadline exceeded" May 06 16:45:33 a-sgp op-node[720133]: t=2026-05-06T16:45:33+0000 lvl=warn msg="failed to notify engine driver of new L2 payload" err="context deadline exceeded" id=0xf98982aa7581224fe50ee4a2130f34f17665ceceee4fad964abdccf517001543:139875697 May 06 16:45:35 a-sgp op-node[720133]: t=2026-05-06T16:45:35+0000 lvl=warn msg="failed to check for unsafe L2 blocks to sync" err="too busy with P2P results/requests: context deadline exceeded" May 06 16:45:37 a-sgp op-node[720133]: t=2026-05-06T16:45:37+0000 lvl=warn msg="failed to check for unsafe L2 blocks to sync" err="too busy with P2P results/requests: context deadline exceeded" May 06 16:45:38 a-sgp op-node[720133]: t=2026-05-06T16:45:38+0000 lvl=warn msg="failed to notify engine driver of new L2 payload" err="context deadline exceeded" id=0x484aeb84b177b5c95894d4bbf60b52b4e4f73e633306fab5473d2fa72939067d:139875695 May 06 16:45:41 a-sgp op-node[720133]: t=2026-05-06T16:45:41+0000 lvl=warn msg="failed to check for unsafe L2 blocks to sync" err="too busy with P2P results/requests: context deadline exceeded" May 06 16:45:42 a-sgp op-node[720133]: t=2026-05-06T16:45:42+0000 lvl=warn msg="failed to notify engine driver of new L2 payload" err="context deadline exceeded" id=0xc12901b6f89b852579291d17d02e3aac7cd3828b40d9b948eac855b0e0bc05f7:139875691

Steps to reproduce the behaviour

Node was running fine for couple of weeks before this. op-geth logs

May 06 16:48:55 a-sgp op-geth[720141]: INFO [05-06|16:48:55.367] loop print db stats database=/root/DRPC/OPBNB/op-geth-data/datadir/geth/chaindata comp_time=1,465,080,797 write_delay_count=0 write_delay_time=0 non_level0_comp_count=39 level0_comp_count=3 May 06 16:48:58 a-sgp op-geth[720141]: INFO [05-06|16:48:58.367] loop print db stats database=/root/DRPC/OPBNB/op-geth-data/datadir/geth/chaindata comp_time=1,465,080,797 write_delay_count=0 write_delay_time=0 non_level0_comp_count=39 level0_comp_count=3 May 06 16:49:01 a-sgp op-geth[720141]: INFO [05-06|16:49:01.368] loop print db stats database=/root/DRPC/OPBNB/op-geth-data/datadir/geth/chaindata comp_time=1,465,080,797 write_delay_count=0 write_delay_time=0 non_level0_comp_count=39 level0_comp_count=3 May 06 16:49:04 a-sgp op-geth[720141]: INFO [05-06|16:49:04.368] loop print db stats database=/root/DRPC/OPBNB/op-geth-data/datadir/geth/chaindata comp_time=1,465,080,797 write_delay_count=0 write_delay_time=0 non_level0_comp_count=39 level0_comp_count=3 May 06 16:49:07 a-sgp op-geth[720141]: INFO [05-06|16:49:07.369] loop print db stats database=/root/DRPC/OPBNB/op-geth-data/datadir/geth/chaindata comp_time=1,465,080,797 write_delay_count=0 write_delay_time=0 non_level0_comp_count=39 level0_comp_count=3

Backtrace

[backtrace]

When submitting logs: please submit them as text and not screenshots.

[Ajes1337]

I also have this problem "too busy with P2P results/requests"

[joey0612]

Noted, I will fix next version.