Bandwidth N/A Problem!

Node Operators troubleshooting
1

Hello, i have problem my node saying: Bandwidth N/A
It’s not sending, nor receiving anything.
I didn’t changed anything, but after last update, this appeared.
Ubuntu 16.04 64bit
Second node is doing fine.
What can be the problem?
ps: port is chnged becuse i have other node on same ip,
but it doesnt matter, it was working like this, for many months.

Storage Node Dashboard ( Node Version: v1.0.1 )

======================

ID XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Last Contact ONLINE
Uptime 48m41s

               Available         Used     Egress     Ingress
 Bandwidth           N/A          0 B        0 B         0 B (since Apr 1)
      Disk        2.3 TB     422.4 GB

Internal 127.0.0.1:7778
External XX.XX.XX.XX:28968

#!/bin/bash

sudo docker run -d --restart unless-stopped -p 28968:28967
-e WALLET=“XXXXXXXXXXXXXXXXXXXXXXX”
-e EMAIL=“xxxxxxxxxxxxx”
-e ADDRESS=“XX.XX.XX.XX:28968”
-e BANDWIDTH=“30TB”
-e STORAGE=“2700GB”
-v “/home/traktor/.local/share/storj/identity/storagenode1”:/app/identity
-v “/home/traktor/s1”:/app/config
–name storagenode1 storjlabs/storagenode:alpha

2

Not a problem: Changelog v0.35.3

3

I see alot of problems with this why are you using the old docker start command and using tag alpha instead of beta? and -v instead of -mount…

4

this is a problem:

It looks like you are using a very old version of the docker run command that used the -v rather than the --mount option which will not work properly. You should use --mount instead as explained here and you must static mount via /etc/fstab. Failure to do so will put you in high risk of failing audits and getting disqualified. Also all the \ at the end of each line are missing. Perhaps you just edited them out for the forum post but they must be present in the docker run command.

You also need to change storjlabs/storagenode:alpha to storjlabs/storagenode:beta and please add --stop-timeout 300 to the first line and -p 127.0.0.1:14002:14002 \ as shown in the example in the link to the documentation above.

This node may be already disqualified or in suspension mode now because of the above problems. If you are running a second node, I suggest you make the needed changes to its docker run command before it gets disqualified.

5

thanks for answer i rewrote everything you said, but node is restarting constantly now, with this new config. So which docker version should I use?
currently using this one:
docker-ce is already the newest version (5:19.03.8~3-0~ubuntu-xenial).

nop matter what i do its sill restarting

this is my config

#!/bin/bash

sudo docker run -d --restart unless-stopped --stop-timeout 300
-p 28968:28967
-p 127.0.0.1:14002:14002
-e WALLET=“0xXXXXXXXXXXXXXXXXXX
-e EMAIL="xxxxxxxx@gmail.com”
-e ADDRESS=“XX.XX.XX.XX:28968”
-e STORAGE=“2TB”
–mount type=bind,source="/home/traktor/.local/share/storj/identity/storagenode1",destination=/app/identity
–mount type=bind,source="/home/traktor/s1",destination=/app/config
–name storagenode1 storjlabs/storagenode:beta

an i have \ signs in config, this forum is damaging configs, im not sure why in here on forum isnt code tag, when everybody pasting configs, i dont understand this, this should be the one of the features

6

Please post the last 20 lines of your log.

docker logs --tail 20 storagenode1

You can post this in a code block like this, to prevent the forum from messing up the text. Please do the same for your docker run command as well.

```
Paste text here
```

Use the ` sign 3x you find on the button left to the 1 on your keyboard.

7

it say im running v 0.28.2?

2020-04-05T01:15:46.606Z ERROR version running on not allowed/outdated version v0.28.2
2020-04-05T01:15:46.606Z FATAL Unrecoverable error {“error”: “outdated software version (v0.28.2), please update”}

what joke is it. Before those restart it was showin normal 1.0.1
now i pulled storj from github again, now its running
in state as it was before 0 bandwith,
i checked in ui, an its showing, that i was disqualified on 1.4.2020
but not sure why…

So i think im going to fire up a new node now.
So we can close this case, for now.

8

You should pull the image before the run

docker pull storjlabs/storagenode:beta

Then use the docker run command: https://documentation.storj.io/setup/cli/storage-node#running-the-storage-node

9

i wrote up there, i already pulled it,
but it doesnt matter anymore cause im disqualified

10

3 posts were merged into an existing topic: I receive no AuthTokens anymore?