Problem with pulling storagenode image to Docker

Node Operators troubleshooting
, ,
1

After the Node restarting it just rebooting repeatedly.

docker stop -t 300 storagenode1
docker rm storagenode1

del Docker distro, del WSL2 distro, reset the network, restart.
then in backwards install WSL2 distro, Docker distro.

in PowerShell:

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

the node rolls up:

c32ce6654453: Pull complete
9e3f12e9f0b9: Pull complete
baabb14e0092: Pull complete
b23156875490: Pull complete
5907f5f7011c: Pull complete
dff5c6ba6652: Pull complete
efc8248e2380: Pull complete
e9c76c2e1d75: Pull complete
2ea849aef508: Pull complete
2c1b1377fc0c: Pull complete
60add7644c64: Pull complete
Digest: sha256:/some sha256 check/
Status: Downloaded newer image for storjlabs/storagenode:latest
downloading storagenode-updater
--2022-11-10 09:58:19--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
Resolving version.storj.io (version.storj.io)... 35.232.172.28, 35.232.172.28
Connecting to version.storj.io (version.storj.io)|35.232.172.28|:443... connected.

and in the end I’m getting the message:

GnuTLS: The TLS connection was non-properly terminated.
Unable to establish SSL connection.
http://: Invalid host name.

What’s wrong and where to dig in? Please need help.

2

Is there any other output between those two sections?

3

Nope, it’s the one section that I’ve split in logical blocks.

4

I think you might have broken it with the

-e SETUP="true"

You should only run it once when you create the node.

5

How can I solve this problem?

6

Try taking out the -e SETUP="true" bit?

7

I should also check- do you have your wallet and address and so on configured in G:\data\, and that’s why you’re not passing those in on the command line?

8

I have got a network malfunction a couple of days ago, got posted there about it:
https://forum.storj.io/t/watchtower-errors/20164/4
That struggled and won with the help of Alexey.

Today I’ve noticed that missed transition log command in a command that I’m using to start the node in Docker:
docker run -d --restart unless-stopped...

So I’ve stopped and removed the storagenode container, add the missing part and restart again.
After that the container starts and stops repeatedly.

And after that I’ve made all that mentioned in topic post.
But nothing works for now.

Tried to start the other nodes, but all the same.

9

it’s command for Win Docker, so it is correct.

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="mywallet" -e EMAIL="nodeidentitymail" -e ADDRESS="whiteipaddress:28967" -e STORAGE="11TB" --mount type=bind,source="G:\identity\storagenode",destination=/app/identity --mount type=bind,source="G:\data\",destination=/app/config --mount type=bind,source=D:/Storj/Logs/node1.log,destination=/app/logs/node1.log --name storagenode1 storjlabs/storagenode:latest --log.output=/app/logs/node1.log

10

This option will create a folder structure and create protection file storage-dir-verification based on provided identity. So this flag should be used only once for entire node’s life. If you specify a wrong path to the identity or data for the worked node you may destroy it (it will be disqualified because of missed data).
So better to do not run setup more than once for the same node.

Regarding a network issue. Is it possible, that your ISP blocking connections to the external resources, like GitHub for example or version.storj.io?

11

I have thought that I need to use this command every time when I’m reinstall the Docker.
There is no way to use a different wrong path - cause I’m using the command that I’ve saved before in *.txt file via Notepad++ and changing only letter of the HDD if it changed.
I have a 4 storagenodes on this PC and used the command -e SETUP="true" only on 2 of them. The other 2 nodes that not involved by this command I’ve tried to start with docker run -d --restart unless-stopped. They performs the same start/stop cycle.

There is no issues when I’m getting to version.storj.io with browser.

2022-11-11_11-54-29
2022-11-11_11-54-291145×262 170 KB

And there was no accidents with PC or network.
I’ve just tried to fix my mistake - the node worked about 3-4 days with:

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="mywallet" -e EMAIL="nodeidentitymail" -e ADDRESS="whiteipaddress:28967" -e STORAGE="11TB" --mount type=bind,source="G:\identity\storagenode",destination=/app/identity --mount type=bind,source="G:\data\",destination=/app/config --mount type=bind,source=D:/Storj/Logs/node1.log,destination=/app/logs/node1.log --name storagenode1 storjlabs/storagenode:latest`

without

--log.output=/app/logs/node1.log

in the end of a command.

I have:

docker stop -t 300 storagenode1

docker rm storagenode1

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="mywallet" -e EMAIL="nodeidentitymail" -e ADDRESS="whiteipaddress:28967" -e STORAGE="11TB" --mount type=bind,source="G:\identity\storagenode",destination=/app/identity --mount type=bind,source="G:\data\",destination=/app/config --mount type=bind,source=D:/Storj/Logs/node1.log,destination=/app/logs/node1.log --name storagenode1 storjlabs/storagenode:latest --log.output=/app/logs/node1.log

Then node starts/stops repeatedly.
Then I’ve made all the proccess from the 1st post and getting the message:

GnuTLS: The TLS connection was non-properly terminated.
Unable to establish SSL connection.
http://: Invalid host name.

I have tried to elevate all the other nodes, but they were starts to perform the same behaviour with start/stop cycle.

12

To make sure I understand, the GnuTLS error is what results when you run with -e SETUP=true, right? What shows up in the logs when the nodes get into the start/stop cycle?

