Last Contact time on dashboard very long time ago. Node Offline

“Last Contact” on Dashboard - very long time ago.

I know this ight seem repetitive to setup but check:

1.Port is opened on your NAT
2.Check that the IP of your node is the same as your NAT record
3. Check that Windows firewall rule is in place
4. Check that DDNS record is up to date(If no used check your public IP that is same as in config.yml)

Yes I have checked with canyouseeme.com

Yes it is. none of the IPs, nor ports have changed in the past week, however the node has inexplicably been online and offline seemingly randomly.

Running on debian. There is a firewall in place, but the ports are properly opened.

Interesting. I will check this. the DDNS is up to date, but maybe there’s an issue with the config.yml

1 Like

DDNS is fine, and the config.yml doesn’t seem to have anyting in it that isn’t default.

Check your docker command for curly quotes or extra space can lead to issues.

If it is a missing quote, i certainly cannot find it.

docker run --log-driver gelf --log-opt gelf-address=udp://xxxx:12201 -d -p 14960:14002 --restart unless-stopped -p 23880:28967 -e WALLET="xxx" -e EMAIL="michael@xxx.com" -e ADDRESS="x.x.x.x:23880" -e STORAGE="25TB" --mount type=bind,source="/root/.local/share/storj/identity/storj-q160",destination=/app/identity --mount type=bind,source="/tank/storj/storj-q160",destination=/app/config --name storj-q160 storjlabs/storagenode:latest

