Null value in column "pqgroup_eusage" violates not-null constraintDETAIL: Failing row contains (6, 4, 0/259, data1, null, 4831838208, root, root, 755, 2017-02-14 17:12:34.201143 00, data1, f, no, 0, 0, 2015/4, null, null)

@exelan Hello again. Your reported:

is actually an instance of the issue I referenced in this thread as related but not the same.

ie this thread covers the error re [quote=“phillxnet, post:7, topic:2841”]
null value in column “pqgroup_eusage” violates not-null constraint
[/quote]

But you have pasted:

which is covered in the related issue I linked before:

and later in that thread (where a few report downgrading to set versions then upgrading again) as a fix to give the db another shot at the migration. However later on (it’s an old thread now) @suman details when he released a fix for the db migration issue that caused the “storageadmin_share.pqgroup_rusage does not exist” reports in the first place. That is the new code expects a database field that failed to get added due to the failed database migration.

And so given your rather constrained options currently and your inevitable (and evidently inconvenient) requirement to re-establish ssh access I thought I’d report my findings on just upgrading 2 very different machines from:

3.8.16-10 to 3.9.0-7

where they both then came up on the dashboard (and some other pages) showing the:

... column storageadmin_share.pqgroup_rusage does not exist LINE 1:

In both cases a consequent reboot (something you can still do remotely as I understand it) and a little pause for the new db migrations to take place, and both machines are now back to normal function.

Very much depends on if your machine got the new fix by @suman in 3.9.0-4 but if so you may well already have a fix in place and just need to reboot. Or if your version is not new enough then you may still have enough UI working to upgrade to beyond that fix and be on the home run again. You didn’t specify the version you had upgraded from and to though.

So in short, previously you had only the option to downgrade to try and trigger the db migration attempt again:

Where as now you may be able to receive a fix via an upgrade, which the UI can do(if it allows it given the reported issue) and if you haven’t already received it of course.

Hope that helps.