Node Status, last Contact "17704127h 18m ago" since Update

Hi all
Since the last Update, my node has a fault. With the following Logs:

2020-09-04T23:12:50.518958282Z 2020-09-04T23:12:49.760Z ERROR orders archiving orders {“error”: “ordersdb error: database is locked”, “errorVer bose”: “ordersdb error: database is locked\n\tstorj.io/storj/storagenode/storagenodedb.(*ordersDB).archiveOne:242\n\tstorj.io/storj/storagenode/storageno dedb.(*ordersDB).Archive:206\n\tstorj.io/storj/storagenode/orders.(*Service).handleBatches.func2:264\n\tstorj.io/storj/storagenode/orders.(*Service).hand leBatches:281\n\tstorj.io/storj/storagenode/orders.(*Service).sendOrdersFromDB.func1:214\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2020-09-04T23:14:54.578561444Z 2020-09-04T23:14:54.568Z INFO Got a signal from the OS: “terminated”
2020-09-04T23:14:54.626003073Z 2020-09-04T23:14:54.625Z ERROR orders cleaning DB archive {“error”: “ordersdb error: context canceled”, “errorVerbo se”: “ordersdb error: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*ordersDB).CleanArchive:323\n\tstorj.io/storj/storagenode/orders.(*Se rvice).CleanArchive:164\n\tstorj.io/storj/storagenode/orders.(*Service).Run.func2:148\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-09-04T23:14:55.034309516Z 2020-09-04T23:14:55.027Z ERROR piecestore:cache error getting current space used calculation: {“error”: “contex t canceled; 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\n— context canceled”}
2020-09-04T23:14:58.331251323Z Error: debug: http: Server closed

Can anyone help?
Thanks

How is your HDD connected ? Have you also checked if your HDD is SMR ?

Is it online?

My HDD is a internal Disk to the Host Server. There is am VM on QEMU Base on it. The disk is online and there is mlre than 300gb free disk space. What I need tho check foe SMR i dont know this.
No, Node is not online but data is visible on the Dashboard… Like stored data, used bamdwith etc.
But Port is still opened.
What can I do?
Am I no out of the System when Im now offline too long?

What should I do now?

Thanks

  1. Stop the storagenode
  2. Check your disk for errors, fix if found
  3. Start the storagenode

The database is locked is happening with nodes with a slow disk or when the database is fragmented too much.
Usually it resolves itself after a while, but the restart is helping too. Also, you can try to vacuum your database:


By the way what the filesystem on that drive?

I restarted a few times, but not working again. I started now the vacuum command. I started this never before. My Drive ist on ext4. I will update you, when the vacuum command is done.
Thankls

okay, script runned:

storagenode
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
storagenode

Now started and since 57m the docker is running but node offline…

Ok, if you do not see any other errors in your logs, then please, process with a standard checklist for offline:

Ah, now it seems to be online again. Am I now disqualified because of too long offline?
What should I do now?

Keep it running :slight_smile:
The disqualification for downtime is currently not enabled.

So I keep it up and running.
Great, thanks

1 Like