Closed kf106 closed 6 years ago
Thanks. If you stop the node and remove the blockchain directory, then connect again as if it had never seen the network before, does the segmentation fault occur reliably?
I deleted the cloud instance that setup the node. I've tried to reproduce the error (I got it two time out of three with the first setup). However, I now have a suspicion of what might have happened:
keir@chainfrog-nitro:~/.multichain$ multichaind frogchain
MultiChain 2.0 alpha 5 Daemon (latest protocol 20004)
Chain frogchain already exists, adding f to list of peers
Other nodes can connect to this node using:
multichaind frogchain@192.168.8.104:8882
Listening for API requests on port 8881 (local only - see rpcallowip setting)
Node ready.
multichaind: pthread_create.c:430: start_thread: Assertion `freesize < pd->stackblock_size' failed.
Aborted (core dumped)
keir@chainfrog-nitro:~/.multichain$ multichaind frogchain@f
That last line is me hitting cursor-up. I recalled the first command (multichaind frogchain@frogchain.multidasher.org:8882
) and backspaced to the @. At least, it looked like I had. But the terminal wasn't displaying correctly. So terminal fault rather than MultiChain fault.
I suspect this is the issue, so I'd put this on ice. If it happens again I'll be more thorough.
OK, that explains it, because this assertion is nowhere to be found in the MultiChain source code!
Error:
OS: Ubuntu 18.04
Version: Multichain 2.0.5
Params.dat file:
Notes: Chain contains a native currency, and has anyone-can-connect/send/receive set to true.
multichain-cli frogchain getinfo returns: error: couldn't connect to server
Node was started with
multichaind frogchain
i.e. not as a daemon.Running the command again didn't give a segmentation fault.