node stopped getting new blocks at 7083588
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- docker, docker-compose, shell, ubuntu
调研方向
从 Docker Compose 配置以及报告中的 op-node 和 healthcheck 日志入手,重点关注区块 7083589 处的 invalid payload 和 protocol error。比较报告中描述的 execution 和 beacon 配置,并复现同步失败;完成的标准是确定 node 拒绝该区块的原因,并记录或验证一个可继续同步的修复方案。
由索引模型根据 Issue 内容生成。
描述
Node stopped getting new blocks at 7083588 (Wed Feb 26 2025 14:59:59 GMT+0000 (UTC)
I did upgrade the docker images with the newest in v.1.2.0 a day before needed (I triple checked everything).
We are atleast 3-4 dudes on Ink's dev-general channel on discord, that experienced the same problem.
I have tried restarting docker compose, also completely removing the instance with "docker compose down -v" and let it resync from scratch with and without the rock torrent download thingy. even with other settings than archive, like full and snap (snap is still syncing though) - but archive, after it has finished downloading and begun to catch up, it always keeps around ~43329 blocks behind the official top.
I have tried different L1-rpc's for execution and beacon, usually I use my own local hosted (nethermind, reth, lighthouse), but I have also tried online services like chainstack for a full unpruned beacon node.
software: ubuntu 22 lxc-container on proxmox, and followed the guide on this github.
errors:
protocols not supported: [/opstack/req/payload_by_number/57073/0]
healthcheck-1 | {"level":30,"time":1740640127229,"targetHeight":7098275,"referenceHeight":7141714,"heightDifference":43439,"minBlockNumber":7098275,"msg":"latest block heights"}
healthcheck-1 | {"level":50,"time":1740640127448,"extra":{"blockNumber":7098275,"referenceHash":"0xeafdc9982d3aef8529fdfe6a01fdd58527cdcbc20f0c612d6e5a276ab0264577","targetHash":"0xb7567a7e6907d1767778d043f2c80f0b95eaf7b5ebfbf816e4fea06fe8798224"},"msg":"reference client has different hash for block"}
healthcheck-1 | {"level":30,"time":1740640127448,"msg":"beginning binary search to find first mismatched block"}
op-node-1 | t=2025-02-27T08:02:38+0000 lvl=warn msg="L1 head signal indicates a possible L1 re-org" old_l1_head=0x2a8eefb8c0d5c16116fe3778e0ab44a85b27594c9f252104d8cc5a1656420ed3:21936344 new_l1_head_parent=0x3a56745e071a91f12c88ce52c919dc4d43a6cd49da6ef3fee81fe2b48d086708 new_l1_head=0x91fec02644b1bc1bd05a15543254ce283d360a40de455fd9e4e7eb5c7cec669c:21936346
op-node-1 | t=2025-02-27T08:02:40+0000 lvl=warn msg="dropping future span batch" origin=0x52c65466f01c6181e1bbf61285390818c8b1b19d55fa0a3ec86f8c7d87692358:21934660 epoch=0x74bae72d1bc891c1cf4ee2a7f4bc42b07767d3ffef2f43ba1b22c882bae4f60a:21932561 batch_type=SpanBatch batch_timestamp=1740617012 parent_check=0xe5afc7ab0f1e97e4ba9a53684b76fe915d541938 origin_check=0x8f42a6f7d0b0c3c66d194bd0d623221a932c04ea start_epoch_number=21934159 end_epoch_number=21934160 block_count=10 txs=0 next_timestamp=1740597671
op-node-1 | t=2025-02-27T08:02:40+0000 lvl=warn msg="Dropping invalid span batch, flushing channel" origin=0x52c65466f01c6181e1bbf61285390818c8b1b19d55fa0a3ec86f8c7d87692358:21934660 epoch=0x74bae72d1bc891c1cf4ee2a7f4bc42b07767d3ffef2f43ba1b22c882bae4f60a:21932561 batch_type=SpanBatch batch_timestamp=1740617012 parent_check=0xe5afc7ab0f1e97e4ba9a53684b76fe915d541938 origin_check=0x8f42a6f7d0b0c3c66d194bd0d623221a932c04ea start_epoch_number=21934159 end_epoch_number=21934160 block_count=10 txs=0
op-node-1 | t=2025-02-26T15:12:39+0000 lvl=warn msg="Dropping invalid unsafe payload" hash=0xe614f2437ad350142a3a461e2b299579efd00a650b74db3cf86ed87a5f3482aa number=7083589 timestamp=1740582000
op-node-1 | t=2025-02-26T15:12:39+0000 lvl=warn msg="Payload was invalid" block=0xe614f2437ad350142a3a461e2b299579efd00a650b74db3cf86ed87a5f3482aa:7083589 err="execution payload 0xe614f2437ad350142a3a461e2b299579efd00a650b74db3cf86ed87a5f3482aa:7083589 was INVALID! Latest valid hash is <nil>, ignoring bad block: 0xc011d16080" timestamp=1740582000
op-node-1 | t=2025-02-26T15:12:39+0000 lvl=warn msg="Engine temporary error" err="temp: cannot process unsafe payload: new - 0xe614f2437ad350142a3a461e2b299579efd00a650b74db3cf86ed87a5f3482aa:7083589; parent: 0x8362847a2fbd7e0291892836c1761af953ad3979abd2e3d9ca1972e387bae502:7083588; err: execution payload 0xe614f2437ad350142a3a461e2b299579efd00a650b74db3cf86ed87a5f3482aa:7083589 was INVALID! Latest valid hash is <nil>, ignoring bad block: 0xc011d16080"
- 主要语言
- Shell
- 星标
- 36.4k
- 派生
- 643
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
inkonchain/node 的其他 Issue
-
Shell scripts initially in CRLF instead of LF (causing execution issues on Linux)可能已有人在做 @Kewe63 于 24 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
inkonchain/node#73 · 1 条评论 ·
-
How do I actually run an Ink mainnet node right now?可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 5/5 一周以上 新手友好度 25/100
inkonchain/node#87 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 45/100
inkonchain/node#84 · 1 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 38/100
inkonchain/node#79 ·
-
test未关闭
难度 5/5 一周以上 新手友好度 5/100
inkonchain/node#75 ·
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
aws-samples/appmod-blueprints#972 ·
维护者通常 1 天内回复
-
status:needs-triage
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
out-of-date
难度 2/5 1-3 小时 新手友好度 62/100
CachyOS/CachyOS-PKGBUILDS#1965 ·
维护者通常 1 天内回复
-
enhancement good first issue help wanted
难度 2/5 1-3 小时 新手友好度 82/100
Sorogate/example-consumer#14 ·