Setup Storj to Asustor AS3304T nas

[kozakbarnabas]

it is drive me back to Barna@HAL9000-NAS:/volume1/home/Barna $

[peem]

Okay, now just the command:

cd /volume1/home/Barna/_STROJ && ls

[peem]

There is a “bind” option in Portainer, but it doesn’t relieve the user from thinking while configuring

[peem]

My guess is that the one-time (!!!) command that configures your node is:

sudo docker run --rm -e SETUP="true" \
    --user $(id -u):$(id -g) \
    --mount type=bind,source="/volume1/home/Barna/_STROJ/Identity/storagenode",destination=/app/identity \
    --mount type=bind,source="/volume1/home/Barna/_STROJ/storage",destination=/app/config \
    --name storagenode storjlabs/storagenode:latest

[kozakbarnabas]

I followed your instrucion (just correct _STROJ to _STORJ), but i got that…

[peem]

sudo docker run --rm -e SETUP="true"  --user $(id -u):$(id -g)  --mount type=bind,source="/volume1/home/Barna/_STORJ/Identity/storagenode",destination=/app/identity  --mount type=bind,source="/volume1/home/Barna/_STORJ/storage",destination=/app/config     --name storagenode storjlabs/storagenode:latest

[Alexey]

Unfortunately it’s converted to -v /srv/dev-disk-by-uuid-...:/app/identity -v /srv/dev-disk-by-uuid-...:/app/config, not --mount.
It’s less dangerous now, because we have checks for special file which is created only on setup, but it’s better to worry than sorry.
Because if disk disappear, docker with option -v will create empty volumes and mount them instead of disk.

[peem]

@Alexey

Unfortunately it’s converted to -v

How did you see it?
What command? or what program?

I can see “docker inspect”:

[Alexey]

Oh, they learned how to use --mount? Respect

[kozakbarnabas]

• Thank you very much peem!
• It is working!

[peem]

I am also happy May the stay of SNO be for you what you have done best in your life

[Roberto]

For all Asustor users, Deadbolt Ransomware! :

https://forum.asustor.com/viewtopic.php?f=45&t=12630

[Luis]

I’m also trying to install Storj on the same NAS.

My container not start.

Can anyone help?

Thanks

The conteiner log is:

2022-03-01T17:30:06.141Z ERROR Failed to load identity. {“error”: “file or directory not found: open identity/identity.cert: no such file or directory”, “errorVerbose”: “file or directory not found: open identity/identity.cert: no such file or directory\n\tstorj.io/common/identity.Config.Load:329\n\tmain.cmdRun:182\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\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.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:474\n\truntime.main:255”}

Error: Failed to load identity: file or directory not found: open identity/identity.cert: no such file or directory

storj.io/common/identity.Config.Load:329

main.cmdRun:182

storj.io/private/process.cleanup.func1.4:363

storj.io/private/process.cleanup.func1:381

github.com/spf13/cobra.(*Command).execute:852

github.com/spf13/cobra.(*Command).ExecuteC:960

github.com/spf13/cobra.(*Command).Execute:897

storj.io/private/process.ExecWithCustomConfig:88

storj.io/private/process.ExecCustomDebug:70

main.main:474

runtime.main:255

2022-03-01T17:30:06.141Z ERROR Failed to load identity. {“error”: “file or directory not found: open identity/identity.cert: no such file or directory”, “errorVerbose”: “file or directory not found: open identity/identity.cert: no such file or directory\n\tstorj.io/common/identity.Config.Load:329\n\tmain.cmdRun:182\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\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.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:474\n\truntime.main:255”}

Error: Failed to load identity: file or directory not found: open identity/identity.cert: no such file or directory

storj.io/common/identity.Config.Load:329

main.cmdRun:182

storj.io/private/process.cleanup.func1.4:363

storj.io/private/process.cleanup.func1:381

github.com/spf13/cobra.(*Command).execute:852

github.com/spf13/cobra.(*Command).ExecuteC:960

github.com/spf13/cobra.(*Command).Execute:897

storj.io/private/process.ExecWithCustomConfig:88

storj.io/private/process.ExecCustomDebug:70

main.main:474

runtime.main:255

[Alexey]

Seems you did not mount the identity folder from your NAS filesystem to the /app/identity folder inside the container.
Perhaps you did not mount your data location too.
Please, stop and remove the container and run it again with all required parameters:

Storage Node

[Luis]

I tried to configure by SSH and the conteineir already works.

I Used

