Unable to access node dashboard on my local network and my node is down

Node Operators troubleshooting
1

Hello There,

Since last few days my node is down, it shows me my port is closed 28967 and 14002. Eventhough I haven’t change anything in my router configuration. Also I am not able to access node dashboard. Since last two year it was working fine but suddenly it stopped working.

In port closed/open checker tool shows port is closed but my ISP told we haven’t blocked anything from end.

Can you help me what exactly the issue is?

Thanks.

2

Then start the node and only then the ports will be open

3

I tried with restart my system but I am unable to do that.

4

Docker? windows? logs?
drive type?

you propably have a fatal error somewhere in the logs.
AV deleted storagenode? drive correctly mounted?
hardware?

You have only 12 days in total per month to be offline, then follows disqualifikation.

5

how can I find logs?

6

2024-01-17T07:59:54Z INFO Running on version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.94.2”}

2024-01-17T07:59:54Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}

2024-01-17T07:59:55Z INFO Command output. {“Process”: “storagenode-updater”, “Output”: “”}

2024-01-17T07:59:55Z ERROR Error updating service. {“Process”: “storagenode-updater”, “Service”: “storagenode”, “error”: “fork/exec /app/storagenode: exec format error”, “errorVerbose”: “fork/exec /app/storagenode: exec format error\n\tmain.update:19\n\tmain.loopFunc:27\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tmain.cmdRun:136\n\tstorj.io/private/process.cleanup.func1.4:393\n\tstorj.io/private/process.cleanup.func1:411\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomOptions:112\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:77\n\tmain.main:20\n\truntime.main:267”}

2024-01-17T07:59:55Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.94.2”}

2024-01-17T07:59:55Z INFO New version is being rolled out but hasn’t made it to this node yet {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}

2024-01-17 07:59:56,649 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-01-17 07:59:56,653 INFO spawned: ‘storagenode’ with pid 31

2024-01-17 07:59:56,654 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

supervisor: couldn’t exec /app/storagenode: ENOEXEC

supervisor: child process was not spawned

2024-01-17 07:59:56,663 INFO exited: storagenode (exit status 127; not expected)

2024-01-17 07:59:58,669 INFO spawned: ‘storagenode’ with pid 32

supervisor: couldn’t exec /app/storagenode: ENOEXEC

supervisor: child process was not spawned

2024-01-17 07:59:58,681 INFO exited: storagenode (exit status 127; not expected)

2024-01-17 08:00:01,689 INFO spawned: ‘storagenode’ with pid 33

supervisor: couldn’t exec /app/storagenode: ENOEXEC

supervisor: child process was not spawned

2024-01-17 08:00:01,702 INFO exited: storagenode (exit status 127; not expected)

7

Here is the last 20 logs I found using this ```
docker logs --tail 20 storagenode

8

Please try to stop and remove the container

docker stop -t 300 storagenode
docker rm storagenode

delete the image

docker rmi storjlabs/storagenode:latest

then pull it again

docker pull storjlabs/storagenode:latest

after that run it back with all your parameters.
By the way, could you please show your docker run command? You may mask your private information.

9

Yes drive is correctly mounted as I can start my computer and access other things on my computer.

10

I am not getting what it means?

11

Accordingly logs you used a docker version. So to run the container you need to specify all mandatory parameters like mount paths, wallet or address, see: Storage Node - Storj Docs

12

root@arya:/home/arya# docker run

“docker run” requires at least 1 argument.

See ‘docker run --help’.

Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG…]

Run a command in a new container

I am getting this after I followed all the commands which you have shared.

13

You need to provide ALL options in your docker run command, see a documentation above.

14

Okay let me set all the info

15

I have set all the info and run that command again.

16

@Alexey Thanks. Issue fixed.

1 Like