Suspended from Satellite

A couple of days ago (9th), my Pi freaked out, not sure what happened but everything was unresponsive. I couldn’t access any of the services I run from it and the docker daemon was unreachable. So I reset the device, thinking that the STORJ node had already been stopped (so I can’t be doing more anymore damage, right?)

It booted back up fine and I managed to restart STORJ just fine and things seemed ok. Fast forward to today (12th) and I’ve got a suspension from us-central-1 (which is odd because the least of my traffic goes there - I would have expected europe-west-1 or something, I’ll probably get one later).

I’ve been running this node (2nd attempt) for a good 8 months now so the thrill of constantly checking my dashboard has died down (although I still do from time to time just to make sure its up). So SSh’ing into the Pi, I get a permission denied error trying to access any of the files inside my STORJ folder (I’m hoping this is normal, but I feel like its not - feels like at least the config.yaml should be accessible).

My first port of call was to create a help ticket here, it goes without saying that I really don’t want to be disqualified. I’ve read the “your topic is similar to…” threads and it looks like my story is similar to some others (though I didn’t see anything about permission denied errors).

I’m running a Pi4 with a USB3 external hard drive attached (8TB total - 6TB used for STORJ), this hard drive is exclusively for STORJ and the remaining 2TB is for buffer space (I’ve heard about leaving 10% free - and some emergency space).

Checking through the logs, I’m getting a lot of database is locked but luckily no database disk image is malformed (the fate of my previous STORJ attempt way back last year). I’ve restarted my node hoping that will fix the locking issue. The logs say that it managed to load the config.yaml file (the one that results in permission denied when I try to access it myself) so that’s a good sign?

I’m still getting a lot of database is locked messages (though I read somewhere that I should wait 2 hours and they should all go away?). I’m also seeing some download failed usedserialsb error: context canceled errors. There’s also a ton of (what seem to be) successful messages saying that files have been uploaded and downloaded, and my available space on the drive is constantly changing.

I just wanted to post this here in case there is still a problem and it hasnt gone away (I’m aware that I’m now on a timer for disqualification). I’ll close it if it sorts itself out after a couple of hours, although maybe my questions above can still be answered by the community.

If I invest in another 8TB drive, would mirroring them be a good idea? My last STORJ node got corrupted and I lost all of the data (obviously resulting in disqualification). I’d like to avoid this happening again as it’s a waste of everyone’s time and money. The cost of another 8TB is a fraction of my “total held amount”

TL;DR: Got an email from one of the least utilized satellites about being suspended. Seeing a lot of database is locked and usedserialsdb error: context canceled errors. Can’t access my STORJ folder without getting permission denied. 8TB HDD (6TB for STORJ) connected via USB3 to Pi4.

Thanks!

Edit: I ran the audit script (https://support.storj.io/hc/en-us/articles/360030997132-Audits-by-satellite) and my output is as follows:

"118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW"
{
  "totalCount": 15269,
  "successCount": 15205,
  "alpha": 19.99999999999995,
  "beta": 0,
  "unknownAlpha": 16.977382807854255,
  "unknownBeta": 3.02261719214573,
  "score": 1
}
"1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"
{
  "totalCount": 13704,
  "successCount": 13635,
  "alpha": 19.99999999999995,
  "beta": 0,
  "unknownAlpha": 18.309369934006952,
  "unknownBeta": 1.690630065993031,
  "score": 1
}
"121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6"
{
  "totalCount": 22447,
  "successCount": 22363,
  "alpha": 19.99999999999995,
  "beta": 0,
  "unknownAlpha": 13.694370924622643,
  "unknownBeta": 6.305629075377339,
  "score": 1
}
"12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S"
{
  "totalCount": 25722,
  "successCount": 25622,
  "alpha": 19.99999999999995,
  "beta": 0,
  "unknownAlpha": 14.80807944699189,
  "unknownBeta": 5.191920553008092,
  "score": 1
}
"12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs"
{
  "totalCount": 22118,
  "successCount": 22031,
  "alpha": 19.99999999999995,
  "beta": 0,
  "unknownAlpha": 14.57553429096967,
  "unknownBeta": 5.424465709030311,
  "score": 1
}
"12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB"
{
  "totalCount": 1675,
  "successCount": 1646,
  "alpha": 19.99999999999995,
  "beta": 0,
  "unknownAlpha": 16.37509537986143,
  "unknownBeta": 3.6249046201385484,
  "score": 1
}

I don’t understand how to interpret a lot of this, but the success counts are quite high. And I assume a score of 1 is pretty good

This issue maybe fixed in 1.6.3 What version is your node on?

1.5.2. Didn’t realize there was an update, shouldn’t watchtower grab this automatically?

It will, but will take a time