Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

"You are not connected to any peers. There is most likely some network issue. Fix connectivity." #7556

Closed
wildfunctions opened this issue Jan 14, 2018 · 6 comments
Labels
M2-config 📂 Chain specifications and node configurations. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Milestone

Comments

@wildfunctions
Copy link

wildfunctions commented Jan 14, 2018

I started off running Parity fine, then eventually was only connected to a single peer. This dropped off to 0 peers and now the display shows "You are not connected to any peers. There is most likely some network issue. Fix connectivity."

I'm running:

  • Which Parity version?: Parity/v1.10.0-unstable-e7f3666-20180113/x86_64-linux-gnu/rustc1.23.0
  • Which operating system?: Ubuntu 16.04.1 LTS
  • How installed?: from source
  • Are you fully synchronized?: no
  • Which network are you connected to?: Kovan
  • Did you try to restart the node?: yes

My issues seems to be identical to #6945 which was marked as "Fixed", though there doesn't seem to be a solution shared.

Here is a log of a run attempt with ./target/release/parity --testnet --config testnet_config.toml
parity-testnet.log

Not sure how typical it is to encounter peers with a different genesis block, but it is happening a lot:

genesis hash mismatch (ours: a3c5…2cb9, theirs: b2a5…6659)

@5chdn 5chdn added Z1-question 🙋‍♀️ Issue is a question. Closer should answer. M2-config 📂 Chain specifications and node configurations. labels Jan 16, 2018
@5chdn 5chdn added this to the 1.9 milestone Jan 16, 2018
@5chdn
Copy link
Contributor

5chdn commented Jan 16, 2018

Please remove your nodes.json and try again!

@5chdn 5chdn closed this as completed Jan 16, 2018
@awgneo
Copy link

awgneo commented Jan 19, 2018

I have this issue as well and it requires me having to delete my nodes.json file multiple times per day or else my parity instance becomes unusable. I am on v1.8.6 on Kovan. My instance hovers around 6-9 peers and gradually drops to zero over the course of a few hours. I have a mainnet instance (also v1.8.6) on a cloned setup and it never experiences this issue. I have tried deleting the database and restarting. After the Kovan node syncs, the issue returns.

@wildfunctions
Copy link
Author

@awgneo, this describes exactly my issue. Though deleting the nodes.json file solves the immediate problem, that this emerges so predictively is an issue--the suggested hack/fix is not a sustainable solution. @5chdn, I suggest this issue be reconsidered if problem is not currently known and documented.

@awgneo
Copy link

awgneo commented Jan 19, 2018

I am able to get fully synchronized via warp, however; for me, this problem only manifests itself after warp sync is complete.

@5chdn
Copy link
Contributor

5chdn commented Jan 22, 2018

This is probably the issue #7531

@neelimabhukya
Copy link

You are not connected to any peers. There is most likely some network issue. Fix connectivity.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
M2-config 📂 Chain specifications and node configurations. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Projects
None yet
Development

No branches or pull requests

4 participants