Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

node: failed to start: header/p2p: failed to open a new stream: protocols not supported: [/mocha/header-ex/v0.0.3] #2327

Closed
bert2002 opened this issue Jun 6, 2023 · 1 comment
Closed

node: failed to start: header/p2p: failed to open a new stream: protocols not supported: [/mocha/header-ex/v0.0.3] #2327

bert2002 opened this issue Jun 6, 2023 · 1 comment
Labels
external Issues created by non node team members needs:triage

Comments

@bert2002
Copy link

bert2002 commented Jun 6, 2023 

          Hi,

we are seeing a problem when we want to sync with v0.10.3 on mocha. We run it in docker with

celestia full start --core.ip rpc-mocha.pops.one --gateway --gateway.addr 0.0.0.0 --gateway.port 26659 --p2p.network mocha

and experience following issue:

Jun 05 11:32:59 node systemd[1]: Started celestia.service.
Jun 05 11:32:59 node celestia[32404]:  Network celestia_default  Creating
Jun 05 11:33:00 node celestia[32404]:  Network celestia_default  Created
Jun 05 11:33:00 node celestia[32404]:  Container celestia-celestia-1  Creating
Jun 05 11:33:00 node celestia[32404]:  Container celestia-celestia-1  Created
Jun 05 11:33:00 node celestia[32404]: Attaching to celestia-celestia-1
Jun 05 11:33:01 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:01.332Z        INFO        node        nodebuilder/module.go:22        Accessing keyring...
Jun 05 11:33:01 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:01.335Z        WARN        module/gateway        gateway/module.go:25        Gateway is enabled, however gateway endpoints are not authenticated. Use with caution!
Jun 05 11:33:01 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:01.354Z        INFO        badger        v2@v2.2007.4/levels.go:183        All 0 tables opened in 0s
Jun 05 11:33:01 node celestia[32404]: celestia-celestia-1  |
Jun 05 11:33:01 node celestia[32404]: celestia-celestia-1  | 2023/06/05 11:33:01 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
Jun 05 11:33:01 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:01.603Z        INFO        module/header        header/config.go:58        No trusted peers in config, initializing with default bootstrappers as trusted peers
Jun 05 11:33:01 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:01.615Z        INFO        header/p2p        p2p/exchange.go:84        client: starting client        {"protocol ID": "/mocha/header-ex/v0.0.3"}
Jun 05 11:33:01 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:01.615Z        INFO        fraudserv        fraudserv/helpers.go:29        joining topic        {"id": "/mocha/fraud-sub/badencoding/v0.0.1"}
Jun 05 11:33:01 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:01.615Z        INFO        fraudserv        fraudserv/service.go:97        starting fraud proof service        {"protocol ID": "/mocha/fraud/v0.0.1"}
Jun 05 11:33:02 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:02.608Z        INFO        share/discovery        discovery/discovery.go:254        discovering peers        {"want": 5}
Jun 05 11:33:04 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:04.584Z        INFO        share/discovery        discovery/discovery.go:300        discovered wanted peers        {"amount": 5}
Jun 05 11:33:04 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:04.990Z        INFO        share/discovery        discovery/discovery.go:300        discovered wanted peers        {"amount": 6}
Jun 05 11:33:06 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:06.584Z        INFO        basichost        basic/natmgr.go:93        DiscoverNAT error:no NAT found
Jun 05 11:33:07 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:07.010Z        INFO        canonical-log        swarm/swarm_dial.go:500        CANONICAL_PEER_STATUS: peer=12D3KooWJPvkxWQzJYnaiVQMgrXTuJzvExvhQRbwuQg5aRdKT4yA addr=/ip4/85.239.239.131/udp/2121/quic-v1 sample_rate=100 connection_status="established" dir="outbound"
Jun 05 11:33:08 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:08.281Z        INFO        canonical-log        swarm/swarm_dial.go:500        CANONICAL_PEER_STATUS: peer=12D3KooWGpNJx4iSahk1HC34qj7DLtH2yn3KaaTSnwNCstMk3jiA addr=/ip4/89.117.57.31/udp/2121/quic-v1 sample_rate=100 connection_status="established" dir="outbound"
Jun 05 11:33:13 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:33:13.502Z        INFO        canonical-log        swarm/swarm_dial.go:500        CANONICAL_PEER_STATUS: peer=12D3KooWEvcLVzhzBbegE8ot8LsA514vXjrkzDiNWq1mVbysXZkv addr=/ip4/84.115.217.205/udp/45637/quic-v1 sample_rate=100 connection_status="established" dir="outbound"
Jun 05 11:34:09 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:34:09.139Z        INFO        dagstore        dagstore@v0.0.0-20230413141458-735ab09a15d6/dagstore_control.go:48        dagstore closed
Jun 05 11:34:09 node celestia[32404]: celestia-celestia-1  | 2023-06-05T11:34:09.146Z        INFO        badger        v2@v2.2007.4/db.go:1027        Storing value log head: {Fid:0 Len:29 Offset:1650}
Jun 05 11:34:09 node celestia[32404]: celestia-celestia-1  |
Jun 05 11:34:09 node celestia[32404]: celestia-celestia-1  | Error: node: failed to start: header/p2p: failed to open a new stream: protocols not supported: [/mocha/header-ex/v0.0.3]
Jun 05 11:34:09 node celestia[32404]: celestia-celestia-1 exited with code 0
Jun 05 11:34:09 node celestia[32785]:  Container celestia-celestia-1  Stopping
Jun 05 11:34:09 node celestia[32785]:  Container celestia-celestia-1  Stopping
Jun 05 11:34:20 node celestia[32785]:  Container celestia-celestia-1  Stopped
Jun 05 11:34:20 node celestia[32785]:  Container celestia-celestia-1  Removing
Jun 05 11:34:20 node celestia[32785]:  Container celestia-celestia-1  Removed
Jun 05 11:34:20 node celestia[32785]:  Network celestia_default  Removing
Jun 05 11:34:20 node celestia[32785]:  Network celestia_default  Removed
Jun 05 11:34:20 node systemd[1]: celestia.service: Succeeded.

This is causing the container to stop and needs to be restarted (though same problem happens again).

Any advice or more information are needed?

Thanks,
bert

Originally posted by @bert2002 in #2176 (comment)
@github-actions github-actions bot added needs:triage external Issues created by non node team members labels Jun 6, 2023
@jcstein
Copy link
Member

jcstein commented Jun 6, 2023

mocha is not supported on v0.10.3, which would cause expected issues. we’re in the process of upgrading mocha to a more recent version, as it’s currently behind on celestia-node version (v0.6.4). as for arabica, you’ll need to use v0.11.0-rc2 to use Arabica. this is likely why you were having issues on v0.10.3 for mocha, as it’s not supported, and neither is Arabica

@Wondertan Wondertan mentioned this issue Jul 11, 2023
Closed
@ramin ramin closed this as completed Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
external Issues created by non node team members needs:triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ramin @bert2002 @jcstein