-
Notifications
You must be signed in to change notification settings - Fork 1.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
Quorum node crashing when running with QBFT #1491
Comments
Hello I am not able to reproduce this on mac m1
Am I missing something?
source of contract
|
Hi @baptiste-b-pegasys,
I had brought up my nodes with
After deploying the contract, I was calling the
This transaction will be in pending status for quite sometime and eventually crash the node. I just retried the steps and could reproduce this at my end.
Please note that one of the node crashes. In first few runs it was always the node from which I had submitted transaction. In another run it was a different node. When the transaction is pending the block number does not increase at the block period interval. |
System information
Geth version: Geth
Version: 1.10.2-stable
Git Commit: 0b0881a
Git Commit Date: 20220822
Quorum Version: 22.7.0
Architecture: amd64
Network Id: 1337
Go Version: go1.18.2
Operating System: darwin
GOPATH=
GOROOT=go
OS & Version: OSX
Commit hash : 0b0881a
Expected behaviour
QBFT consensus working fine without any faulires
Actual behaviour
Node crashed with the below message:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x49d2292]
Steps to reproduce the behaviour
Backtrace
When submitting logs: please submit them as text and not screenshots.
1.log
The text was updated successfully, but these errors were encountered: