Storage node dashboard service error: sql: expected 13 destination arguments in Scan, not 12

SlavikCA · August 30, 2019, 6:56pm

I’m trying to get info from recently added dashboard on port 14002.

It works great on 1 of my node.

But another gives this error:

storage node dashboard service error: sql: expected 13 destination arguments in Scan, not 12

I’m not sure, if it’s ok to open such endpoint. I think it is.
So, here it is:
http://deb10b.slavikf.com:14002/api/satellite/118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW

The dashboard endpoint is ok:
http://deb10b.slavikf.com:14002/api/dashboard

So, the issue is only with satellite details.

What that error means for the node? should I fix it? how?

Logs from Docker:

2019-08-30T18:44:11.808Z ERROR console:endpoint api handler server error {“status code”: 500, “error”: “storagenode console web error: storage node dashboard service error: sql: expected 13 destination arguments in Scan, not 12”, “errorVerbose”: “storagenode console web error: storage node dashboard service error: sql: expected 13 destination arguments in Scan, not 12\n\t
storj.io/storj/storagenode/console.(*Service).GetSatelliteData:188\n\t
storj.io/storj/storagenode/console/consoleserver.(*Server).satelliteHandler:171\n\t
net/http.HandlerFunc.ServeHTTP:1995\n\t
net/http.(*ServeMux).ServeHTTP:2375\n\t
net/http.serverHandler.ServeHTTP:2774\n\t
net/http.(*conn).serve:1878”}

Dylan · August 30, 2019, 8:45pm

Can you post your docker run command?

SlavikCA · August 30, 2019, 9:12pm

docker run -d --restart unless-stopped \
    -p 28967:28967 \
    -p 14002:14002 \
    -e WALLET="0x277b6D64AF9a1D0BA1E8Be24Bb657409B0de8363" \
    -e EMAIL="slavikCA+deb10b@gmail.com" \
    -e ADDRESS="deb10b.slavikf.com:28967" \
    -e BANDWIDTH="40TB" \
    -e STORAGE="1400GB" \
    --mount type=bind,source="/home/slavik/.local/share/storj/identity/storagenode",destination=/app/identity \
    --mount type=bind,source="/var/storj",destination=/app/config \
    --name storagenode \
    storjlabs/storagenode:alpha

Dylan · August 30, 2019, 9:40pm

In the past we have seen user with a read only info.db, maybe that’s it. Can you post more of your logs?

docker logs --tail 20 storagenode

SlavikCA · August 30, 2019, 9:52pm

