Parent process not found error

Node Running
1

I encountered an error that I cannot resolve, and I have tried multiple methods without success

/tcp/40019"}
Jul 30 12:34:30 m release_autorun.sh[1402464]: Signature check passed
Jul 30 12:34:30 m release_autorun.sh[1402464]: {"level":"info","ts":1722342870.6469855,"caller":"rpc/data_worker_ipc_server.go:92","msg":"data worker listening","address":"/ip4/127.0.0.1/tcp/40022"}
Jul 30 12:34:34 m release_autorun.sh[1402416]: [395B blob data]
Jul 30 12:35:04 m release_autorun.sh[1402711]: {"level":"error","ts":1722342904.5535815,"caller":"rpc/data_worker_ipc_server.go:125","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:125"}
Jul 30 12:35:04 m release_autorun.sh[1402438]: {"level":"error","ts":1722342904.5575879,"caller":"rpc/data_worker_ipc_server.go:125","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:125"}
Jul 30 12:35:04 m release_autorun.sh[1402452]: {"level":"error","ts":1722342904.5767536,"caller":"rpc/data_worker_ipc_server.go:125","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:125"}
Jul 30 12:35:04 m release_autorun.sh[1402436]: {"level":"error","ts":1722342904.6016185,"caller":"rpc/data_worker_ipc_server.go:125","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:125"}
2

Hey thanks for making this bug report! I edited it a bit to make it more legible.

Could you share some more info? Did this happen after the v1.4.21.1 release? Which version of the release_autorun.sh script are you using (git branch/are there any modifications to it)?

1 Like
3

Before the release of v1.4.21.1, this issue had also occurred, and at that time the node couldn’t resolve it, so I had to shut it down. Now that I have updated to the latest version, this issue has appeared again.

4

I’m sorry you’re experiencing this problem. Unfortunately it’s difficult to help without knowing more about your setup. Does restarting the node fix the issue?