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

Geth 1.8.9 stopped responding #16840

Closed
vogelito opened this issue May 30, 2018 · 3 comments · Fixed by #16843
Closed

Geth 1.8.9 stopped responding #16840

vogelito opened this issue May 30, 2018 · 3 comments · Fixed by #16843

Comments

@vogelito
Copy link

System information

Geth version:

Geth
Version: 1.8.9-stable
Git Commit: ff9b14617e73c07dfa028bc477fe86c1e04d80c5
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.10
Operating System: linux
GOPATH=
GOROOT=/usr/local/go

OS & Version: Linux

Expected behaviour

Node should continue operating

Actual behaviour

Node became unresponsive

Steps to reproduce the behaviour

Unsure. 1.8.9 ran for roughly 24 hours and then it became unresponsive to RPC calls. Log contains some more information.

Backtrace

Log pastebin

@holiman
Copy link
Contributor

holiman commented May 30, 2018

Great that you caught the trace. Very interesting, the trace suggests there's a lock contention in the tx_pool. Thanks!

@karalabe
Copy link
Member

This was a bit unfortunate timing. The bug which (apparently) caused this lockup was already present on master for the entire week last week while you were running the memory tests. I've pushed a fix onto master, will release a hotfix shortly. I really hope this (#16843) was the issue.

@vogelito
Copy link
Author

Thanks for the quick turnaround with this

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

Successfully merging a pull request may close this issue.

3 participants