error: Node didn't shut down normally, performing recovery

Question

I am getting this message after starting daemon for chain

message:

Starting up node...

Other nodes can connect to this node using:
multichaind chainx@169.254.207.242:9543

This host has multiple IP addresses, so from some networks:
multichaind chainx@192.168.56.1:9543
multichaind chainx@10.100.2.102:9543
multichaind chainx@169.254.65.172:9543
multichaind chainx@192.168.48.1:9543
multichaind chainx@192.168.42.1:9543
multichaind chainx@10.10.56.252:9543
multichaind chainx@169.254.193.134:9543

Listening for API requests on port 9542 (local only - see rpcallowip setting)

Node didn't shut down normally, performing recovery

Node ready.

-------------------------------------------------------------------------------------------------------------------------

then, I tried to publish items on streams using publishCommand (in python language)

But after inserting some items, I got this message:-

------------------------------------------------------------------------------------------------

returncode: 1
b'error: Could not connect to the server 127.0.0.1:9542\n\nMake sure the multichaind server is running and that you are connecting to the correct RPC port.\n'

--------------------------------------------------------------------------------------------------

I don't understand why it stopped suddenly. Also, I noticed, the number of items published on stream kept on increasing when the same command was re-run. it is like the total duration of node running time (before stopping) increases each time

Answer 1

If the node is crashing in your particular situation then that is a bug we need to look into. Please start by telling me which version you are running, and looking at the recent lines in the debug.log file in the blockchain directory to see if there's any hint about the cause.