slavik@deb10b:~$ sudo docker logs --tail 20 storagenode
2019-08-30T21:27:42.417Z ERROR server rpc error: code = PermissionDenied desc = untrusted peer 1QzDKGHDeyuRxbvZhcwHU3syxTYtU1jHy5duAKuPxja3XC8ttk
2019-08-30T21:32:54.625Z ERROR server rpc error: code = PermissionDenied desc = untrusted peer 1QzDKGHDeyuRxbvZhcwHU3syxTYtU1jHy5duAKuPxja3XC8ttk
2019-08-30T21:38:05.720Z ERROR server rpc error: code = PermissionDenied desc = untrusted peer 1QzDKGHDeyuRxbvZhcwHU3syxTYtU1jHy5duAKuPxja3XC8ttk
2019-08-30T21:42:20.440Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW sending {“count”: 266}
2019-08-30T21:42:20.443Z INFO bandwidth Performing bandwidth usage rollups
2019-08-30T21:42:20.614Z INFO version running on version v0.19.5
2019-08-30T21:42:41.335Z ERROR orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW gRPC client error when receiveing new order settlements {“error”: “order: failed to receive settlement response: rpc error: code = Unavailable desc = transport is closing”, “errorVerbose”: “order: failed to receive settlement response: rpc error: code = Unavailable desc = transport is closing\n\tstorj.io/storj/storagenode/orders.(*Service).settle:310\n\tstorj.io/storj/storagenode/orders.(*Service).Settle:190\n\tstorj.io/storj/storagenode/orders.(*Service).sendOrders.func2:169\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2019-08-30T21:42:41.335Z INFO orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW finished
2019-08-30T21:42:41.335Z ERROR orders.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW failed to settle orders {“error”: “order: failed to receive settlement response: rpc error: code = Unavailable desc = transport is closing”, “errorVerbose”: “order: failed to receive settlement response: rpc error: code = Unavailable desc = transport is closing\n\tstorj.io/storj/storagenode/orders.(*Service).settle:310\n\tstorj.io/storj/storagenode/orders.(*Service).Settle:190\n\tstorj.io/storj/storagenode/orders.(*Service).sendOrders.func2:169\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2019-08-30T21:43:20.869Z ERROR server rpc error: code = PermissionDenied desc = untrusted peer 1QzDKGHDeyuRxbvZhcwHU3syxTYtU1jHy5duAKuPxja3XC8ttk
2019-08-30T21:48:33.421Z ERROR server rpc error: code = PermissionDenied desc = untrusted peer 1QzDKGHDeyuRxbvZhcwHU3syxTYtU1jHy5duAKuPxja3XC8ttk
2019-08-30T21:51:08.029Z INFO piecestore upload started {“Piece ID”: “DQDZY3PMK2YWCRHKV4YT7UOQNMTR43IWRUNHOBNAVH3DJMDCKQUA”, “SatelliteID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “Action”: “PUT”}
2019-08-30T21:51:18.405Z INFO piecestore upload failed {“Piece ID”: “DQDZY3PMK2YWCRHKV4YT7UOQNMTR43IWRUNHOBNAVH3DJMDCKQUA”, “SatelliteID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “Action”: “PUT”, “error”: “piecestore protocol: rpc error: code = Canceled desc = context canceled”, “errorVerbose”: “piecestore protocol: rpc error: code = Canceled desc = context canceled\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).Upload:242\n\tstorj.io/storj/pkg/pb._Piecestore_Upload_Handler:851\n\tstorj.io/storj/pkg/server.(*Server).logOnErrorStreamInterceptor:23\n\tgoogle.golang.org/grpc.(*Server).processStreamingRPC:1127\n\tgoogle.golang.org/grpc.(*Server).handleStream:1178\n\tgoogle.golang.org/grpc.(*Server).serveStreams.func1.1:696”}
2019-08-30T21:51:18.405Z ERROR server piecestore protocol: rpc error: code = Canceled desc = context canceled
storj.io/storj/storagenode/piecestore.(*Endpoint).Upload:242
storj.io/storj/pkg/pb._Piecestore_Upload_Handler:851
storj.io/storj/pkg/server.(*Server).logOnErrorStreamInterceptor:23
google.golang.org/grpc.(*Server).processStreamingRPC:1127
google.golang.org/grpc.(*Server).handleStream:1178
google.golang.org/grpc.(*Server).serveStreams.func1.1:696

Alexey · August 30, 2019, 9:54pm

How is your storage connected?

SlavikCA · August 30, 2019, 10:00pm

Here is all ERRORs from the log:

https://slavikf.com/files/error.txt

Is it connected? I think so:

Storage Node Dashboard ( Node Version: v0.19.5 )

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

ID           12T3ZXA96tu6C3JG7tVsZ5S8kEcR95ynwk1QoQDQ4jXJokJ7jAU
Last Contact 2s ago
Uptime       10h17m39s

                   Available         Used     Egress     Ingress
     Bandwidth       40.0 TB       2.2 GB     1.2 GB      1.0 GB (since Aug 1)
          Disk        1.4 TB     576.6 MB

Bootstrap bootstrap.storj.io:8888
Internal  127.0.0.1:7778
External  deb10b.slavikf.com:28967

Neighborhood Size 145

Alexey · August 30, 2019, 10:09pm

I mean, how is physically connected your storage? What the interface?
Is it a network connected drive?
USB?
Internal?
Other?

SlavikCA · August 30, 2019, 10:23pm

I have Linux system (Debian 10) with local physical 2TB hard drive
Running Docker
So, storage is local hard drive, mounted to Docker.

slavik@deb10b:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            946M     0  946M   0% /dev
tmpfs           192M   20M  173M  11% /run
/dev/sda1       1.8T  2.8G  1.7T   1% /
tmpfs           960M     0  960M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           960M     0  960M   0% /sys/fs/cgroup
tmpfs           192M     0  192M   0% /run/user/1000