Try posting it between 3 backticks ```. Also remove your ETH address and email.

if my run command is messed up i will usually try to compare it with a working node’s run command, and if one plans a bit their length will be exactly the same and thus errors are easy to spot…

however why udp? i do believe all storj ports are tcp… but i don’t think i got anything at all there, oh nevermind that seems to be related to your log-driver

i think i switched around some of the parameters of the run command last node i made, and it wouldn’t work before they where in the right sequence.

something like that, can’t remember exactly… switch some around in the run command that i didn’t think mattered but turned out it did.

i would try to follow the sequence of the documentation
https://documentation.storj.io/setup/cli/storage-node

the node clearly worked before, what did you change … i mean are you sure it’s the run command that is doing this? but i suppose it is one of the points with many points of failure…

1 Like

What is in your logs?
https://documentation.storj.io/resources/faq/check-logs

2020-10-23 08:03:14 +00:00 clay001
2020-10-23T08:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 07:08:27 +00:00 clay001
2020-10-23T07:08:27.613Z INFO trust Scheduling next refresh {“after”: “6h44m46.945974806s”}
2020-10-23 07:03:14 +00:00 clay001
2020-10-23T07:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 06:03:14 +00:00 clay001
2020-10-23T06:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 05:03:14 +00:00 clay001
2020-10-23T05:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 04:03:14 +00:00 clay001
2020-10-23T04:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 03:03:14 +00:00 clay001
2020-10-23T03:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 02:03:47 +00:00 clay001
2020-10-23T02:03:47.280Z INFO trust Scheduling next refresh {“after”: “5h4m40.080509481s”}
2020-10-23 02:03:14 +00:00 clay001
2020-10-23T02:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 01:03:14 +00:00 clay001
2020-10-23T01:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 00:03:14 +00:00 clay001
2020-10-23T00:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 23:03:14 +00:00 clay001
2020-10-22T23:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 22:03:14 +00:00 clay001
2020-10-22T22:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 21:03:14 +00:00 clay001
2020-10-22T21:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 20:03:14 +00:00 clay001
2020-10-22T20:03:14.355Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 19:03:14 +00:00 clay001
2020-10-22T19:03:14.356Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 18:03:14 +00:00 clay001
2020-10-22T18:03:14.358Z INFO Private server started on 127.0.0.1:7778
2020-10-22 18:03:14 +00:00 clay001
2020-10-22T18:03:14.358Z INFO Public server started on [::]:28967
2020-10-22 18:03:14 +00:00 clay001
2020-10-22T18:03:14.358Z INFO Node 1KxKQAo3EEirpgvMgEb7Kg53GpXJW9mWzZ1oHNSjuJsWDsjbmB started
2020-10-22 18:03:14 +00:00 clay001
2020-10-22T18:03:14.358Z INFO trust Scheduling next refresh {“after”: “8h0m32.745478603s”}
2020-10-22 18:03:14 +00:00 clay001
2020-10-22T18:03:14.354Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 18:03:14 +00:00 clay001
2020-10-22T18:03:14.354Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-10-22 18:03:13 +00:00 clay001
2020-10-22T18:03:13.823Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-10-22 18:03:13 +00:00 clay001
2020-10-22T18:03:13.330Z INFO db.migration Database Created {“version”: 45}
2020-10-22 18:03:09 +00:00 clay001
2020-10-22T18:03:09.911Z INFO Telemetry enabled
2020-10-22 18:03:09 +00:00 clay001
2020-10-22T18:03:09.481Z INFO Operator wallet {“Address”: “xx”}
2020-10-22 18:03:09 +00:00 clay001
2020-10-22T18:03:09.481Z INFO Operator email {“Address”: “michael@xx.com”}
2020-10-22 18:03:09 +00:00 clay001
2020-10-22T18:03:09.386Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}

And again, other than updating the node, nothing has changed in the port forwarding configuration and such.

It seems almost like it’s DQ’d but the web dashboard doesn’t show this?

You have specified a wrong external address and port for this NodeID. It registered with a different port than you showed to us. Please, check your command again and especially - your external address.
If you have specified it in the config.yaml, then please, remove or comment out it.

When you checking on the yougetsignal, please, use the external address and port from the -e ADDRESS option.

How can you tell this from the logs?

I never specify anything in config.yaml, it looks to be standard.

You showed your NodeID. I have a limited access to the satellites to check the node’s info.
And also please, check your identity:

i think he checked it from your node id.

yes the log and the run command you gave above seems to be consistent

external ip:23880 routed internal ip:28967 and then internal docker container connects over local ip:28967
seem right from what i can tell

I’m sorry that was a similiar log but from a different node ID.

Here is the correct NODE ID with logs from past 24 hours

2020-10-23 07:55:17 +00:00 bcn003
2020-10-23T07:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 06:55:17 +00:00 bcn003
2020-10-23T06:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 06:19:08 +00:00 bcn003
2020-10-23T06:19:08.217Z INFO trust Scheduling next refresh {“after”: “4h19m23.201105067s”}
2020-10-23 05:55:17 +00:00 bcn003
2020-10-23T05:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 04:55:17 +00:00 bcn003
2020-10-23T04:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 03:55:17 +00:00 bcn003
2020-10-23T03:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 02:55:17 +00:00 bcn003
2020-10-23T02:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 01:55:17 +00:00 bcn003
2020-10-23T01:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-23 00:55:17 +00:00 bcn003
2020-10-23T00:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 23:55:17 +00:00 bcn003
2020-10-22T23:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 23:13:17 +00:00 bcn003
2020-10-22T23:13:17.557Z INFO trust Scheduling next refresh {“after”: “7h5m50.026333232s”}
2020-10-22 22:55:17 +00:00 bcn003
2020-10-22T22:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 21:55:17 +00:00 bcn003
2020-10-22T21:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 20:55:17 +00:00 bcn003
2020-10-22T20:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 19:55:17 +00:00 bcn003
2020-10-22T19:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 19:19:33 +00:00 bcn003
2020-10-22T19:19:33.482Z WARN console:service unable to get Satellite URL {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted”, “errorVerbose”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted\n\tstorj.io/storj/storagenode/trust.(*Pool).getInfo:228\n\tstorj.io/storj/storagenode/trust.(*Pool).GetNodeURL:167\n\tstorj.io/storj/storagenode/console.(*Service).GetDashboardData:160\n\tstorj.io/storj/storagenode/console/consoleapi.(*StorageNode).StorageNode:44\n\tnet/http.HandlerFunc.ServeHTTP:2042\n\tgithub.com/gorilla/mux.(*Router).ServeHTTP:210\n\tnet/http.serverHandler.ServeHTTP:2843\n\tnet/http.(*conn).serve:1925”}
2020-10-22 18:55:17 +00:00 bcn003
2020-10-22T18:55:17.305Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 18:45:44 +00:00 bcn003
2020-10-22T18:45:44.269Z WARN console:service unable to get Satellite URL {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted”, “errorVerbose”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted\n\tstorj.io/storj/storagenode/trust.(*Pool).getInfo:228\n\tstorj.io/storj/storagenode/trust.(*Pool).GetNodeURL:167\n\tstorj.io/storj/storagenode/console.(*Service).GetDashboardData:160\n\tstorj.io/storj/storagenode/console/consoleapi.(*StorageNode).StorageNode:44\n\tnet/http.HandlerFunc.ServeHTTP:2042\n\tgithub.com/gorilla/mux.(*Router).ServeHTTP:210\n\tnet/http.serverHandler.ServeHTTP:2843\n\tnet/http.(*conn).serve:1925”}
2020-10-22 18:45:03 +00:00 bcn003
2020-10-22T18:45:03.085Z WARN console:service unable to get Satellite URL {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted”, “errorVerbose”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted\n\tstorj.io/storj/storagenode/trust.(*Pool).getInfo:228\n\tstorj.io/storj/storagenode/trust.(*Pool).GetNodeURL:167\n\tstorj.io/storj/storagenode/console.(*Service).GetDashboardData:160\n\tstorj.io/storj/storagenode/console/consoleapi.(*StorageNode).StorageNode:44\n\tnet/http.HandlerFunc.ServeHTTP:2042\n\tgithub.com/gorilla/mux.(*Router).ServeHTTP:210\n\tnet/http.serverHandler.ServeHTTP:2843\n\tnet/http.(*conn).serve:1925”}
2020-10-22 18:41:23 +00:00 bcn003
2020-10-22T18:41:23.595Z WARN console:service unable to get Satellite URL {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted”, “errorVerbose”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted\n\tstorj.io/storj/storagenode/trust.(*Pool).getInfo:228\n\tstorj.io/storj/storagenode/trust.(*Pool).GetNodeURL:167\n\tstorj.io/storj/storagenode/console.(*Service).GetDashboardData:160\n\tstorj.io/storj/storagenode/console/consoleapi.(*StorageNode).StorageNode:44\n\tnet/http.HandlerFunc.ServeHTTP:2042\n\tgithub.com/gorilla/mux.(*Router).ServeHTTP:210\n\tnet/http.serverHandler.ServeHTTP:2843\n\tnet/http.(*conn).serve:1925”}
2020-10-22 17:55:17 +00:00 bcn003
2020-10-22T17:55:17.305Z INFO Private server started on 127.0.0.1:7778
2020-10-22 17:55:17 +00:00 bcn003
2020-10-22T17:55:17.305Z INFO Public server started on [::]:28967
2020-10-22 17:55:17 +00:00 bcn003
2020-10-22T17:55:17.305Z INFO Node 1BLkAg5edkUKX1W9UU2EwUJoZ1X4UvNhoPdd1BVKFdGW5n8EG9 started
2020-10-22 17:55:17 +00:00 bcn003
2020-10-22T17:55:17.304Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 17:55:17 +00:00 bcn003
2020-10-22T17:55:17.304Z INFO trust Scheduling next refresh {“after”: “5h17m59.636803079s”}
2020-10-22 17:55:17 +00:00 bcn003
2020-10-22T17:55:17.304Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-10-22 17:55:16 +00:00 bcn003
2020-10-22T17:55:16.423Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-10-22 17:55:13 +00:00 bcn003
2020-10-22T17:55:13.431Z INFO db.migration Database Version {“version”: 45}
2020-10-22 17:55:13 +00:00 bcn003
2020-10-22T17:55:13.423Z INFO Telemetry enabled
2020-10-22 17:55:12 +00:00 bcn003
2020-10-22T17:55:12.446Z INFO Operator email {“Address”: “michael@xxx.com”}
2020-10-22 17:55:12 +00:00 bcn003
2020-10-22T17:55:12.446Z INFO Operator wallet {“Address”: “xxx”}
2020-10-22 17:55:12 +00:00 bcn003
2020-10-22T17:55:12.434Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-10-22 17:52:20 +00:00 bcn003
Error: debug: http: Server closed
2020-10-22 17:52:12 +00:00 bcn003
2020-10-22T17:52:12.049Z ERROR servers unexpected shutdown of a runner {“name”: “debug”, “error”: “debug: http: Server closed”, “errorVerbose”: “debug: http: Server closed\n\tstorj.io/private/debug.(*Server).Run.func2:108\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2020-10-22 17:52:11 +00:00 bcn003
2020-10-22T17:52:11.548Z INFO Got a signal from the OS: “terminated”
2020-10-22 17:43:04 +00:00 bcn003
2020-10-22T17:43:04.204Z WARN console:service unable to get Satellite URL {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted”, “errorVerbose”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted\n\tstorj.io/storj/storagenode/trust.(*Pool).getInfo:228\n\tstorj.io/storj/storagenode/trust.(*Pool).GetNodeURL:167\n\tstorj.io/storj/storagenode/console.(*Service).GetDashboardData:160\n\tstorj.io/storj/storagenode/console/consoleapi.(*StorageNode).StorageNode:44\n\tnet/http.HandlerFunc.ServeHTTP:2042\n\tgithub.com/gorilla/mux.(*Router).ServeHTTP:210\n\tnet/http.serverHandler.ServeHTTP:2843\n\tnet/http.(*conn).serve:1925”}
2020-10-22 17:37:38 +00:00 bcn003
2020-10-22T17:37:38.193Z INFO Private server started on 127.0.0.1:7778
2020-10-22 17:37:38 +00:00 bcn003
2020-10-22T17:37:38.193Z INFO Public server started on [::]:28967
2020-10-22 17:37:38 +00:00 bcn003
2020-10-22T17:37:38.193Z INFO Node 1BLkAg5edkUKX1W9UU2EwUJoZ1X4UvNhoPdd1BVKFdGW5n8EG9 started
2020-10-22 17:37:38 +00:00 bcn003
2020-10-22T17:37:38.193Z INFO trust Scheduling next refresh {“after”: “5h59m19.856124981s”}
2020-10-22 17:37:38 +00:00 bcn003
2020-10-22T17:37:38.193Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 17:37:38 +00:00 bcn003
2020-10-22T17:37:38.192Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-10-22 17:37:37 +00:00 bcn003
2020-10-22T17:37:37.326Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-10-22 17:37:34 +00:00 bcn003
2020-10-22T17:37:34.867Z INFO db.migration Database Version {“version”: 45}
2020-10-22 17:37:34 +00:00 bcn003
2020-10-22T17:37:34.859Z INFO Telemetry enabled
2020-10-22 17:37:33 +00:00 bcn003
2020-10-22T17:37:33.592Z INFO Operator email {“Address”: “michael@easybitatm.com”}
2020-10-22 17:37:33 +00:00 bcn003
2020-10-22T17:37:33.592Z INFO Operator wallet {“Address”: “0x37C611913ac8A0f3004E3180606720bf186588d6”}
2020-10-22 17:37:33 +00:00 bcn003
2020-10-22T17:37:33.561Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-10-22 17:37:18 +00:00 bcn003
Error: debug: http: Server closed
2020-10-22 17:37:17 +00:00 bcn003
2020-10-22T17:37:17.392Z ERROR servers unexpected shutdown of a runner {“name”: “debug”, “error”: “debug: http: Server closed”, “errorVerbose”: “debug: http: Server closed\n\tstorj.io/private/debug.(*Server).Run.func2:108\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2020-10-22 17:37:16 +00:00 bcn003
2020-10-22T17:37:16.892Z INFO Got a signal from the OS: “terminated”
2020-10-22 17:36:58 +00:00 bcn003
2020-10-22T17:36:58.796Z WARN console:service unable to get Satellite URL {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted”, “errorVerbose”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted\n\tstorj.io/storj/storagenode/trust.(*Pool).getInfo:228\n\tstorj.io/storj/storagenode/trust.(*Pool).GetNodeURL:167\n\tstorj.io/storj/storagenode/console.(*Service).GetDashboardData:160\n\tstorj.io/storj/storagenode/console/consoleapi.(*StorageNode).StorageNode:44\n\tnet/http.HandlerFunc.ServeHTTP:2042\n\tgithub.com/gorilla/mux.(*Router).ServeHTTP:210\n\tnet/http.serverHandler.ServeHTTP:2843\n\tnet/http.(*conn).serve:1925”}
2020-10-22 17:13:41 +00:00 bcn003
2020-10-22T17:13:41.354Z WARN console:service unable to get Satellite URL {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted”, “errorVerbose”: “storage node dashboard service error: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted\n\tstorj.io/storj/storagenode/trust.(*Pool).getInfo:228\n\tstorj.io/storj/storagenode/trust.(*Pool).GetNodeURL:167\n\tstorj.io/storj/storagenode/console.(*Service).GetDashboardData:160\n\tstorj.io/storj/storagenode/console/consoleapi.(*StorageNode).StorageNode:44\n\tnet/http.HandlerFunc.ServeHTTP:2042\n\tgithub.com/gorilla/mux.(*Router).ServeHTTP:210\n\tnet/http.serverHandler.ServeHTTP:2843\n\tnet/http.(*conn).serve:1925”}
2020-10-22 17:12:42 +00:00 bcn003
2020-10-22T17:12:42.031Z INFO db.migration Database Version {“version”: 45}
2020-10-22 17:12:42 +00:00 bcn003
2020-10-22T17:12:42.023Z INFO Telemetry enabled
2020-10-22 17:12:41 +00:00 bcn003
2020-10-22T17:12:41.121Z INFO Operator email {“Address”: “michael@xxx.com”}
2020-10-22 17:12:41 +00:00 bcn003
2020-10-22T17:12:41.122Z INFO Operator wallet {“Address”: “xxx”}
2020-10-22 17:12:41 +00:00 bcn003
2020-10-22T17:12:41.107Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-10-22 17:12:25 +00:00 bcn003
Error: debug: http: Server closed
2020-10-22 17:12:24 +00:00 bcn003
2020-10-22T17:12:24.869Z ERROR servers unexpected shutdown of a runner {“name”: “debug”, “error”: “debug: http: Server closed”, “errorVerbose”: “debug: http: Server closed\n\tstorj.io/private/debug.(*Server).Run.func2:108\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2020-10-22 17:12:24 +00:00 bcn003
2020-10-22T17:12:24.368Z INFO Got a signal from the OS: “terminated”
2020-10-22 15:13:41 +00:00 bcn003
2020-10-22T15:13:41.142Z INFO trust Scheduling next refresh {“after”: “6h28m31.50542944s”}
2020-10-22 15:03:15 +00:00 bcn003
2020-10-22T15:03:15.943Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 14:03:15 +00:00 bcn003
2020-10-22T14:03:15.943Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 13:03:15 +00:00 bcn003
2020-10-22T13:03:15.943Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 12:03:15 +00:00 bcn003
2020-10-22T12:03:15.943Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 11:03:15 +00:00 bcn003
2020-10-22T11:03:15.943Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 10:03:15 +00:00 bcn003
2020-10-22T10:03:15.944Z INFO Private server started on 127.0.0.1:7778
2020-10-22 10:03:15 +00:00 bcn003
2020-10-22T10:03:15.943Z INFO trust Scheduling next refresh {“after”: “5h10m24.562503872s”}
2020-10-22 10:03:15 +00:00 bcn003
2020-10-22T10:03:15.944Z INFO Public server started on [::]:28967
2020-10-22 10:03:15 +00:00 bcn003
2020-10-22T10:03:15.944Z INFO Node 1BLkAg5edkUKX1W9UU2EwUJoZ1X4UvNhoPdd1BVKFdGW5n8EG9 started
2020-10-22 10:03:15 +00:00 bcn003
2020-10-22T10:03:15.943Z INFO bandwidth Performing bandwidth usage rollups
2020-10-22 10:03:15 +00:00 bcn003
2020-10-22T10:03:15.943Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-10-22 10:03:15 +00:00 bcn003
2020-10-22T10:03:15.026Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-10-22 10:03:11 +00:00 bcn003
2020-10-22T10:03:11.202Z INFO db.migration Database Version {“version”: 45}
2020-10-22 10:03:11 +00:00 bcn003
2020-10-22T10:03:11.194Z INFO Telemetry enabled
2020-10-22 10:03:09 +00:00 bcn003
2020-10-22T10:03:09.657Z INFO Operator wallet {“Address”: “xxx”}
2020-10-22 10:03:09 +00:00 bcn003
2020-10-22T10:03:09.657Z INFO Operator email {“Address”: “michael@xxx.com”}
2020-10-22 10:03:09 +00:00 bcn003
2020-10-22T10:03:09.634Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-10-22 08:58:12 +00:00 bcn003
Error: debug: http: Server closed
2020-10-22 08:58:11 +00:00 bcn003
2020-10-22T08:58:11.179Z ERROR servers unexpected shutdown of a runner {“name”: “debug”, “error”: “debug: http: Server closed”, “errorVerbose”: “debug: http: Server closed\n\tstorj.io/private/debug.(*Server).Run.func2:108\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2020-10-22 08:58:10 +00:00 bcn003
2020-10-22T08:58:10.678Z INFO Got a signal from the OS: “terminated”
1 Like

Neither of those produce anything. However the identity files do exist in /root/.local/share/storj/identity/storj-q160/

Please also note that this node was restarted a few times, this was me manually restarting it to see if that made it start accepting data agai.

This is bcn003, not the storj-q160. Are sure that it’s a right one? :wink:

NVM, that’s seems to be a right one, at least a port is correct.

From this error I can assume that node doesn’t work on the latest version, please, pull the latest image.

This is very suspicious to me. It must work.

Ok, then please, check it there

grep -c BEGIN /root/.local/share/storj/identity/storj-q160/ca.cert
grep -c BEGIN /root/.local/share/storj/identity/storj-q160/identity.cert
1 Like

bcn003 is a server, storj-q160 is a node.

And yes i am 100% this is the correct node. The logs don’t show it its a graylog lack of configuration, but i’m searching for that specific node