Docker node - restarting - master database on storagenode: database: database is locked

Node Operators troubleshooting
21

Just check them again.
You need ca.cert, ca.key, identity.cert, identity.key
Two others - backup copies, they will appear after authorization

Example

    Directory: Y:\storagenode2\identity


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----        6/19/2019  10:04 PM            546 ca.1560971067.cert
-a----        6/19/2019  10:04 PM           1076 ca.cert
-a----        6/19/2019  10:01 PM            241 ca.key
-a----        6/19/2019  10:04 PM           1084 identity.1560971067.cert
-a----        6/19/2019  10:04 PM           1614 identity.cert
-a----        6/19/2019  10:01 PM            241 identity.key
22

Hi Alexey : sorry, I cannot post anymore as an new user of the forum
FYI; i’ve only following on my win computer I used to generate identity

C:\Users\Yoga>dir C:\Users\Yoga\AppData\Roaming\Storj\Identity\storagenode
Le volume dans le lecteur C n’a pas de nom.
Le numéro de série du volume est 9023-D596

Répertoire de C:\Users\Yoga\AppData\Roaming\Storj\Identity\storagenode

28/07/2021 11:45 .
28/07/2021 11:45 …
28/07/2021 11:45 558 ca.cert
28/07/2021 11:45 241 ca.key
28/07/2021 11:45 1 100 identity.cert
28/07/2021 11:45 241 identity.key
4 fichier(s) 2 140 octets
2 Rép(s) 414 305 046 528 octets libres

23

Yes, then you need to authorize it:

  1. Request a new authorization token: https://registration.storj.io/
  2. Authorize your brand new identity with that token: Identity - Node Operator
24

this new user thing is so stupid, it also got me when i joined…
i forget the details, but without a doubt the new user post could be doubled or something, so that people can actually manage to solve their problems.

25

This is because it’s not a chat. The forum trying to incentive new users to post everything in one post. By the way, @stygre did that and this is cool!
Just then I’m failed to type faster than @stygre respond :slight_smile:

26

Node is up…MANY thanks for your help.

To sum up :
1- DB issue
Newbie must have filesystem and mount type in concern
regarding what I learned…cifs may not work for the transactionnal DB
Mount an ext4 formated iSCSI LUN worked as an charm for me (take care of automount on server reboot)

2 - Cert issue
When creating the identity, ensure having 6 files generated and ensure folder hosting them is configured on docker container options

To conclude, I’ve highlty used this command :
To delete the container sudo docker stop storagenode / sudo docker rm storagenode
To get docker status : sudo docker ps -a
To check identity files : sudo docker exec -it storagenode ls -l /app/identity
Your best friend : get logs : sudo docker logs --tail 30 storagenode

@Alexey @SGC : you are the ones…thks again

1 Like