在将 Polkadot 从 v0.9.23 升级到 v0.9.26 后,客户端侧连接出现问题
作者: Chralt98创建于 2022年11月14日更新于 2023年8月24日
标签J2-unconfirmed
2022-11-14 16:54:27.169 INFO tokio-runtime-worker sub-libp2p: [Relaychain] Discovered new external address for our node: /ip4/...
2022-11-14 16:54:27.248 INFO tokio-runtime-worker sub-libp2p: [ Zeitgeist Parachain] Discovered new external address for our node: /ip4/...
The above is shown in the 0.9.23 version. This does not happen after the upgrade to 0.9.26. It's worth to mention, that this messages informs us, that there was a new external address found for **ip4**. After that message, the 0.9.23 version did found peers and sync with them.
We experience client side connection issues after the dependency update to polkadot-v0.9.26 in [this PR](https://GitHub.com/zeitgeistpm/zeitgeist/pull/850). We would like to see, that the local node successfully synchronises with other nodes in the network. This correctly happens with the `polkadot-v0.9.23` version. I need to mention, that we used Moonbeam dependencies of Substrate and a couple of others before. Now we use the official dependencies.
When I started the node for 0.9.23 (which does sync and found peers) and after that the 0.9.26 runtime, the updated version did sync too. But when the 0.9.26 run alone, it did not sync with the outer parachain nodes.
The following logs are noticeable with the 0.9.26 upgrade:
```bash
RUST_LOG=libp2p=trace ./target/debug/zeitgeist --chain=battery_station --tmp --detailed-log-output2022-11-14 17:16:08.423 TRACE tokio-runtime-worker sub-libp2p: [ Zeitgeist Parachain] Ignoring self-reported non-global address /ip4/127.0.0.1/tcp/30334/ws from 12D3KooWEbhud9TrHYtzK2K1fpKeC4PjDu7bKnHTn8QYzyrfBJsK.
2022-11-14 17:16:08.424 TRACE tokio-runtime-worker sub-libp2p: [ Zeitgeist Parachain] Ignoring self-reported non-global address /ip4/192.168.1.3/tcp/30334/ws from 12D3KooWEbhud9TrHYtzK2K1fpKeC4PjDu7bKnHTn8QYzyrfBJsK.
...
2022-11-14 17:17:30.895 TRACE tokio-runtime-worker sub-libp2p: [Relaychain] Libp2p => Failed to reach PeerId("12D3KooWRuwKV1yt6fqPL6hsfPvJQ28pqmmTxNSDxEC4eLKagzjK"): An error occurred while negotiating the transport protocol(s) on a connection: [("/dns/bsr.zeitgeist.pm/tcp/30338/p2p/12D3KooWRuwKV1yt6fqPL6hsfPvJQ28pqmmTxNSDxEC4eLKagzjK", Other(Custom { kind: Other, error: Timeout })), ("/dns/bsr.zeitgeist.pm/tcp/30338/ws/p2p/12D3KooWRuwKV1yt6fqPL6hsfPvJQ28pqmmTxNSDxEC4eLKagzjK", Other(Custom { kind: Other, error: Timeout }))].
...
2022-11-14 17:23:01.013 TRACE tokio-runtime-worker sub-libp2p: [ Zeitgeist Parachain] Libp2p => Failed to reach PeerId("12D3KooWSBj4SXAz1ETTurW5PRAF1abyxXb9APAVs4vqBVr2NjRt"): An error occurred while negotiating the transport protocol(s) on a connection: [("/dns/bsr.zeitgeist.pm/tcp/30337/p2p/12D3KooWSBj4SXAz1ETTurW5PRAF1abyxXb9APAVs4vqBVr2NjRt", Other(Custom { kind: Other, error: Timeout })), ("/dns/bsr.zeitgeist.pm/tcp/30337/ws/p2p/12D3KooWSBj4SXAz1ETTurW5PRAF1abyxXb9APAVs4vqBVr2NjRt", Other(Custom { kind: Other, error: Timeout }))].
...
2022-11-14 17:22:55.965 TRACE ...内容来源: paritytech/substrate