bnb-chain / opbnb-node-docker

36 stars 25 forks source link

failed to fetch unsafe block signing address from system config #11

Closed dachi-nodies closed 1 week ago

dachi-nodies commented 1 month ago

I tried using multiple public endpoints for L1 from documentation however none of them are working. All of them have same error in op-node.

t=2024-08-04T13:08:12+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0xe8e3c50e56d7bf609250829a5555c1919ae60145c058f85f7d4da13f2eb56965: limit exceeded"
t=2024-08-04T13:08:23+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0xeae09bc050f98f6b2269fa9d1ec488c7bd6c7485ce7443c062cd360428cfdfcf: limit exceeded"
t=2024-08-04T13:08:33+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0x6155e87316c1a3ff572e2527d793fff36b08463cb7afc85ef300c8a516c59d44: limit exceeded"
t=2024-08-04T13:08:43+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0xa7ad3b44fc71d650dd76471a0fdf4de7f776caf4020ff23f0020133707175c10: limit exceeded"
t=2024-08-04T13:08:53+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0x6b349bf9da49a2516d335bcd90532974ea913bcae0ce43e1e800319ecc6893e7: limit exceeded"
t=2024-08-04T13:08:53+0000 lvl=eror msg="Error initializing the rollup node" err="failed to init the runtime config: failed to load runtime configuration repeatedly, last error: operation failed permanently after 5 attempts: failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0x6b349bf9da49a2516d335bcd90532974ea913bcae0ce43e1e800319ecc6893e7: limit exceeded"
t=2024-08-04T13:08:53+0000 lvl=warn msg="failed to notify engine driver of L1 head change" err="context canceled"
welkin22 commented 1 month ago

I tried using multiple public endpoints for L1 from documentation however none of them are working. All of them have same error in op-node.

t=2024-08-04T13:08:12+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0xe8e3c50e56d7bf609250829a5555c1919ae60145c058f85f7d4da13f2eb56965: limit exceeded"
t=2024-08-04T13:08:23+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0xeae09bc050f98f6b2269fa9d1ec488c7bd6c7485ce7443c062cd360428cfdfcf: limit exceeded"
t=2024-08-04T13:08:33+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0x6155e87316c1a3ff572e2527d793fff36b08463cb7afc85ef300c8a516c59d44: limit exceeded"
t=2024-08-04T13:08:43+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0xa7ad3b44fc71d650dd76471a0fdf4de7f776caf4020ff23f0020133707175c10: limit exceeded"
t=2024-08-04T13:08:53+0000 lvl=eror msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0x6b349bf9da49a2516d335bcd90532974ea913bcae0ce43e1e800319ecc6893e7: limit exceeded"
t=2024-08-04T13:08:53+0000 lvl=eror msg="Error initializing the rollup node" err="failed to init the runtime config: failed to load runtime configuration repeatedly, last error: operation failed permanently after 5 attempts: failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0x6b349bf9da49a2516d335bcd90532974ea913bcae0ce43e1e800319ecc6893e7: limit exceeded"
t=2024-08-04T13:08:53+0000 lvl=warn msg="failed to notify engine driver of L1 head change" err="context canceled"

@dachi-nodies hi, may I ask what kind of L1 endpoint you are using? It looks like this endpoint has a QPS limit. You might consider adding a line --l1.max-concurrency=1 in the startup command in scripts/op-node-start.sh to limit the concurrency of your requests to the L1 endpoint. Alternatively, consider using a node without QPS limits.

welkin22 commented 1 week ago

Since there has been no activity for a long time, I will close this issue for now. Please feel free to reopen it if necessary.