Node offline (the external address got changed)

   sudo docker logs --tail 20 storj2
2020-11-02T13:16:48.368Z	INFO	Operator wallet	{"Address": "[ADDRESS]"}
2020-11-02T13:16:48.624Z	INFO	Telemetry enabled
2020-11-02T13:16:48.649Z	INFO	db.migration	Database Version	{"version": 45}
2020-11-02T13:16:49.488Z	INFO	preflight:localtime	start checking local system clock with trusted satellites' system clock.
2020-11-02T13:16:50.084Z	INFO	preflight:localtime	local system clock is in sync with trusted satellites' system clock.
2020-11-02T13:16:50.084Z	INFO	bandwidth	Performing bandwidth usage rollups
2020-11-02T13:16:50.085Z	INFO	Node [NODE_ID] started
2020-11-02T13:16:50.085Z	INFO	Public server started on [::]:28967
2020-11-02T13:16:50.085Z	INFO	Private server started on 127.0.0.1:7778
2020-11-02T13:16:50.086Z	INFO	trust	Scheduling next refresh	{"after": "7h3m9.61227678s"}
2020-11-02T13:17:10.306Z	INFO	orders.1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE	sending	{"count": 141}
2020-11-02T13:17:10.306Z	INFO	orders.12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB	sending	{"count": 151}
2020-11-02T13:17:10.307Z	INFO	orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S	sending	{"count": 88}
2020-11-02T13:17:10.306Z	INFO	orders.121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6	sending	{"count": 115}
2020-11-02T13:17:10.306Z	INFO	orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs	sending	{"count": 123}
2020-11-02T13:17:10.495Z	INFO	orders.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S	finished
2020-11-02T13:17:10.691Z	INFO	orders.1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE	finished
2020-11-02T13:17:10.905Z	INFO	orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs	finished
2020-11-02T13:17:11.253Z	INFO	orders.121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6	finished
2020-11-02T13:17:11.490Z	INFO	orders.12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB	finished


CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS              PORTS                                                NAMES
ad407fb2b9b9        storjlabs/storagenode:latest   "/entrypoint"            12 minutes ago      Up 12 minutes       0.0.0.0:14002->14002/tcp, 0.0.0.0:28967->28967/tcp   storj2
a560db1a10ee        storjlabs/watchtower           "/watchtower watchto…"   46 minutes ago      Up 46 minutes                                                            watchtower

After updating my node manually and re-running I’m getting stats indicating that my node is down but I’m not sure why, any thoughts?

Updated to latest version and relaunched according to the guide on storj software updates.

UPDATE:
Following the guide here: Node stopped responding overnight. Still shows OFFLINE after restart helped! My router grabbed a new ip and the computer that I have no-ip installed on was not with me. I’ll need to investigate no-ip for my linux server. The timing of the two events was curiously close.

UPDATE 2: (since I’ve personally benefited from mining these forums)
I’m going to assuming having no-ip on a laptop was a bad idea and the new ip allocation was really no-ip grabbing the ip location of the laptop that my wife took to work (personal laptop that she uses to do homework in down time) Anywho, this caused the node to go offline. I went ahead and added this script as a 10min cron job to the server (computer) running storj https://github.com/theonemule/no-ip

I’ve now got automated docker image updates and automated ip lookups on the host device.

1 Like

if you move the computer that has no-ip on it then where ever it is online from the no-ip would redirect to… when using stuff like no-ip you should have the software running so it can adjust the addresses live, else you are asking for trouble…

it is possible that your router was waiting for an excuse to switch ip, and you shutting down the nodes simply gave it time to run it’s firmware update, reboot, or whatever it did that happened to change the ip address…

can’t say for sure that is what happened… but could be something like that… if we are excluding random chance… or that you didn’t notice the node was offline before you updated is also an option ofc…

1 Like

Good call. I imagine that my wife logged into the laptop at her work and the ip changed. The no-ip is on my user of the laptop but it’s certainly possible that the service ran in the background as I didn’t fully log out. I went ahead and started using https://github.com/theonemule/no-ip as a 10 min cron job on the host computer (ubuntu server os). :crossed_fingers: hopefully this will be a more stable node!

2 Likes

something i wrote a while back, has a few tips and tricks, tho it is rather long and a bit of a mess…

You can try to setup your router to update the DDNS address without DUC on your laptop.

3 Likes