Error starting master database (operation not permitted) after update on QNAP-Nas

beli · August 4, 2020, 3:40pm

which files you mean in detail? i checked all *.db files as you see above. also i checked some samples in the subdirs of config-dir. All are full writeable by owner

utropicmedia-karl · August 4, 2020, 3:40pm

parent directory too?

beli · August 4, 2020, 3:41pm

yes it is 700, with matching ownerships

BrightSilence · August 4, 2020, 3:42pm

Whoops, sorry Karl, I kind of assumed this was about the QNAP app.

utropicmedia-karl · August 4, 2020, 3:46pm

@BrightSilence - no worries. Looks like something else, but you never can be too careful

calebcase · August 4, 2020, 5:06pm

@beli Can you provide us with the docker run command you used to start the container? Can you confirm that the /app/config/config.yaml contains the path inside the container you’ve bind mounted?

calebcase · August 4, 2020, 5:10pm

@user01357 Are you also running on QNAP or is this a different kind of host environment?

beli · August 4, 2020, 5:29pm

Yes - paths are matching - only “change” was upgrade from 1.6.4 to 1.9.5 i think.

docker run -d --restart unless-stopped -p 28967:28967 -p 14002:14002
-e WALLET=“wally”
-e EMAIL=“mailly”
-e ADDRESS=“addressy”
-e STORAGE=“7TB”
-m 4096M
–mount type=bind,source="/share/Container/STORJ/identity",destination=/app/identity
–mount type=bind,source="/share/Container/STORJ/config",destination=/app/config
–stop-timeout 300
–name storagenode storjlabs/storagenode:latest

user01357 · August 4, 2020, 5:51pm

I using the docker image on the QNAP device which updating by watchtower.

immiq · August 4, 2020, 6:36pm

Exactly the same here, docker image in qnap device + watchtower

striker43 · August 4, 2020, 6:40pm

I have the same setup and no problems so far. My watchtower updated to 1,9,5 yesterday…

qookoo · August 10, 2020, 2:13pm

Hello, my QNAP app can’t start after the second day I upgrade to the newest version.

Even I installed the old version still not working.

Here’s the log, thanks.

Alexey · August 10, 2020, 6:22pm

Hello @qookoo,
Welcome to the forum!

For some reason the container on QNAP requires --privileged option in the docker run command.

qookoo · August 10, 2020, 8:38pm

Do you have any tutorial to do this?

or will you solve this problem in the future app update?

I’m new to this, even after googling it still feel confused.

brandon · August 10, 2020, 10:32pm

Hey @qookoo! That is a great question @utropicmedia-karl might be able to give us more information about how to do this or if it going to be updated in the next release.

utropicmedia-karl · August 11, 2020, 5:13am

Hi qookoo,

What is the firmware version of your qnap?

Thanks.

-K

beli · August 11, 2020, 6:25am

If i can also answer

Mine is now 4.4.3.1381, i updated to newest version during debugging

[Firmware Update] Updated system from version 4.4.2.1320(20200529) to 4.4.3.1381(20200729).

on 4.4.2 the system was running since 1.june 2020

Alexey · August 11, 2020, 6:39am

So, the --priveleged start to be required after firmware upgrade?

beli · August 11, 2020, 6:53am

No. The storagenode V1.9.5 was not starting with “operation not permitted” with both firmwares.
To debug the situation i upgraded to actual firmware but no change. Still “operation not permitted”.

qookoo · August 11, 2020, 6:59pm

My QNAP model is TS-231P2.

My system version was 4.4.2.1302, and I update it to 4.4.3.1381 but still not work.