Issues with running on Synology

Node Operators troubleshooting
, ,
1

Hi,

I’ve been trying for a full day get the node to run on a Synology docker.
I installed by following the instructions.

Right now the error i’m getting is:

2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.839Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.732Z INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.730Z INFO Running on version {"Service": "storagenode-updater", "Version": "v1.50.4"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.728Z INFO Invalid configuration file value for key {"Key": "log.level"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.728Z INFO Invalid configuration file key {"Key": "storage.allocated-bandwidth"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.728Z INFO Invalid configuration file key {"Key": "server.private-address"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.728Z INFO Invalid configuration file key {"Key": "console.address"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.728Z INFO Invalid configuration file key {"Key": "storage.allocated-disk-space"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.728Z INFO Invalid configuration file key {"Key": "server.address"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.728Z INFO Invalid configuration file key {"Key": "operator.wallet"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.727Z INFO Invalid configuration file key {"Key": "operator.email"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.726Z INFO Invalid configuration file key {"Key": "contact.external-address"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.725Z INFO Invalid configuration file key {"Key": "operator.wallet-features"}
2022-03-26 12:53:59	stdout	2022-03-26T12:53:58.724Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
2022-03-26 12:53:59	stdout	2022-03-26 12:53:58,561 INFO spawned: 'storagenode-updater' with pid 11
2022-03-26 12:53:59	stdout	2022-03-26 12:53:58,549 INFO spawned: 'storagenode' with pid 10
2022-03-26 12:53:58	stdout	2022-03-26 12:53:58,534 INFO spawned: 'processes' with pid 9
2022-03-26 12:53:57	stdout	2022-03-26 12:53:57,527 CRIT could not write pidfile /run/supervisord.pid

I’ve searched for the config.yaml file but I could not find it.

help :frowning:

Thanks,
Alex

2

Seems you have specified the user as it is suggested in the previous CRIT message?
If so, please, remove it.
See CRIT messages in log after update (docker)

1 Like
3

Hi Alexey,

I have removed and re-placed the container. I used this:

docker run --rm -e SETUP="true" \
    --mount type=bind,source="/volume1/docker/storj/identity",destination=/app/identity \
    --mount type=bind,source="/volume1/docker/storj/data",destination=/app/config \
    --name storagenode storjlabs/storagenode:latest

The “Invalid configuration file key” errors have not disappared. They are reported again.

But, I have discovered that the problem is actually with the Synology firewall.

The storJ node did run for a few hours, and then I discovered that it was “Offline” (QUIC was reporting OK). I disabled the firewall, restarted the container and it went Online again.

In addition, when I try to start the container with the firewall on, it started and shut down after a few seconds. Dashboard was not accessible. As soon as I disabled the firewall everything is ok.

I have ofcourse allowed all required ports on synology firewall:

UDP 28967-28999 (just in case i needed to use other ports)
TCP 28967-28999 (just in case i needed to use other ports)
TCP 14002

I dont understand how the firewall stops the container from launcing.

Thanks
Alex

4

Seems you have not only inbound rules, but also outbound. Please remove or disable outbound rules, it should have only inbound.

1 Like
5

Hi. There’s no option for inbound/outbound on synology firewall. I believe all rules are inbound by default.

6

When you enable firewall your node cannot be contacted, so it’s restarting.
Seems you need to configure something else on Synology firewall, not only ports.
I have no Synology, so cannot say for sure how it should be done.
However, in the firewall rule should not be any source IP (or select “all” if there is such an option), the action should be “allow”. All “allow” rules should be before any “deny”.