-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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 crashes when submitting transaction. panic: runtime error: invalid memory address or nil pointer dereference #19427
Comments
This is a duplicate of #19427. Is it possible for you to run light clients from the master branch? That should work ok. |
I mean a dup of #19424. |
Thanks, that worked. |
@karalabe I too faced the issue of Geth Crashing with a segmentation fault while submitting the transaction. I raised this issue in #19424 , wherein I was prompted to use the latest master for my client. But I ended up facing the same problem which is faced by @dannieb , i.e. |
We'll release a hotfix for 1.8 to fix this issue. |
Thank you @karalabe |
Master should be fixed now wrt the context canceled. Stable needs a PR to patch the original bug, should hopefully be done in a couple of hours. |
@karalabe I download PPA on |
@karalabe same issue faced from my end |
@karalabe when can we expect hotfix for 1.8 |
This issue has been fixed in #19437, and just shipped in Geth v1.8.26. Please allow half an hour or so for the binaries to be built and pushed out. Sorry for any inconvenience. |
Hi.
We're running geth on light mode with the following configuration:
geth --rpc --rpcapi db,eth,net,web3,personal,txpool --cache=12192 --rpcport 8545 --rpcaddr 0.0.0.0 --rpccorsdomain * --rpcvhosts=* --syncmode light
The process was running fine previously but all of a sudden we're now seeing this exception when a new transaction gets submitted to geth:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xb35640]
goroutine 42 [running]:
github.com/ethereum/go-ethereum/les.(*peer).GetRequestCost(0xc000033ef0, 0xc, 0x1, 0x0)
/home/travis/gopath/src/github.com/ethereum/go-ethereum/les/peer.go:166 +0xa0
github.com/ethereum/go-ethereum/les.(*LesTxRelay).send.func1(0x11f1920, 0xc000033ef0, 0xc015470d01)
/home/travis/gopath/src/github.com/ethereum/go-ethereum/les/txrelay.go:121 +0x4e
github.com/ethereum/go-ethereum/les.(*requestDistributor).nextRequest(0xc0000b2000, 0x0, 0x0, 0x0, 0x0)
/home/travis/gopath/src/github.com/ethereum/go-ethereum/les/distributor.go:195 +0x2b1
github.com/ethereum/go-ethereum/les.(*requestDistributor).loop(0xc0000b2000)
/home/travis/gopath/src/github.com/ethereum/go-ethereum/les/distributor.go:129 +0x7f
created by github.com/ethereum/go-ethereum/les.newRequestDistributor
/home/travis/gopath/src/github.com/ethereum/go-ethereum/les/distributor.go:80 +0xf9
Then the process dies.
When we bring geth back up, a transaction sometimes goes through but we're seeing the process crash on nearly all transactions.
Any ideas?
System information
Geth
Version: 1.8.23-stable
Git Commit: c942700
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.10.4
Operating System: linux
GOPATH=
GOROOT=/usr/lib/go-1.10
The text was updated successfully, but these errors were encountered: