Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

op-node errors and shutdown after upgrade

Aperta
  • Qualcosa non va?
#45 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
28/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
devops

Direzione di ricerca

Inizia riproducendo l'upgrade di Sepolia con op-geth v1.101500.0 e op-node v1.11.0, quindi esamina gli errori registrati «L2 reorg» e «invalid payload attributes». Confronta il comportamento e la compatibilità di queste versioni; il lavoro è completato quando viene identificata la causa dell'arresto e viene documentato un percorso di upgrade compatibile e verificato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Hi team!
I tried upgrading our Sepolia node to the latest versions of op-geth (v1.101500.0) and op-node (v1.11.0), which seemed to work fine for some time, but eventually we got some errors that force op-node to shut down.
Are we not supposed to run these versions yet? What do you recommend?

Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="generated attributes in payload queue" txs=1 timestamp=1739478694
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=warn msg="L2 reorg: existing unsafe block does not match derived attributes from L1" err="nil EIP1559Params in attributes but non-nil extraData in block: [0 0 0 0 250 0 0 0 6]" unsafe=0xbc3836b93b8e29a665176384fc01545130a684a13a2b643822cf1272e44f4417:10475398 pending_safe=0x690610986522bc7eb5cd368832489433f8df5a542b3ccb542a76ab12f837e4d7:10475397
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=warn msg="Failed to share forkchoice-updated signal" state="&{HeadBlockHash:0x690610986522bc7eb5cd368832489433f8df5a542b3ccb542a76ab12f837e4d7 SafeBlockHash:0x690610986522bc7eb5cd368832489433f8df5a542b3ccb542a76ab12f837e4d7 FinalizedBlockHash:0x690610986522bc7eb5cd368832489433f8df5a542b3ccb542a76ab12f837e4d7}" err="Invalid payload attributes"
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=warn msg="could not process payload attributes" err="payload attributes are not valid, cannot build block: Invalid payload attributes"
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=error msg="deposit only block was invalid" parent=0x690610986522bc7eb5cd368832489433f8df5a542b3ccb542a76ab12f837e4d7:10475397 err="payload attributes are not valid, cannot build block: Invalid payload attributes"
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=error msg="Critical error" err="failed to process block with only deposit transactions: payload attributes are not valid, cannot build block: Invalid payload attributes"
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x58f14259a1fdcb6dd8442b69be6932bec8dd77e53b7b421906722985c8bacc4c:10479135
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="stopped listening network address" addr=/ip4/0.0.0.0/tcp/9222
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="disconnected from peer" peer=16Uiu2HAmNt6VeSf6Z22VJ4MzyfAi3mbUmjZXTdurnNcGcnmJXqu1 addr=/ip4/217.22.153.182/tcp/30175
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="disconnected from peer" peer=16Uiu2HAmBBC7aADaA9cfMeuHLZLYAdLNwEahKh7kc9WyUrcvPqXz addr=/ip4/35.246.186.81/tcp/9003
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=warn msg="failed p2p sync request" peer=16Uiu2HAmMkoSMbNkaLYWPFCEhFo7ZqnwNFs1U3C88fEZJxJPNXj3 num=10478890 err="failed to read result part of response: stream reset"
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="processing L2 range request" target=10478268 end=0xd5e1f34674dde2deac3c958a92087b5aa765f1d7fad7b8578c8feb657050f7c3:10479088 rangeReqId=18
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="no peers ready to handle block requests for more P2P requests for L2 block history" target=
10478268 end=0xd5e1f34674dde2deac3c958a92087b5aa765f1d7fad7b8578c8feb657050f7c3:10479088 current=10478921
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="disconnected from peer" peer=16Uiu2HAmMkoSMbNkaLYWPFCEhFo7ZqnwNFs1U3C88fEZJxJPNXj3 addr=/ip4/40.160.21.230/tcp/9222
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="disconnected from peer" peer=16Uiu2HAmLst3ByaaMp61DJb23B1bZxUKeYq5kB8a7QJdspYp3APv addr=/ip4/129.213.114.38/tcp/9222
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="stopped P2P req-resp L2 block sync client"
Feb 13 21:33:52 op-node[171952]: t=2025-02-13T21:33:52+0000 lvl=info msg="State loop returned"
Feb 13 21:33:52 systemd[1]: op-node.service: Deactivated successfully.
Feb 13 21:33:52 systemd[1]: op-node.service: Consumed 9.782s CPU time.
Lingua principale
Shell
Stelle
36.4k
Fork
643
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di inkonchain/node

Tutte le issue di inkonchain/node

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.