Help pls… 
Dashboard says OFFLINE. this is the only ERROR on logs.
ERROR nodestats:cache Get disk space usage query failed {“error”: “context canceled”}
Please, use this checklist:
I think this may actually be a matter of a restarting node because it can’t access the storage device or something. Are you using direct attached storage or network attached? SMB, NFS etc.?
Direct attached. checked everything. still offline and port still closed.
Can you post a bit more of your log. Try stopping the node, starting it and copying the log you see after a few minutes. Perhaps some more context gives us a bit more of a clue what’s going on.
did a ‘docker rm storagenode’. then created a new node. no more ERROR msg but still offline. so i’m thinking its the a port problem. but checked everything and from what i can see nothing seems wrong with my port forward set up.
Storage Node Dashboard ( Node Version: v0.25.1 )
======================
ID 12f1H8srz5PUSmPoRuFuefXCMXUSMJVuCztov5JniRhzyj3h4E1
Last Contact OFFLINE
Uptime 8m38s
Available Used Egress Ingress
Bandwidth 2.9 TB 72.8 GB 4.2 GB 68.5 GB (since Nov 1)
Disk 1.3 TB 0.7 TB
Internal 127.0.0.1:7778
External redzstorj.ddns.net:28967
2019-11-14T02:55:00.322Z INFO Configuration loaded from: /app/config/config.yaml
2019-11-14T02:55:00.337Z INFO Operator email: rvr**@gmail.com
2019-11-14T02:55:00.337Z INFO operator wallet: 0xbc58A8780E2c54**
2019-11-14T02:55:02.139Z INFO version running on version v0.25.1
2019-11-14T02:55:02.159Z INFO db.migration Database Version {“version”: 25}
2019-11-14T02:55:02.170Z INFO contact:chore Storagenode contact chore starting up
2019-11-14T02:55:02.170Z INFO bandwidth Performing bandwidth usage rollups
2019-11-14T02:55:02.170Z INFO Node 12f1H8srz5PUSmPoRuFuefXCMXUSMJVuCztov5JniRhzyj3h4E1 started
2019-11-14T02:55:02.170Z INFO Public server started on [::]:28967
2019-11-14T02:55:02.170Z INFO Private server started on 127.0.0.1:7778
2019-11-14T02:55:02.210Z INFO piecestore:monitor Remaining Bandwidth {“bytes”: 2927217858816}
2019-11-14T02:55:02.384Z INFO version running on version v0.25.1
PS C:\Users\rvroj> docker exec -it storagenode ls -l /app/identity
total 14
-rwxr-xr-x 1 root root 546 Jul 8 22:00 ca.1562623220.cert
-rwxr-xr-x 1 root root 1076 Jul 8 22:00 ca.cert
-rwxr-xr-x 1 root root 241 Jul 8 21:58 ca.key
-rwxr-xr-x 1 root root 1088 Jul 8 22:00 identity.1562623220.cert
-rwxr-xr-x 1 root root 1618 Jul 8 22:00 identity.cert
-rwxr-xr-x 1 root root 241 Jul 8 21:58 identity.key
Please, check every case from the check list. This error is not related to the storage, it’s about the offline, so the connectivity issue.
2 Likes
Yeah, my bad. If there are no errors anymore it must be a normal connection error as @Alexey mentioned. All possible causes and fixes for that are on the topic already linked. Double-check everything even if you set it up right before. Things can change like IPs or firewall rules disappearing. Don’t assume you set anything up correctly already.
1 Like
really tried everything… my only guess now is it’s an ISP problem. thanks for the help guys…
We can try together. But I’m think that your WAN IP doesn’t match the public IP. It’s very often problem, because most of ISP uses CGN today
1 Like
Yes, that’s the problem. You do not have a public IP.
To solve this you have a few options:
- switch the ISP to the other one which can give you a public IP (it could be dynamic, but should match the WAN IP);
- ask your current ISP give you a public IP;
- use a VPN with port forwarding option, such as PIA, ngrok, portmap.io, PureVPN, etc.
1 Like
Thank Alexey for all the help…
need your help one last time cause i’m not really that technical. but im great at following instructions.lol
nwei, can you pls help me set up portmap.io?
i’m getting this error:
PS C:\Users\rvroj> docker logs --tail 20 storagenode
2019-11-17T13:53:22.116Z INFO bandwidth Performing bandwidth usage rollups
2019-11-17T13:53:23.665Z INFO version running on version v0.25.1
2019-11-17T14:08:23.410Z INFO version running on version v0.25.1
2019-11-17T14:11:58.246Z ERROR telemetry failed sending report: lookup collectora.storj.io on 192.168.65.1:53: read udp 172.17.0.2:41963->192.168.65.1:53: i/o timeout
2019-11-17T14:23:23.251Z INFO version running on version v0.25.1
2019-11-17T14:34:06.973Z INFO Got a signal from the OS: “terminated”
2019-11-17T14:34:12.429Z INFO Configuration loaded from: /app/config/config.yaml
2019-11-17T14:34:12.439Z INFO Operator email: rvrojas9@gmail.com
2019-11-17T14:34:12.439Z INFO operator wallet: 0xbc
2019-11-17T14:34:13.541Z INFO version running on version v0.25.1
2019-11-17T14:34:13.588Z INFO db.migration Database Version {“version”: 25}
2019-11-17T14:34:13.608Z INFO bandwidth Performing bandwidth usage rollups
2019-11-17T14:34:13.609Z INFO Node 12f1H8srz5PUSmPoRuFuefXCMXUSMJVuCztov5JniRhzyj3h4E1 started
2019-11-17T14:34:13.609Z INFO Public server started on [::]:28967
2019-11-17T14:34:13.609Z INFO Private server started on 127.0.0.1:7778
2019-11-17T14:34:13.608Z INFO contact:chore Storagenode contact chore starting up
2019-11-17T14:34:13.833Z INFO piecestore:monitor Remaining Bandwidth {“bytes”: 2927217858816}
2019-11-17T14:34:13.833Z WARN piecestore:monitor Disk space is less than requested. Allocating space {“bytes”: 2994339206912}
2019-11-17T14:34:14.609Z INFO version running on version v0.25.1
2019-11-17T14:49:14.677Z INFO version running on version v0.25.1
You should place the generated by portmap.io host with a given port in the ADDRESS parameter in case of docker run and port mapping -p 28967:28967. If your OpenVPN connection is running, then your node should be online.
Also, seems your default DNS does not work, please set the 8.8.8.8 or 1.1.1.1 as a one of the default DNS either on your router or in the configuration of your PC.
1 Like
Got it back online… thanks!
1 Like