Node dashboard indicates “online” but the bandwidth and utilization numbers are not refreshing.
1 Like
It is refreshed once or twice in 24h. The points on the graph is one day sliced.
2 Likes
So the arrow next to the Storj logo is not a refresh button? It seemed to have updated the numbers before but if all is running fine then I’ll stop refreshing with that button.
1 Like
You can check it - leave it for 12h+ and then check the usage, then click Refresh button on the Dashboard and compare.
Then refresh the page in the browser and compare.
As far as I remember, the autoupdate function was disabled, but maybe it is working again I didn’t track.
1 Like
I think the 12h is only for disk usage. I’m pretty sure the bandwidth usage is updated more frequently. Probably real time or about once an hour when the bandwidth rollups take place.
To clarify, there is a difference between refreshing the page and refreshing the underlying data.
The page is refreshed when you click that refresh button (and as far as I can tell is never automatically refreshed). At that point it pulls new data from the storagenode db’s.
The underlying data for storage is recalculated and sent back to the nodes once every 12+h by the satellite. Se when you refresh the page it shows the last data as reported back to the node. Bandwidth is tracked by the node itself, but there is a process every hour that does a rollup on those bandwidth numbers. It could either be real time if the dashboard includes not only rollups but also bandwidth usage that hasn’t been rolled up yet or once every hour if it only shows rolled up data.
Hope that helps!
1 Like
Thanks so much for your reply. It makes things a bit more understandable. I don’t understand the entire payout or storage system and I just have to trust the Storj organization to keep up with things. I did receive my first months earnings of .02 USD 
My biggest frustration with the Storj program is that it is very unstable and susceptible to shut down at any time. After shut down I have to delete and reinstall the program to get it back online. I’m unsure how to fix this beccause it’s hurting my “uptime”. It happened today when I did a browser restore to check about the bandwidth update. Any suggestions about getting the program to settle down and keep running would be greatly appreciated.
1 Like
Best way to start would be to have a look at your logs and look for any errors that happened prior to it shutting itself down.
1 Like
Not too tech savy but here is the last 20 from the logs. I saw errors but I’m way over my head as to what they mean or what I need to do to fix them
2020-10-07T12:08:07.513-0400 INFO Telemetry enabled
2020-10-07T12:08:07.523-0400 INFO db.migration Database Version {“version”: 45}
2020-10-07T12:08:09.068-0400 INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-10-07T12:08:29.149-0400 ERROR preflight:localtime unable to get satellite system time {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “rpc: context deadline exceeded”, “errorVerbose”: “rpc: context deadline exceeded\n\tstorj.io/common/rpc.Dialer.dialTransport:211\n\tstorj.io/common/rpc.Dialer.dial:188\n\tstorj.io/common/rpc.Dialer.DialNodeURL:148\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).getSatelliteTime:110\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check.func1:67\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2020-10-07T12:08:29.149-0400 INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-10-07T12:08:29.149-0400 INFO Node 1wLVsXkBgctVLRk4Pq3hPYMmBcPou8mmZ1sX4nqH6yyuZg2pJ5 started
2020-10-07T12:08:29.150-0400 INFO Public server started on [::]:28967
2020-10-07T12:08:29.150-0400 INFO Private server started on 127.0.0.1:7778
2020-10-07T12:08:29.150-0400 INFO trust Scheduling next refresh {“after”: “5h11m37.491823606s”}
2020-10-07T12:08:29.150-0400 INFO bandwidth Performing bandwidth usage rollups
2020-10-07T12:08:29.150-0400 WARN piecestore:monitor Disk space is less than requested. Allocated space is {“bytes”: 3998979668352}
2020-10-07T12:08:34.561-0400 INFO piecestore upload started {“Piece ID”: “7PJH7XI2X4WGH7CN7TCEG5MW3NU3SZF46AIWMQ6OFDTUOR7XQV2A”, “Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “Action”: “PUT”, “Available Space”: 3876178956288}
2020-10-07T12:08:34.595-0400 INFO piecestore uploaded {“Piece ID”: “7PJH7XI2X4WGH7CN7TCEG5MW3NU3SZF46AIWMQ6OFDTUOR7XQV2A”, “Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “Action”: “PUT”}
2020-10-07T12:08:35.871-0400 ERROR piecestore:cache error getting current used space: {“error”: “FindNextFile G:\StorjFiles\blobs\6r2fgwqz3manwt4aogq343bfkh2n5vvg4ohqqgggrrunaaaaaaaa\fb: The file or directory is corrupted and unreadable.”}
2020-10-07T12:08:35.871-0400 ERROR services unexpected shutdown of a runner {“name”: “piecestore:cache”, “error”: “FindNextFile G:\StorjFiles\blobs\6r2fgwqz3manwt4aogq343bfkh2n5vvg4ohqqgggrrunaaaaaaaa\fb: The file or directory is corrupted and unreadable.”}2020-10-07T12:08:35.871-0400 ERROR contact:service ping satellite failed {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “attempts”: 1, “error”: “ping satellite error: rpc: context canceled”, “errorVerbose”: “ping satellite error: rpc: context canceled\n\tstorj.io/common/rpc.Dialer.dialTransport:211\n\tstorj.io/common/rpc.Dialer.dial:188\n\tstorj.io/common/rpc.Dialer.DialNodeURL:148\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2020-10-07T12:08:35.871-0400 ERROR nodestats:cache Get pricing-model/join date failed
{“error”: “context canceled”}
2020-10-07T12:08:35.872-0400 INFO contact:service context cancelled {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”}
2020-10-07T12:08:36.372-0400 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-07T12:08:36.554-0400 FATAL Unrecoverable error {“error”: “FindNextFile G:\StorjFiles\blobs\6r2fgwqz3manwt4aogq343bfkh2n5vvg4ohqqgggrrunaaaaaaaa\fb: The file or directory is corrupted and unreadable.”}
Even though the node shows “online” in green, the screen reverted back to a screen that was displayed earlier today. I’m not so sure that I’m really even online.
1 Like
This is indication of the problem with this disk.
Please, stop the storagenode and run chkdsk /f G: as an Administrator
1 Like
Rebooted as “offline” , refreshed DUC and rebooted Storj again and will not come online or open
Removed and re-installed, showing this screen that has been like this all day
Wait! Wait! got an updated bandwidth usage with the refresh button…showing 28.9 GB
1 Like
Are errors gone after chkdsk?
1 Like
Yes, it appears to be smooth sailing when checking the last 20.
3 Likes