I’m not gonna lie, the operation of a storj node on v3 is starting to break me. i’ve come home from work today, checked on my node and its offline. Now i’ve had other issues in the past but i thought these where sorted. I’ve had hundreds of hours continuous use with no problems then this. Trouble shooting so far. checked port = open. restarted node = offline. just stuck for solution. changed alpha for beta at the end of command = offline.
Any clues??
Checked dns? Firewall? Is your node version uptodate
dns server 8.8.8.8. Just checked port again. it says open. version 23.2.
do you use a dynamic dns service or do you type in your ip in the run command?
yes dynamic dns. Used for years on v2 as well
Some have had to update or renew their dns for it to go online again.
Have you checked that dynamic dns works or if the problem lies there.
What does the log say when you start the node
ddns comes back on port open tool as open using the address rather than ip.
2019-10-10T17:58:28.364Z INFO Configuration loaded from: /app/config/config.yaml
2019-10-10T17:58:28.386Z INFO Operator email: sbarr***@googlemail.com
2019-10-10T17:58:28.386Z INFO operator wallet: 0x*****
2019-10-10T17:58:30.484Z INFO version running on version v0.23.2
2019-10-10T17:58:30.506Z INFO db.migration Database Version {“version”: 25}
2019-10-10T17:58:30.512Z INFO contact:chore Storagenode contact chore starting up
2019-10-10T17:58:30.513Z INFO Node 12gkDpqRzzBdSxGQ4cpjbFpg8unNAv9QT1JEBi9BpaxzxHK1Nd3 started
2019-10-10T17:58:30.513Z INFO Public server started on [::]:28967
2019-10-10T17:58:30.514Z INFO bandwidth Performing bandwidth usage rollups
2019-10-10T17:58:30.524Z INFO Private server started on 127.0.0.1:7778
2019-10-10T17:58:30.606Z INFO piecestore:monitor Remaining Bandwidth {“bytes”: 12797876066304}
2019-10-10T17:58:30.638Z INFO version running on version v0.23.2
2019-10-10T18:13:32.031Z INFO version running on version v0.23.2
2019-10-10T18:21:22.503Z INFO Got a signal from the OS: “terminated”
2019-10-10T18:29:30.963Z INFO Configuration loaded from: /app/config/config.yaml
2019-10-10T18:29:30.992Z INFO Operator email: sbarr***
2019-10-10T18:29:30.992Z INFO operator wallet: 0x****
2019-10-10T18:29:33.291Z INFO version running on version v0.23.2
2019-10-10T18:29:33.349Z INFO db.migration Database Version {“version”: 25}
2019-10-10T18:29:33.396Z INFO bandwidth Performing bandwidth usage rollups
2019-10-10T18:29:33.396Z INFO contact:chore Storagenode contact chore starting up
2019-10-10T18:29:33.397Z INFO Node 12gkDpqRzzBdSxGQ4cpjbFpg8unNAv9QT1JEBi9BpaxzxHK1Nd3 started
2019-10-10T18:29:33.397Z INFO Public server started on [::]:28967
2019-10-10T18:29:33.397Z INFO Private server started on 127.0.0.1:7778
2019-10-10T18:29:33.477Z INFO piecestore:monitor Remaining Bandwidth {“bytes”: 12797876066304}
2019-10-10T18:29:33.519Z INFO version running on version v0.23.2
after removal of Kademlia, it takes some time to be “ONLINE”. Give it some time.
ok i understand that, but how long should you wait before offline means offline? An hour is a long time to be fair
Wait at least 2 hours without restarting the node.
Do you see any error messages in the logs?
You can check your port here: https://www.yougetsignal.com/tools/open-ports/
Type your DDNS address in the address field and your port in the port field, click the Check
Port [28967]is open on pio***** (read out from site)
It shows online in storjnet.
http://storjnet.info/@12gkDpqRzzBdSxGQ4cpjbFpg8unNAv9QT1JEBi9BpaxzxHK1Nd3
Online yet?
probably as stated Before.
let it run and see if it Changes to online
i appreciate that but its been online for many hours and now its not. hundreds of hours infact.
What is Web dashboard says?
Is you OS - Windows?
If so, try to restart the Docker from the Docker desktop application.
Unfortunately, storjnet can no longer update any status of any node. You’ll note that the uptime bar has not been updated since Oct 5th. This is because storjnet.info is run by a non-active node which does not have a signed operating certificate.
The storjnet operator’s request to operate a signed analytics node has been denied …
So, it looks like we are operating without externally available information on node status until such time as Storj decides to provide such analytics. This is most unfortunate… resulting in some avoidable forum posts and troubleshooting rounds by Storj… but I do understand the security implications involved.
I’m running windows 10 pro. I restarted everything including docker, os and node. This was last night. Kept track of it for a good hour or so. nothing happening on logs or network and node still reported offline. Anyway it was getting late and i just left it running. Woke this morning and its back online. This is strange. i’ve not altered anything other than the regular updates as needed.