-
Notifications
You must be signed in to change notification settings - Fork 20.3k
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
segfault when running geth on a server for a couple of hours. #14800
Comments
We kind of need the beginning of the logs especially, that contains the crashing goroutine. I've been running Geth for quite extensively (weeks without restarts) and didn't see an issue until now. If it happens again, could you get us the first few hundred lines of the crash log? That's the most interesting part. |
This appears to be identical to #14552 |
I've had this trip on me a couple times over the past few days. I've dumped the log in its entirety from the process in this gist. I've been running the docker alpine version posted publicly, and I've been starting it up with this command:
Edit: I realized a gist isn't large enough to hold the entire log, so it's been split continuously over three files, all still in the same gist. |
@linas Sorry I looked at all of them and this was the most recently updated one. Assumptions make fools of us all :) I appreciate you bumping the other thread with this information. |
Closing this issue being the same as #14552 |
System information
Geth version:
Geth
Version: 1.6.7-stable
Git Commit: ab5646c
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.8.1
Operating System: linux
GOPATH=
GOROOT=/usr/lib/go-1.8
OS & Version: Linux kfir-Z10PE-D8-WS 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Steps to reproduce the behaviour
Run geth and a large server for a couple of hours.
Backtrace
Note that this is only a partial backtrace due to the large number of co-routines running.
The text was updated successfully, but these errors were encountered: