Stopped working out of nowhere

Node Operators troubleshooting
,
1 
sudo docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28967:28967/tcp \
    -p 28967:28967/udp \
    -p 127.0.0.1:14002:14002 \
    -e WALLET="0xmy" \
    -e EMAIL="@proton.me" \
    -e ADDRESS=".zapto.org:28967" \
    -e STORAGE="9TB" \
    --user $(id -u):$(id -g) \
    --mount type=bind,source="/home/pi/.local/share/storj/identity/storagenode",destination=/app/identity \
    --mount type=bind,source="/media/pi/my hdd",destination=/app/config \
    --name storagenode storjlabs/storagenode:latest

=

 --metrics.app-suffix string        application suffix. Ignored for certain applications. (default "-release")
  --metrics.event-addr string        address(es) to send telemetry to (comma-separated IP:port or complex BQ definition, like bigquery:app=...,project=...,dataset=..., depends on the config/usage) (default "eventkitd.datasci.storj.io:9002")
  --metrics.event-queue int          size of the internal eventkit queue for UDP sending (default 10000)
  --metrics.instance-prefix string   instance id prefix
  --metrics.interval duration        how frequently to send up telemetry. Ignored for certain applications. (default 1m0s)
  --monkit.hw.oomlog string          path to log for oom notices (default "/var/log/kern.log")
  --tracing.agent-addr string        address for jaeger agent (default "agent.tracing.datasci.storj.io:5775")
  --tracing.app string               application name for tracing identification (default "storagenode")
  --tracing.app-suffix string        application suffix (default "-release")
  --tracing.buffer-size int          buffer size for collector batch packet size
  --tracing.enabled                  whether tracing collector is enabled (default true)
  --tracing.interval duration        how frequently to flush traces to tracing agent (default 0s)
  --tracing.queue-size int           buffer size for collector queue size
  --tracing.sample float             how frequent to sample traces

2025-02-17 18:32:16,114 WARN exited: storagenode (exit status 1; not expected)
2025-02-17 18:32:18,120 WARN received SIGTERM indicating exit request
2025-02-17 18:32:18,120 INFO waiting for processes-exit-eventlistener, storagenode to die
2025-02-17 18:32:20,123 WARN received SIGQUIT indicating exit request
2025-02-17 18:32:20,124 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)

2

This may have nothing to do with your problem, and I see the quotes: but spaces-in-paths for CLI services has burned me so many times in the past…

4 Likes
3

I see many curly quotes in your command, could you please check, that all quotes are straight ones?
Also if you put your command between two lines with three backticks, it would be formatted properly, i.e.

```
docker run ...
```

I modified your post. Could you please find in the logs the beginning of the output, there should be an actual error.
But usually it prints help, if some quote is missing or you used either a curly one or hyphen instead of space, or long dashes instead of double minuses, etc.

4

Fixed it myself but had to do it this way

sudo -s

docker run ...
1 Like