Hello, Today my node started crashing during startup, it’s displaying the following log, which seems to be something related to updates: 2024-11-29T15:52:20Z ERROR Error updating service. 2024-11-29T15:52:19Z INFO Configuration loaded {"Process": "storagenode-updater", "Location": "…

Could you please remove the bin subfolder from the data location and then try to run the node?

It is a intel NUC with a i5 processor

How much RAM does this NUC have ?

Yeah I’d grep dmesg or /var/log/syslog (or whereever system messages are for your distro) for “oom” messages.

RAM Memory is 16GB, almost 2GB being used, I don’t think it’s the computer, because I have another storagenode running in the same machine, but different HDD, and is doing good. [image]

[image] Dreiker: but different HDD, and is doing good. If HDD cannot keep up with IO the node will attempt to buffer the io, run out of ram, and get killed. While doing so it will evict filesystem caches, further destroying performance and dying faster. The solution here is to not use solita…

[image] Dreiker: RAM Memory is 16GB, Try the --memory docker option for this node. [image] Updates on Test Data Announcements Yeap, this is why we suggest to use a --memory docker option… See Just use the value, which you have after the OS is fully booted: free…

Please search for FATAL or Unrecoverable errors in the node’s logs (seems you have redirected them).

Here is the full log: 2024-11-30T12:23:42Z INFO Configuration loaded {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"} 2024-11-30T12:23:42Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.email"} 2024-11-30T12:23:42Z …

Storagenode crashing during startup

Node Operators FAQ

nerdatwork November 29, 2024, 5:27pm 8

Try the --memory docker option for this node.