Invalid Node Type

subwolf · September 28, 2019, 10:07am

So I’m setting up a node at home, have over a terabyte of free space so figured I could test it out. However, things are not going to plan. I have tested this with both wired and/or wireless connections active with no difference.

The dashboard is definitely running, my neighbourhood size is 189 with port forwarding and dynamic dns set up:

Storage Node Dashboard ( Node Version: v0.9.1 )

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

ID           1eLJoKbAdMtGHtMSuwrarwGGwBbxzA92NLDP1xT2GA7JYCfBP5
Last Contact 5s ago
Uptime       5m50s

                   Available     Used     Egress     Ingress
     Bandwidth      100.0 TB        0          0           0 (since Sep 1)
          Disk        1.0 TB        0

Bootstrap bootstrap.storj.io:8888
Internal  127.0.0.1:7778
External  subwolf.ddns.net:28967

Neighborhood Size 189

But my log is full of…

2019-09-28T10:05:14.911Z        DPANIC  INVALID NODE TYPE: transport dial node
2019-09-28T10:05:15.297Z        DPANIC  INVALID NODE TYPE: connection success
2019-09-28T10:05:15.485Z        DPANIC  INVALID NODE TYPE: connection success
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: next
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: next
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: next
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: next
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: transport dial node
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: next
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: transport dial node
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: transport dial node
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: transport dial node
2019-09-28T10:05:18.468Z        DPANIC  INVALID NODE TYPE: transport dial node
2019-09-28T10:05:18.593Z        DPANIC  INVALID NODE TYPE: connection success
2019-09-28T10:05:18.795Z        DPANIC  INVALID NODE TYPE: connection success
2019-09-28T10:05:18.804Z        DPANIC  INVALID NODE TYPE: next
2019-09-28T10:05:18.805Z        DPANIC  INVALID NODE TYPE: transport dial node
2019-09-28T10:05:18.882Z        DPANIC  INVALID NODE TYPE: connection success
2019-09-28T10:05:18.927Z        DPANIC  INVALID NODE TYPE: connection success
2019-09-28T10:05:19.128Z        DPANIC  INVALID NODE TYPE: connection success
2019-09-28T10:05:19.339Z        DPANIC  INVALID NODE TYPE: next
2019-09-28T10:05:19.339Z        DPANIC  INVALID NODE TYPE: transport dial node
2019-09-28T10:05:19.434Z        DPANIC  INVALID NODE TYPE: next
2019-09-28T10:05:19.434Z        DPANIC  INVALID NODE TYPE: transport dial node

A quick look at my ifconfig reveals (leaving out docker entries):

enp27s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.46  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fdaa:bbcc:ddee:0:6d63:3bd4:f4e4:777c  prefixlen 64  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:e8ba:261f:7566:baf3  prefixlen 64  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:5b5c:40b0:a5ec:1131  prefixlen 64  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:4079:33e9:745:5411  prefixlen 64  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:6c69:7493:c8f1:cace  prefixlen 64  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:f461:edf6:88ba:dc54  prefixlen 64  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:14ff:85c3:fd56:25ff  prefixlen 64  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:44a0:7bba:29c:d6cc  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::c85c:970d:78b1:f40e  prefixlen 64  scopeid 0x20<link>
        ether 00:d8:61:72:d2:ef  txqueuelen 1000  (Ethernet)
        RX packets 3077800542  bytes 4577096559089 (4.5 TB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 750034425  bytes 686403668049 (686.4 GB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp28s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.47  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fdaa:bbcc:ddee:0:31d4:3293:ab04:958d  prefixlen 64  scopeid 0x0<global>
        inet6 fdaa:bbcc:ddee:0:7dc1:2714:137b:4a07  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::dbc8:42ae:4093:35a2  prefixlen 64  scopeid 0x20<link>
        ether a8:6d:aa:dd:ac:ca  txqueuelen 1000  (Ethernet)
        RX packets 8634442  bytes 12450850214 (12.4 GB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 511039  bytes 55521120 (55.5 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

This is unexpected and very confusing!

BrightSilence · September 28, 2019, 10:23am

Mate, you seem to be running version 0.9.1 while the current version is 0.21.3. I’d start by getting the latest version.

subwolf · September 28, 2019, 10:26am

Argh, why doesn’t downloading the latest with docker get the latest? Installed watchtower, waiting for update.

subwolf · September 28, 2019, 10:31am

subwolf@subwolf-tk:~$  sudo docker pull storjlabs/storagenode:beta
beta: Pulling from storjlabs/storagenode
Digest: sha256:46489ce5724cba8dbf252f882ee6e4fc05303788cd6e22666dab096e357d209c
Status: Image is up to date for storjlabs/storagenode:beta
docker.io/storjlabs/storagenode:beta

kevink · September 28, 2019, 11:48am

What’s your docker run command?

subwolf · September 28, 2019, 2:01pm

Which one? As there was no update yet I just restarted watchtower with a 10 minute update interval, after that works I’ll revert to the old interval.

kevink · September 28, 2019, 2:56pm

remove your node container and start it with the correct docker run command again. make sure to use the beta tag

subwolf · September 28, 2019, 3:07pm

I did! It’s the latest version now.

However, I’m seeing operations failing, maybe because it has the same node ID?

2019-09-28T14:14:54.693Z        INFO    piecestore      download started        {"Piece ID": "XZCVDJWHQUP33BPQ2QB6J2AGAYUDXGXG7QFDMU4QBSFFZGD26NDQ", "SatelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "GET"}
2019-09-28T14:14:54.787Z        INFO    piecestore      download failed {"Piece ID": "XZCVDJWHQUP33BPQ2QB6J2AGAYUDXGXG7QFDMU4QBSFFZGD26NDQ", "SatelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "GET", "error":
"rpc error: code = NotFound desc = file does not exist"}
2019-09-28T14:14:54.787Z        ERROR   server  gRPC stream error response      {"error": "rpc error: code = NotFound desc = file does not exist"}
2019-09-28T14:14:59.776Z        ERROR   server  gRPC unary error response       {"error": "rpc error: code = PermissionDenied desc = untrusted peer 1QzDKGHDeyuRxbvZhcwHU3syxTYtU1jHy5duAKuPxja3XC8ttk"}
2019-09-28T14:15:54.442Z        INFO    piecestore      download started        {"Piece ID": "K76NFS43W7YZA7DZ5A5JKXC7SSTE5GTRJLOZQ2SAGYJUDGTNSSCA", "SatelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "GET_AUDIT"}
2019-09-28T14:15:54.443Z        INFO    piecestore      download failed {"Piece ID": "K76NFS43W7YZA7DZ5A5JKXC7SSTE5GTRJLOZQ2SAGYJUDGTNSSCA", "SatelliteID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "GET_AUDIT", "error": "rpc error: code = NotFound desc = file does not exist"}
2019-09-28T14:15:54.443Z        ERROR   server  gRPC stream error response      {"error": "rpc error: code = NotFound desc = file does not exist"}

subwolf · September 28, 2019, 4:52pm

Ok, got it, now on the waiting list, thanks.

BrightSilence · September 28, 2019, 6:55pm

Oof turn off that node asap. Same node id means the same node. The satellite will assume you hold all data for that ID. Keeping this running will also damage your original node as data sent to the new node is now missing on the old node. If you don’t fix that issue asap you’ll most certainly get disqualified.

subwolf · September 30, 2019, 6:44am

Up and running now at home, thank you!