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.

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

Couldn't connect to any seeds module=p2p #2757

Closed
bobio2018 opened this issue Nov 5, 2018 · 3 comments
Closed

Couldn't connect to any seeds module=p2p #2757

bobio2018 opened this issue Nov 5, 2018 · 3 comments

Comments

@bobio2018
Copy link

@bobio2018 bobio2018 commented Nov 5, 2018

Tendermint version (use tendermint version or git rev-parse --verify HEAD if installed from source):
0.25.0-0c9c3292

ABCI app (name for built-in, URL for self-written if it's publicly available):
Not sure

Environment:

  • OS (e.g. from /etc/os-release):
  • Install tools:
  • Others:
    MacOS High Sierra version 10.13.6

What happened:

When running on single node, I see below error "Couldn't connect to any seeds module=p2p" periodically

What you expected to happen:
Expect no errors?

Have you tried the latest version: yes/no
yes

How to reproduce it (as minimally and precisely as possible):
Running on single node mode

tendermint init
tendermint node --proxy_app=kvstore

Logs (paste a small part showing an error (< 10 lines) or link a pastebin, gist, etc. containing more of the log file):

I[11-05|13:11:57.586] Indexed block                                module=txindex height=10316
I[11-05|13:11:58.485] Ensure peers                                 module=p2p numOutPeers=0 numInPeers=0 numDialing=0 numToDial=10
I[11-05|13:11:58.485] No addresses to dial nor connected peers. Falling back to seeds module=p2p 
E[11-05|13:11:58.485] Couldn't connect to any seeds                module=p2p 
I[11-05|13:11:58.587] Timed out                                    module=consensus dur=997.419ms height=10317 round=0 step=RoundStepNewHeight

Config (you can paste only the changes you've made):

node command runtime flags:

/dump_consensus_state output for consensus bugs

Anything else we need to know:

@zramsay

This comment has been minimized.

Copy link
Contributor

@zramsay zramsay commented Nov 5, 2018

That's expected behaviour since you're running a single node blockchain. Your chain should still be producing blocks, yeah?

@melekes

This comment has been minimized.

Copy link
Collaborator

@melekes melekes commented Nov 5, 2018

@bobio2018 note there's no such thing as "single node" deployment in Tendermint. It only makes sense for local development and trying stuff out as a first time user. We can change the log level from Error to Info however. Do you want to submit a PR?

@bobio2018

This comment has been minimized.

Copy link
Author

@bobio2018 bobio2018 commented Nov 5, 2018

thank you everyone, closing the ticket now.

@bobio2018 bobio2018 closed this Nov 5, 2018
melekes added a commit that referenced this issue Nov 6, 2018
Refs #2757
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.