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

Problems after upgrading to 0.4.8 #92

Closed
hvredevoort opened this issue Oct 15, 2019 · 4 comments
Closed

Problems after upgrading to 0.4.8 #92

hvredevoort opened this issue Oct 15, 2019 · 4 comments

Comments

@hvredevoort
Copy link

I added a new bug report because of update to 0.4.8 but the previous report shows similar errors

Where does the bug occur?
chain

What is your wallet address and your balance?
If it is too private to answer, you can skip it.

Describe the bug
Since update to 0.4.8 I see more sync errors, sync shutting down, broken pipe erros

To Reproduce
Update 0.4.6 to 0.4.8

Expected behavior
no sync errors

Screenshots
Update 0 4 8

** Configuration (please complete the following information):**

  • OS: [e.g. Ubuntu 18.04]
  • cpchain version [e.g. 0.2.3]
    Ubuntu 19.04
    CPChain 0.4.8

Additional context
Add any other context about the problem here.
If your bug can only be reproduced occasionally, please emphasize it.

@hvredevoort
Copy link
Author

Address: 0x42204cC9F4f188A21e90403DC8D21A3F1957dDBd and
0x5019A330Ab801A366A6960Ff960fB1a72031b96b
I also got an impeached block on the first RNode

@hvredevoort
Copy link
Author

I downgraded to 0.4.6 because I got too many errors and no sealed blocks

@alex031029
Copy link
Contributor

The screenshot indicates that the peer your node trying to sync disconnected. Since the cpchain was running in multithreading, many same warnings can pop up in a short time. But all these warning should not bother you from sealing blocks.

We have tested the 0.4.8 version in our pre-production environment, which did not have anything wrong with sealing process. So currently I have no idea why your node cannot seal any blocks running the newest version.

I will keep you updated.

@hvredevoort
Copy link
Author

I reinstalled 0.4.8, did a compact of the database and was able to start again
Just sealed some blocks, so this node is fine now

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

2 participants