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

Grin - Connected Peers < 5 #2597

Closed
alienninja opened this issue Feb 19, 2019 · 2 comments
Closed

Grin - Connected Peers < 5 #2597

alienninja opened this issue Feb 19, 2019 · 2 comments

Comments

@alienninja
Copy link

Describe the bug
Was having issues with my Chain Height not increasing to the Header Chain Height.
I would have peers, but eventually they would go to 0.
I tried removing the chain_data/peer directory, but that did not change the behavior.
I then removed the entire chain_data directory, and it started to work, however after about
2 hours, I'm still at 4 peers and Status "Preparing chain state for validation, step 3/4" This was after restarting Grin because it hung on downloading the chain.

To Reproduce
Steps to reproduce the behavior:

  1. Clean reboot of system
  2. Run 'grin server start'
  3. Run 'grin'

Relevant Information
grin_server.log attached.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Version [e.g. 1.0.1]
    Linux 4.15.0-45-generic WIP: Tracking Transaction Pool Implementation #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
    Additional context
    Note I am also mining on this server with bminer

Also, should I be running both "grin" and "grin server start" ? On reboot, I send "grin" to screen, and just run grin server start, then start my mining as well as start the wallet listener.

Thanks
grin-server.log

@antiochp
Copy link
Member

I believe grin by default runs grin server run.

So you should definitely not be running grin server start alongside this as this will cause multiple grin processes to be potentially writing to the same backend db and files.

@hashmap
Copy link
Contributor

hashmap commented Feb 24, 2019

Agree, it has nothing to with number of peers (4 is low but enough to get a node synced), you corrupt your chain data by running 2 instances of grin. It will be fixed soon (by not allowing the second process to start)
Closing for now.

@hashmap hashmap closed this as completed Feb 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants