Storj Node not receiving data to store

I started my node and it has been up a mere 86 hours. Is there a time period that needs to be proven for the node to be considered trustworthy to receive data to store? Should I be concerned no data has been sent to be stored?

What do the logs say?

INFO bandwidth Performing bandwidth usage rollups
INFO trust Scheduling next refresh {“after”: “6h32m39.583005687s”}

Just lots of these messages. Nothing really showcasing an issue.

can you post some lines, like the last 50 or so.

2021-11-18T21:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-18T22:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-18T23:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T00:06:33.736Z INFO trust Scheduling next refresh {“after”: “8h21m10.475763676s”}
2021-11-19T00:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T01:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T02:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T03:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T04:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T05:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T06:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T07:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T08:16:23.285Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T08:27:44.754Z INFO trust Scheduling next refresh {“after”: “8h15m7.753874874s”}
2021-11-19T09:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T10:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T11:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T12:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T13:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T14:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T15:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T16:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T16:42:52.265Z INFO trust Scheduling next refresh {“after”: “6h32m39.583005687s”}
2021-11-19T17:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T18:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T19:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T20:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T21:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T22:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-19T23:15:32.073Z INFO trust Scheduling next refresh {“after”: “3h48m59.601986011s”}
2021-11-19T23:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T00:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T01:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T02:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T03:04:31.876Z INFO trust Scheduling next refresh {“after”: “5h19m13.807170157s”}
2021-11-20T03:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T04:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T05:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T06:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T07:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T08:16:22.833Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T08:23:45.895Z INFO trust Scheduling next refresh {“after”: “6h36m1.963655675s”}
2021-11-20T09:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T10:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T11:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T12:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T13:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T14:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T14:59:47.618Z INFO trust Scheduling next refresh {“after”: “4h19m38.385295599s”}
2021-11-20T15:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T16:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T17:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T18:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T19:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T19:19:26.217Z INFO trust Scheduling next refresh {“after”: “5h35m36.279639251s”}
2021-11-20T20:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T21:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T22:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-20T23:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T00:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T00:55:02.699Z INFO trust Scheduling next refresh {“after”: “7h13m57.74904289s”}
2021-11-21T01:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T02:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T03:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T04:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T05:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T06:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T07:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T08:09:00.654Z INFO trust Scheduling next refresh {“after”: “7h40m17.292822807s”}
2021-11-21T08:16:22.384Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T09:16:21.942Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T10:16:21.942Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T11:16:21.942Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T12:16:21.942Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T13:16:21.942Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T14:16:21.942Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T15:16:21.942Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T15:49:17.704Z INFO trust Scheduling next refresh {“after”: “5h33m15.639647184s”}
2021-11-21T16:16:21.942Z INFO bandwidth Performing bandwidth usage rollups
^C2021-11-21T16:30:52.253Z INFO Got a signal from the OS: “interrupt”
2021-11-21T16:31:10.269Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2021-11-21T16:31:10.292Z INFO Operator email {“Address”: “xxxxx@xxxxxx.com”}
2021-11-21T16:31:10.292Z INFO Operator wallet {“Address”: “xxxxxxxxxxxxxxxxxxxxxxxxxx”}
2021-11-21T16:31:10.722Z INFO Telemetry enabled {“instance ID”: “1RUaq76MziEVzuXaNRANHKi9jBFU3A9QWaxBMkzPaAL1CwEkSW”}
2021-11-21T16:31:10.817Z INFO db.migration Database Version {“version”: 53}
2021-11-21T16:31:11.328Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2021-11-21T16:31:12.081Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2021-11-21T16:31:12.081Z INFO trust Scheduling next refresh {“after”: “5h20m25.501654468s”}
2021-11-21T16:31:12.081Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T16:31:12.082Z INFO Node 1RUaq76MziEVzuXaNRANHKi9jBFU3A9QWaxBMkzPaAL1CwEkSW started
2021-11-21T16:31:12.082Z INFO Public server started on [::]:28967
2021-11-21T16:31:12.082Z INFO Private server started on 127.0.0.1:7778
2021-11-21T17:31:12.082Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T18:31:12.082Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T19:31:12.082Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T20:31:12.082Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T21:31:12.082Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T21:51:37.795Z INFO trust Scheduling next refresh {“after”: “6h32m4.70424264s”}
2021-11-21T22:31:12.082Z INFO bandwidth Performing bandwidth usage rollups
2021-11-21T23:31:12.082Z INFO bandwidth Performing bandwidth usage rollups

This doesnt look like a node running is this everything in the logs?

Hello @grburgos ,
Welcome to the forum!

Is it online? Please, check your web-dashboard on http://localhost:14002

Here is another image about disk utilization.

you are using an old version of the storagenode software and you will not get ingress when more than 2 minor versions behind, you should be on v1.42.4
so update and it will start getting ingress

don’t forget to setup watchtower or whatever else autoupdate is called.

3 Likes

I have now gone and setup watchtower and I’m waiting for it to cycle and update my node. Keep you all posted.

It looks like the question about not getting ingress (anymore) together with the solution to update comes up quite a lot.
I am wondering, if the satellite as it is aware of non-actual version couldn’t trigger some kind of log message on the node so that this specific issue becomes immediately visible and clear to anyone.

1 Like

And maybe also a big red warning on the node dashboard

1 Like


No updates are happening using Storj watchtower and the dashboard states the version is in range.

watchtower is working fine…

docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2783f518f42a storjlabs/watchtower “/watchtower storage…” 23 hours ago Up 23 hours watchtower
61b05a349caf storjlabs/storagenode:latest-data-8 “/entrypoint” 5 days ago Up 23 hours 0.0.0.0:14002->14002/tcp, 0.0.0.0:28967->28967/tcp, 0.0.0.0:28967->28967/udp storagenode-0

You should just update manually. Your node is already not running correctly, Also im not exactly sure how you can install a node that is outdated before you get started. what is your docker pull command?

I’m using Qnap’s docker version. Used the GUI instead of the command line. I will be recreating it manually.

I also have a node on qnap. it is much easier to manage it via SSH and CLI

I found out using the GUI on QNAP if you do not pay attention it caches the docker images. Apparently, I had pulled the image a while back. I did it again through the GUI and now have an updated node running.

I’m now running v1.42 and got ingress. Now, I’m wondering what would happen for the next update. Will storj watchtower work? We shall wait and see…

If you could share your docker node creation command it would help me in the future. (Not fully versed yet with Docker)