13 
2022-11-12 00:38:12 downloading storagenode-updater
2022-11-12 00:38:13 downloading storagenode-updater
2022-11-12 00:38:15 downloading storagenode-updater
2022-11-12 00:38:17 downloading storagenode-updater
2022-11-12 00:38:12 --2022-11-11 20:38:12--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
2022-11-12 00:38:12 Resolving version.storj.io (version.storj.io)... ::ffff:35.232.172.28, 35.232.172.28
2022-11-12 00:38:12 Connecting to version.storj.io (version.storj.io)|::ffff:35.232.172.28|:443... connected.
2022-11-12 00:38:12 GnuTLS: The TLS connection was non-properly terminated.
2022-11-12 00:38:12 Unable to establish SSL connection.
2022-11-12 00:38:12 http://: Invalid host name.
2022-11-12 00:38:13 --2022-11-11 20:38:13--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
2022-11-12 00:38:14 Resolving version.storj.io (version.storj.io)... 35.232.172.28, ::ffff:35.232.172.28
2022-11-12 00:38:14 Connecting to version.storj.io (version.storj.io)|35.232.172.28|:443... connected.
2022-11-12 00:38:14 GnuTLS: The TLS connection was non-properly terminated.
2022-11-12 00:38:14 Unable to establish SSL connection.
2022-11-12 00:38:14 http://: Invalid host name.
2022-11-12 00:38:15 --2022-11-11 20:38:15--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
2022-11-12 00:38:15 Resolving version.storj.io (version.storj.io)... ::ffff:35.232.172.28, 35.232.172.28
2022-11-12 00:38:15 Connecting to version.storj.io (version.storj.io)|::ffff:35.232.172.28|:443... connected.
2022-11-12 00:38:15 GnuTLS: The TLS connection was non-properly terminated.
2022-11-12 00:38:15 Unable to establish SSL connection.
2022-11-12 00:38:15 http://: Invalid host name.
2022-11-12 00:38:17 --2022-11-11 20:38:17--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
2022-11-12 00:38:17 Resolving version.storj.io (version.storj.io)... ::ffff:35.232.172.28, 35.232.172.28
2022-11-12 00:38:17 Connecting to version.storj.io (version.storj.io)|::ffff:35.232.172.28|:443... connected.
2022-11-12 00:38:17 GnuTLS: The TLS connection was non-properly terminated.
2022-11-12 00:38:17 Unable to establish SSL connection.
2022-11-12 00:38:17 http://: Invalid host name.
2022-11-12 00:38:19 --2022-11-11 20:38:19--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
2022-11-12 00:38:19 Resolving version.storj.io (version.storj.io)... ::ffff:35.232.172.28, 35.232.172.28
2022-11-12 00:38:19 Connecting to version.storj.io (version.storj.io)|::ffff:35.232.172.28|:443... connected.
2022-11-12 00:38:19 GnuTLS: The TLS connection was non-properly terminated.
2022-11-12 00:38:19 Unable to establish SSL connection.
2022-11-12 00:38:19 http://: Invalid host name.
2022-11-12 00:38:22 --2022-11-11 20:38:22--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
2022-11-12 00:38:22 Resolving version.storj.io (version.storj.io)... 35.232.172.28, ::ffff:35.232.172.28
2022-11-12 00:38:22 Connecting to version.storj.io (version.storj.io)|35.232.172.28|:443... connected.
2022-11-12 00:38:22 GnuTLS: The TLS connection was non-properly terminated.
2022-11-12 00:38:22 Unable to establish SSL connection.
2022-11-12 00:38:22 http://: Invalid host name.
2022-11-12 00:38:26 --2022-11-11 20:38:26--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
2022-11-12 00:38:26 Resolving version.storj.io (version.storj.io)... ::ffff:35.232.172.28, 35.232.172.28
2022-11-12 00:38:26 Connecting to version.storj.io (version.storj.io)|::ffff:35.232.172.28|:443... connected.
2022-11-12 00:38:26 GnuTLS: The TLS connection was non-properly terminated.
2022-11-12 00:38:26 Unable to establish SSL connection.
2022-11-12 00:38:26 http://: Invalid host name.
2022-11-12 00:38:33 --2022-11-11 20:38:33--  https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
2022-11-12 00:38:33 Resolving version.storj.io (version.storj.io)... 35.232.172.28, ::ffff:35.232.172.28
2022-11-12 00:38:33 Connecting to version.storj.io (version.storj.io)|35.232.172.28|:443... connected.
2022-11-12 00:38:19 downloading storagenode-updater
2022-11-12 00:38:22 downloading storagenode-updater
2022-11-12 00:38:26 downloading storagenode-updater
2022-11-12 00:38:33 downloading storagenode-updater
2022-11-12 00:38:33 GnuTLS: The TLS connection was non-properly terminated.
2022-11-12 00:38:33 Unable to establish SSL connection.
2022-11-12 00:38:33 http://: Invalid host name.

this log from node that not been set up with -e SETUP=true.
Just docker run -d --restart unless-stopped.

14

So seems it’s the same network issue with the connection termination, as before.
Perhaps you need not only uninstall the Docker desktop and wsl2 distro, but also WSL itself to remove a previously configured virtual switch and install everything back.

15

I’ve all the steps described in this article:
uninstall wsl2 windows 10

What have I missed?

16

These all steps which are requires to remove all components, but it requires reboot afterward.

17

I’ve rebooted after these steps and rebooted after Docker uninstallation and net reset settings.

18

did it help? Or do you still have this issue to download a small file?
If so, could you please try a mobile internet for a while to confirm that there is no problem with this PC

19

The truth is that I’m getting to this PC via remote access software so there is no obvious reasons of node setup blockage.

20

The previous problem with download of a small file had gone and I’ve replied in topic.
After few days passed I’m noticed that I’ve missed a part of a command about log file.
And this is get me this pit.