Storagenode Status restarting

Node Operators troubleshooting
, ,
1

The image remains in status “restarting”

docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7c2781a7baff storjlabs/storagenode:latest “/entrypoint” 7 seconds ago Restarting (1) 1 second ago storagenode

docker logs storagenode

Error: write /app/config/config.yaml493469550: operation not permitted
Error: write /app/config/config.yaml883356979: operation not permitted
Error: write /app/config/config.yaml913730747: operation not permitted
Error: write /app/config/config.yaml904132711: operation not permitted
Error: write /app/config/config.yaml435291078: operation not permitted
Error: write /app/config/config.yaml959565671: operation not permitted
Error: write /app/config/config.yaml330805613: operation not permitted
Error: write /app/config/config.yaml580394221: operation not permitted
Error: write /app/config/config.yaml970663828: operation not permitted

Launched by user quetdn, who is the owner of identity files and can write in storage directory. Same result if launched with sudo.

*docker run -d --restart unless-stopped --stop-timeout 300 \*
  • -p 28967:28967 *
  • -p 127.0.0.1:14002:14002 *
  • -e WALLET=“0xXXXXXXXXXXXXXXXXXXXX” *
  • -e EMAIL="xxxxxxxx@gmail.com" *
  • -e ADDRESS=“xx.xx.xx:28967” *
  • -e STORAGE=“600GB” *
  • –mount type=bind,source="/home/quetdn/.local/share/storj/identity/storagenode",destination=/app/identity *
  • –mount type=bind,source="/mnt/storjuser02",destination=/app/config *
  • –name storagenode storjlabs/storagenode:latest*

ls -l /mnt
total 0
drwxrwxrwx 2 root root 0 Jun 29 23:32 storjuser02

ls -l /mnt/storjuser02/
total 0
-rw-rw-r-- 1 quetdn quetdn 0 Jun 29 23:41 pp

df -k .

Filesystem 1K-blocks Used Available Use% Mounted on
192.168.0.150,192.168.0.151,192.168.0.152,192.168.0.153:/other/StorJData/ 1852850176 979525632 873324544 53% /mnt/storjuser02

It is a Cephfs

Any ideas?

2

The network connected drives are not supported.
The only working network protocol is iSCSI

By the way, can you write something to the mounted disk?

ll /mnt/storjuser02
echo "Test" > /mnt/storjuser02/testfile
ll /mnt/storjuser02
cat /mnt/storjuser02/testfile
rm /mnt/storjuser02/testfile
3

I think you need root access to the share because when I tried this it created root owned files in my home

4

Alexey and andrew2.hart, you were right, it was a problem with the write rights. I could create files (with touch)and I assumed that I could write into the files, but it was no possible. It was a problem with my ceph configuration.
I changed the auth type of the user that maps the disk:
ceph auth caps client.storjuser02 mon ‘allow r’ mds ‘allow rw’ osd 'allow rwx pool=cephfs_metadata,allow rwx pool=cephfs_data’

It worked. The node is up, running and Online.

Thanks for your help.

5

Are you running erasure coding or 3 copies on your storj pool? I had assumed ceph would be too slow to write with any redundancy

6

Any network connected drive will have a higher latency than a local connected.

7

Replication mode
replicated size 3 min_size 2

8

Agree Alexey, but it is my current set up, and it is very reliable with replication and HA of storage and the VM in HA. I will try if I can gain confidence in the storj network.