Hi! I have three nodes, two of them running fine, third one is permanently crashes with many of such messages in log (i tried to restart node several times):
{“level”:“error”,“ts”:1732106956.318682,“caller”:“rpc/data_worker_ipc_server.go:190”,“msg”:“parent process not found, terminating”,“stacktrace”:“source.quilibrium.com/quilibrium/monorepo/node/rpc.(*DataWorkerIPCServer).monitorParent\n\t/opt/ceremonyclient/node/rpc/data_worker_ipc_server.go:190”}
Also node stops and restarts itself after a time with a such message:
Nov 20 16:02:22 /root/ceremonyclient/node/release_autorun.sh: line 84: 105814 Killed ./node-$version-$release_os-$release_arch
Nov 20 16:02:22 process crashed or stopped. restarting…
also when requesting node info and balance with q1 it says:
panic: error getting node info: rpc error: code = Unavailable desc = connection error: desc = “transport: Error while dialing: dial tcp 127.0.0.1:8337: connect: connection refused”
okay, so you’d need to check the errors before that. The first error:
{“level”:“error”,“ts”:1732106956.318682,“caller”:“rpc/data_worker_ipc_server.go:190”,“msg”:“parent process not found, terminating”,“stacktrace”:“[source.quilibrium.com/quilibrium/monorepo/node/rpc.(*DataWorkerIPCServer).monitorParent](http://source.quilibrium.com/quilibrium/monorepo/node/rpc.(*DataWorkerIPCServer).monitorParent)\n\t/opt/ceremonyclient/node/rpc/data_worker_ipc_server.go:190”}
is the error that prints off when a worker detects that it’s parent process died-- your node process died, it kills your workers-- so this error is not really meaningful other than knowing the error occurred further up.
The second:
Nov 20 16:02:22 /root/ceremonyclient/node/release_autorun.sh: line 84: 105814 Killed ./node-$version-$release_os-$release_arch
Nov 20 16:02:22 process crashed or stopped. restarting…
seems more like an issue with the script killing off your process. I’d update your script (git pull in the ceremonyclient directory) and see if that solves it.
The last doesn’t work because your node isn’t running, which is what spins up the gRPC server that that command relies on to connect to.