Node wont start after power outage

Node Operators troubleshooting
,
1

like the post said i lost conection after power outage. My drive re-mounted and i access able but i keep getting error uploading error log please help

sudo docker logs --tail 20 storagenode1
2025-04-03 14:19:01,134 INFO spawned: ‘storagenode’ with pid 52
2025-04-03 14:19:01,136 INFO spawned: ‘storagenode-updater’ with pid 53
2025-04-03T14:19:01Z INFO Anonymized tracing enabled {“Process”: “storagenode-updater”}
2025-04-03T14:19:01Z INFO Running on version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.125.2”}
2025-04-03T14:19:01Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}
2025-04-03T14:19:01Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2025-04-03T14:19:01Z INFO Operator email {“Process”: “storagenode”, “Address”: “kristapher.hunter@yahoo.com”}
2025-04-03T14:19:01Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “0x8Cfb875891565be596bf893519936A587eB4Ee6D”}
2025-04-03T14:19:01Z ERROR failure during run {“Process”: “storagenode”, “error”: “Error opening database on storagenode: open config/storage/trash/.trash-uses-day-dirs-indicator: permission denied”, “errorVerbose”: “Error opening database on storagenode: open config/storage/trash/.trash-uses-day-dirs-indicator: permission denied\n\tmain.cmdRun:69\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272”}
Error: Error opening database on storagenode: open config/storage/trash/.trash-uses-day-dirs-indicator: permission denied
2025-04-03T14:19:01Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode”, “Version”: “v1.125.2”}
2025-04-03T14:19:01Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode”}
2025-04-03 14:19:01,620 WARN exited: storagenode (exit status 1; not expected)
2025-04-03T14:19:01Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.125.2”}
2025-04-03T14:19:01Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
2025-04-03 14:19:01,638 WARN received SIGTERM indicating exit request
2025-04-03 14:19:01,638 INFO waiting for processes-exit-eventlistener, storagenode, storagenode-updater to die
2025-04-03T14:19:01Z INFO Got a signal from the OS: “terminated” {“Process”: “storagenode-updater”}
2025-04-03 14:19:01,641 INFO stopped: storagenode-updater (exit status 0)
2025-04-03 14:19:01,642 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)

2

This is your issue. Check filesystem, paths, mountpoints, and permissions.

1 Like
3

how would i do so???

4

what commands should i use im using linux ubuntu

5

What is specifically your question? What did you try and what did not work?

According to the log you posted the issue with node container (supposedly, you did not say if you use container) being unable to access filesystem properly (permission denied). So you solve it just as any other access related isuse.

  • check filesystem for corruption (because you mentioned power outage, and did not mention whether you have a ups or not)
  • check that the user ID container runs at has permissions to that folder
  • check that mount point to container is correct.

This is out of scope of this forum, it’s a OS specific things, and shall be described in OS manual. But I’d start with ls -al, fschk, and look at container configuration. If you amusing podman — check systemd files. Else — check what user ID are you passing

1 Like