docker run --rm -e SETUP=“true”
–user $(id -u):$(id -g)
–mount type=bind,source="/volume1/home/LHM/Storj/Identity/storagenode",destination=/app/identity
–mount type=bind,source="/volume1/home/LHM/Storj/Storage",destination=/app/config
–name storagenode storjlabs/storagenode:latest

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=“0x4d95bcc771F4A5a2CcDdc16d7dfCE06A62416655”
-e EMAIL=“luis.xxxx@xxxx.pt”
-e ADDRESS=“xxxxxx.ddns.me:28967”
-e STORAGE=“2TB”
–user $(id -u):$(id -g)
–mount type=bind,source="/volume1/home/LHM/Storj/Identity/storagenode",destination=/app/identity
–mount type=bind,source="/volume1/home/LHM/Storj/Storage",destination=/app/config
–name storagenode storjlabs/storagenode:latest

The problem now seems to me to be the doors closed.

2022-03-02T17:25:36.785Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2022-03-02T17:25:36.790Z INFO Operator email {“Address”: “luis.xxxx@xxxx.pt”}
2022-03-02T17:25:36.790Z INFO Operator wallet {“Address”: “0x4d95bcc771F4A5a2CcDdc16d7dfCE06A62416655”}
2022-03-02T17:25:37.729Z INFO Telemetry enabled {“instance ID”: “1SGXst5g2uzR6hMoz3qQYHgMmssgr7tNDDSFvy8BGQ1NfLU2CP”}
2022-03-02T17:25:37.805Z INFO db.migration Database Version {“version”: 53}
2022-03-02T17:25:39.085Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2022-03-02T17:25:40.049Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2022-03-02T17:25:40.050Z INFO Node 1SGXst5g2uzR6hMoz3qQYHgMmssgr7tNDDSFvy8BGQ1NfLU2CP started
2022-03-02T17:25:40.050Z INFO Public server started on [::]:28967
2022-03-02T17:25:40.050Z INFO Private server started on 127.0.0.1:7778
2022-03-02T17:25:40.050Z INFO failed to sufficiently increase receive buffer size (was: 224 kiB, wanted: 2048 kiB, got: 448 kiB). See UDP Receive Buffer Size · lucas-clemente/quic-go Wiki · GitHub for details.

2022-03-02T17:25:45.549Z WARN contact:service failed PingMe request to satellite {“Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”, “error”: “ping satellite: check-in network: failed to ping node (ID: 1SGXst5g2uzR6hMoz3qQYHgMmssgr7tNDDSFvy8BGQ1NfLU2CP) at address: xxxxxxxx.ddns.me:28967, err: contact: failed to dial storage node (ID: 1SGXst5g2uzR6hMoz3qQYHgMmssgr7tNDDSFvy8BGQ1NfLU2CP) at address xxxxxxx.ddns.me:28967 using QUIC: rpc: quic: timeout: no recent network activity”, “errorVerbose”: “ping satellite: check-in network: failed to ping node (ID: 1SGXst5g2uzR6hMoz3qQYHgMmssgr7tNDDSFvy8BGQ1NfLU2CP) at address: xxxxxxx.ddns.me:28967, err: contact: failed to dial storage node (ID: 1SGXst5g2uzR6hMoz3qQYHgMmssgr7tNDDSFvy8BGQ1NfLU2CP) at address xxxxxxx.ddns.me:28967 using QUIC: rpc: quic: timeout: no recent network activity\n\tstorj.io/storj/storagenode/contact.(*Service).requestPingMeOnce:194\n\tstorj.io/storj/storagenode/contact.(*Service).RequestPingMeQUIC:167\n\tstorj.io/storj/storagenode.(*Peer).addConsoleService:841\n\tstorj.io/storj/storagenode.(*Peer).Run:880\n\tmain.cmdRun:251\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\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.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:474\n\truntime.main:255”}

I have on the local network more nodes on windows, about 50TB in data
Every computer on my local network has a different port.

I do not understand also because config.yaml does not have the correct configuration.

the public address of the node, useful for nodes behind NAT

contact.external-address: “”

path to the certificate chain for this identity

identity.cert-path: identity/identity.cert

path to the private key for this identity

identity.key-path: identity/identity.key

operator email address

operator.email: “”

operator wallet address

operator.wallet: “”

public address to listen on

server.address: :""

However in the NAS is being more complicated.

[Alexey]

@Luis

docker run --rm -e SETUP="true" ...

This command should be used only once.

@Luis

I do not understand also because config.yaml does not have the correct configuration.

This is normal for docker setup, all required parameters you provide in the CLI, they have a precedence above parameters in config.yaml.

The ping failed means that your address is not available from outside.
Please, use this checklist to troubleshoot:

My Node is OFFLINE for 2 hours

It should connect in seconds. There are a few things you should check. Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port. If it’s closed, it could still be several things. Make sure the WAN IP you see in your router settings matches the IP shown on the above page. Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…

I would only add, that you need to forward UDP 28967 as well or modify your port forwarding rule to forward both protocols - TCP+UDP.
Please, also make sure to add allowance rules to the firewall on your NAS.

[Luis]

Finally online.

The problem was the ports closed.

I routed port 28967 in to rooter,.
Forwarding in NAS and rooter i couldn’t open the port.

Thanks