Node Error Forcing Shutdown

So yesterday my node randomly went offline, I wasn’t able to find the logs. Now today I ran the logs after it shutdown again. This is the only ERROR log I could find?

2023-10-02T13:19:39Z    ERROR   piecestore      upload failed   {"process": "storagenode", "Piece ID": "FEQPCSQHL7AUMM4SHOVXTDQY2A5N66ZRWWUKPVR3XCCAF3GH3AMA", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "PUT", "error": "manager closed: unexpected EOF", "errorVerbose": "manager closed: unexpected EOF\n\*Conn).readMsg:225\n\*Conn).Read:171\n\*Reader).ReadPacketUsing:96\n\*Manager).manageReader:226", "Size": 65536, "Remote Address": ""}

Here is a paste of the last 100 logs storjlog -

I also ran docker container ls and noticed that watchtower and storagenode are not running. So I ran the start command for storage node and received this error:

Error response from daemon: failed to start shim: mkdir /run/snap.docker/containerd/daemon/io.containerd.runtime.v2.task/moby/11ed2645b1537b04971867b6e67c346f31017e0f0e264e71bad993977aca2edf: file exists: unknown
Error: failed to start containers: storagenode

I’ve since rebooted my server again and the node is back online. Any idea whats going on?

since there is no fatal error, my guess:

maybe check the ram if it happens more often…

1 Like

Not sure that’s the issue… :frowning:

Is this on a VPS? Or otherwise virtualized? Failure to start shim can sometimes be attributed to the virtual environment having an issue, or a drive space or RAM issue.

1 Like

Thanks for the reply, yes it is a VPS, drive space doesn’t seem to be an issue, I’ll take a look at the RAM since this is the second person alluding to a possible memory issue.

1 Like

Seems you using a snap version of docker. It’s better to uninstall it and use a normal docker instead:

To uninstall the snap version:

sudo snap remove docker

Ah, this is what it was… thank you @Alexey