Relay Node Status goes back to "starting..."

I have the stake pool running in the cloud successfully registered and getting processed TX but relay node randomly goes back to “starting…”. This usually happens after the runs. Is this a problem?

What is your CPU and RAM on the problem relay? Does restarting it help?

Its the 2nd tier on digital ocean with 2vcpu and 4gb of RAM. It syncs backup after leaving it alone for a few minutes. Glive loses connection though.

The issue still persists, my relay node stops syncing and gLive loses connection. When the topology updater runs I get “Invalid Block No”… Do we restart both BP and relay node every time topology updater runs? Any ideas?

I am get this from topology updater:

cardano-cli: Network.Socket.connect: <socket: 11>: does not exist (No such file or directory){ “resultcode”: “502”, “datetime”:“2021-04-23 17:23:24”, “clientIp”: “”, “msg”: “invalid blockNo ” }

That messsge means your node is not synced. Your hw specs may not be sufficient. Upgrading to 8GB Ram should solve the issue. My nodes consistently use 5-6GB.

Thank you Triton-pool that seems to have solved the issue. Nodes are synced and is processing TX. Thanks again!

1 Like