My Node is offline,
This graphic is a joke. She says I haven’t been online for years
I get this errors in the log data:
2020-03-15T12:39:53.348+0100 ERROR piecestore:cache error getting current space used calculation: {"error": "context canceled; context canceled; context canceled; context canceled; context canceled", "errorVerbose": "group:\n--- context canceled\n--- context canceled\n--- context canceled\n--- context canceled\n--- context canceled"}
2020-03-15T12:39:53.369+0100 ERROR pieces:trash emptying trash failed {"error": "pieces error: filestore error: context canceled", "errorVerbose": "pieces error: filestore error: context canceled\n\tstorj.io/storj/storage/filestore.(*blobStore).EmptyTrash:127\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).EmptyTrash:309\n\tstorj.io/storj/storagenode/pieces.(*Store).EmptyTrash:329\n\tstorj.io/storj/storagenode/pieces.(*TrashChore).Run.func1:51\n\tstorj.io/common/sync2.(*Cycle).Run:87\n\tstorj.io/common/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-03-15T12:39:53.433+0100 ERROR pieces:trash emptying trash failed {"error": "pieces error: filestore error: context canceled", "errorVerbose": "pieces error: filestore error: context canceled\n\tstorj.io/storj/storage/filestore.(*blobStore).EmptyTrash:127\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).EmptyTrash:309\n\tstorj.io/storj/storagenode/pieces.(*Store).EmptyTrash:329\n\tstorj.io/storj/storagenode/pieces.(*TrashChore).Run.func1:51\n\tstorj.io/common/sync2.(*Cycle).Run:87\n\tstorj.io/common/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-03-15T12:39:53.478+0100 ERROR pieces:trash emptying trash failed {"error": "pieces error: filestore error: context canceled", "errorVerbose": "pieces error: filestore error: context canceled\n\tstorj.io/storj/storage/filestore.(*blobStore).EmptyTrash:127\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).EmptyTrash:309\n\tstorj.io/storj/storagenode/pieces.(*Store).EmptyTrash:329\n\tstorj.io/storj/storagenode/pieces.(*TrashChore).Run.func1:51\n\tstorj.io/common/sync2.(*Cycle).Run:87\n\tstorj.io/common/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-03-15T12:39:53.511+0100 ERROR pieces:trash emptying trash failed {"error": "pieces error: filestore error: context canceled", "errorVerbose": "pieces error: filestore error: context canceled\n\tstorj.io/storj/storage/filestore.(*blobStore).EmptyTrash:127\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).EmptyTrash:309\n\tstorj.io/storj/storagenode/pieces.(*Store).EmptyTrash:329\n\tstorj.io/storj/storagenode/pieces.(*TrashChore).Run.func1:51\n\tstorj.io/common/sync2.(*Cycle).Run:87\n\tstorj.io/common/sync2.(*Cycle).Start.func1:68\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2
The Last Contact time seems very likely to be a clock sync issue on the local OS… or maybe with the BIOS clock and the OS clock.
Can you check free space on your HDD ? I wonder if clearing cache would be any helpful.
It looks like it’s having trouble with your storage. How is it connected to the node?
Its connected with Sata blue intern
ok, iam out. I dont understand the bugs!
Alexey
March 16, 2020, 7:05pm
7
Is it docker version? If so, try to restart the docker from the docker desktop.
docker ps
For the Windows GUI:
Get-Service storagenode*
Please, check the connectivity of your node with this checklist:
It should connect in seconds. There are a few things you should check.
Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port.
If it’s closed, it could still be several things.
Make sure the WAN IP you see in your router settings matches the IP shown on the above page.
Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…
update: now it works and i did nothing, lol. run since 6 days.
hm, i see in the log file, that upload doesnt run. many issues
That’s normal behavior. If enough other nodes finish the transfer before yours does the transfer to your node gets cancelled. Nothing to worry about.
1 Like
thanks!
thought it was strange because I had never had such a high number of crashes. the last month maximum 5%. Should I limit the maximum connections a bit? Has been changed to max 100 in some update.
Alexey
March 23, 2020, 6:42pm
11
Please, comment out this setting and restart the storagenode
I just restarted the storage node because I moved to a larger hard drive, but the massive errors when uploading remain.
Alexey
March 23, 2020, 6:54pm
13
They will not disappear if you didn’t change the physical location.
I exactly copied the storage node to another hard drive and gave the new drive the same drive letter. everything works great, except for the high number of cancellations, which was just as high before the move!
But I didn’t have this problem a month ago
twl
March 23, 2020, 7:31pm
15
I think it’s not neccessary to sync your windows clock with an external tool anymore. At least I didn’t do that with storj v3 and there haven’t been any issues.
The current preflight check of local time with satellite’s time does require SNO to keep time synced. Its a small utility but saves lot of time literally.
1 Like
twl
March 24, 2020, 9:54am
17
Thanks, gonna install sync tool on my nodes!
1 Like
twl
March 24, 2020, 11:12am
18
What would seem to be a good interval between syncs? 1h?
Mine is set to default of 15 mins
twl
March 24, 2020, 1:29pm
20
My default value after installing was 12h
15m sounds reasonable though, I recall using that setting back in good v1 days
