I woke up to my node giving me the same error. Any tips to get it back online. 2020-08-04T15:23:51.445Z INFO Operator email {"Address": "##REDACTED##"} 2020-08-04T15:23:51.445Z INFO Operator wallet {"Address": "##REDACTED##"} Error: Error starting master database on storagenode: storage node dat…

What the command say: echo $USER

[image] Alexey: echo $USER It returns the user admin

I am seeing the same issue on my storj node. Error messages are same as start of this thread. I am running it as a container as root on a Linux SBC (pine64). It was running without any issues previously. I suspect it might be related to a recent update (?). I have been running the container as …

Same issue on a Rock64. Container as root, stopped working after the update. Permissions are correct.

Same here, on qnap there you have no “root” :frowning:

Hi @bovcan Your hint guided me to search the “error” in the “docker-universe” as QNAP is not more the only intersection. [kit] Docker : How to avoid Operation not permitted in Docker Container? docker, permissions, suse asked by kit on 06:33AM - 16 Dec…

Adding the --privileged flag to the docker run command appears to have resolved my issue. Thanks!

[image] pbelk: –privileged I will be concerned if we need to run the container with privileges after updating to the latest version. I can’t think of one good reason the storagenode would need access to the host.

Storj Community Forum (official)

Error starting master database on storagenode: storage node database error: unable to open database file: operation not permitted

Node Operators troubleshooting