-
Notifications
You must be signed in to change notification settings - Fork 649
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
Segmentation fault when running several witness nodes on the same machine #377
Comments
AFAIK there is a bug which will cause a crash when the chain has too few blocks and another p2p node is trying to connect. It's related to |
same machine. (see bitshares#377)
same machine. (see bitshares#377)
Fixed by #1286. |
Sorry this is after the fact, but I failed to transcribe the email discussions into the Issue Description per standard:
|
My estimation on this issue is 5-10 hours. |
Per converations with Core Team Devs, the invoice for weeks 34-35 reflects 10 hours remitted for this issue. In the future, I will work to ensure estimates are reviewed prior to merge to eliminate discrepancy after the fact. |
Hi all,
I'm trying to setup a local network to play a bit around with the Bitshares software. I've compiled commit 5e67be7 and I copied the
witness_node
executable to somewhere else.Next, I did the following: I created a genesis file with the following command:
./witness_node --create-genesis-json my-genesis.json
and I initialised the data directory:./witness_node --data-dir=data --genesis-json my-genesis.json
and I close the program. Now, I have a data directory which I rename todata-clean
. Next, I have the following bash script to run a witness node with a specific ID:Now I open five ssh sessions to my server and I run the script five times, with five different IDs. Note that node 1 is always the seed node in my experiment. However, after a while, node 1 segfaults. I've attached
gdb
to this process and I get the following stack trace:This issue is reproducible on my server. When I run a modified version of the script, spawning up to 40
witness_node
instances (my server has enough cpu/memory/file descriptor capacity), there is usually one node that segfaults, however, with 40 instances, this is slightly harder to capture using gdb.The output of the crashing witness node looks like this:
Am I doing something wrong here or did I encounter a bug in graphene? I can provide other log files if necessary.
The text was updated successfully, but these errors were encountered: