Erreur node storj freebox delta

Node Operators troubleshooting
, , ,
1

Bonjour.
J’ai créé mon premier node avec freebox delta et VM ubuntu 22.04 jammy.
Mon noeud redémarre en permanence… J’ai regardé le forum, essayé de réinstaller mais rien ne fonctionne… les logs ci-dessous:
2023-01-23 12:02:15,872 INFO Set uid to user 0 succeeded
2023-01-23 12:02:15,890 INFO RPC interface ‘supervisor’ initialized
2023-01-23 12:02:15,891 INFO supervisord started with pid 1
2023-01-23 12:02:16,895 INFO spawned: ‘processes-exit-eventlistener’ with pid 45
2023-01-23 12:02:16,899 INFO spawned: ‘storagenode’ with pid 46
2023-01-23 12:02:16,903 INFO spawned: ‘storagenode-updater’ with pid 47
2023-01-23T12:02:16.937Z INFO Configuration loaded {“Process”: “storagenode-updater”, “Location”: “/app/config/config.yaml”}
2023-01-23T12:02:16.938Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.enabled”}
2023-01-23T12:02:16.939Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-disk-space”}
2023-01-23T12:02:16.939Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”}
2023-01-23T12:02:16.939Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet-features”}
2023-01-23T12:02:16.940Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”}
2023-01-23T12:02:16.940Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-bandwidth”}
2023-01-23T12:02:16.941Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”}
2023-01-23T12:02:16.941Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.details”}
2023-01-23T12:02:16.941Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.private-address”}
2023-01-23T12:02:16.942Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “console.address”}
2023-01-23T12:02:16.942Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.email”}
2023-01-23T12:02:16.943Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.level”}
2023-01-23T12:02:16.945Z INFO Anonymized tracing enabled {“Process”: “storagenode-updater”}
2023-01-23T12:02:16.950Z INFO Running on version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.70.2”}
2023-01-23T12:02:16.951Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}
2023-01-23T12:02:17.012Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-01-23T12:02:17.014Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2023-01-23T12:02:17.018Z INFO Operator email {“Process”: “storagenode”, “Address”: “yohan.bernardgranger@gmail.com”}
2023-01-23T12:02:17.019Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “0xF29032d5E331EcB9a3ca9Dcf78604802FC492BDf”}
2023-01-23T12:02:17.022Z INFO db database does not exist {“Process”: “storagenode”, “database”: “info”}
2023-01-23T12:02:17.022Z INFO db database does not exist {“Process”: “storagenode”, “database”: “bandwidth”}
2023-01-23T12:02:17.023Z INFO db database does not exist {“Process”: “storagenode”, “database”: “orders”}
2023-01-23T12:02:17.024Z INFO db database does not exist {“Process”: “storagenode”, “database”: “piece_expiration”}
2023-01-23T12:02:17.024Z INFO db database does not exist {“Process”: “storagenode”, “database”: “pieceinfo”}
2023-01-23T12:02:17.025Z INFO db database does not exist {“Process”: “storagenode”, “database”: “piece_spaced_used”}
2023-01-23T12:02:17.026Z INFO db database does not exist {“Process”: “storagenode”, “database”: “reputation”}
2023-01-23T12:02:17.026Z INFO db database does not exist {“Process”: “storagenode”, “database”: “storage_usage”}
2023-01-23T12:02:17.027Z INFO db database does not exist {“Process”: “storagenode”, “database”: “used_serial”}
2023-01-23T12:02:17.028Z INFO db database does not exist {“Process”: “storagenode”, “database”: “satellites”}
2023-01-23T12:02:17.028Z INFO db database does not exist {“Process”: “storagenode”, “database”: “notifications”}
2023-01-23T12:02:17.029Z INFO db database does not exist {“Process”: “storagenode”, “database”: “heldamount”}
2023-01-23T12:02:17.030Z INFO db database does not exist {“Process”: “storagenode”, “database”: “pricing”}
2023-01-23T12:02:17.031Z INFO db database does not exist {“Process”: “storagenode”, “database”: “secret”}
2023-01-23T12:02:17.377Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode”, “Version”: “v1.70.2”}
2023-01-23T12:02:17.377Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode”}
2023-01-23T12:02:17.396Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.70.2”}
2023-01-23T12:02:17.396Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
2023-01-23T12:02:18.030Z INFO Telemetry enabled {“Process”: “storagenode”, “instance ID”: “1peXS823YvH1siL4X3xH73kJ5sTYCc7mRWM2BmLJbKYzrJWAin”}
2023-01-23 12:02:18,031 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-23 12:02:18,031 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-23 12:02:18,031 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-23T12:02:18.032Z INFO Event collection enabled {“Process”: “storagenode”, “instance ID”: “1peXS823YvH1siL4X3xH73kJ5sTYCc7mRWM2BmLJbKYzrJWAin”}
Error: Error creating tables for master database on storagenode: migrate: database: info opening file “config/storage/info.db” failed: database is locked

Pouvez-vous m’aider?

merci Yohan

2

docker run --rm -e SETUP=“true”
–user $(id -u):$(id -g)
–mount type=bind,source=“/mnt/Disque-4/storagenode/identity/storagenode/”,destination=/app/identity
–mount type=bind,source=“/mnt/Disque-4/storagenode/storjdata”,destination=/app/config
–name storagenode storjlabs/storagenode:latest

docker run -d --restart unless-stopped --stop-timeout 300
-p 28967:28967/tcp
-p 28967:28967/udp
-p 14002:14002
-e WALLET=“0xxxxxxxxxxxxxxxxxxxxx”
-e EMAIL="xxxxx@gmail.com"
-e ADDRESS=“xxxxxxxxxxx:28967”
-e STORAGE=“2TB”
–user $(id -u):$(id -g)
–mount type=bind,source=“/mnt/Disque-4/storagenode/identity/storagenode/”,destination=/app/identity
–mount type=bind,source=“/mnt/Disque-4/storagenode/storjdata”,destination=/app/config
–name storagenode storjlabs/storagenode:latest

3

Est-il possible qu’un autre noeud soit déjà en cours d’execution?

Si ce n’est pas le cas, executez-vous peut-être le noeud sur iSCSI ou NFS?

4

Bonjour @bernard-granger,
Bienvenue sur le forum !

Comment avez-vous connecté le disque à cette VM ? SMB/NFS ne fonctionnera pas, vous devrez soit créer un disque virtuel et l’attacher à la machine virtuelle, soit utiliser iSCSI si vous êtes obligé d’utiliser une connexion réseau au stockage.

6

Hello
My hard drive is mounted when starting the VM with this command:

packages:

cifs-utils montages
:
[ ’ //mafreebox.freebox.fr/Disque\0404 ', ‘/mnt/Disque-4’, cifs, ‘guest,uid=1000,gid=1000’, ‘0’, ‘0’ ]
[ ’ //mafreebox.freebox.fr/Disque\0405 ', ‘/mnt/Disque-5’, cifs, ‘guest,uid=1000,gid=1000’, ‘0’, ‘0’ ]
[ ’ //myfreebox.freebox.fr/Freebox ', ‘/mnt/Freebox’, cifs, ‘guest,uid=1000,gid=1000’, ‘0’, ‘0’ ]
[ ‘//myfreebox.freebox.fr/INTERNRAID1’, ‘/mnt/INTERNRAID1’, cifs, ‘guest,uid=1000,gid=1000’, ‘0’, ‘0’ ]
Is this the problem?

Yohan

7

Hello
My hard drive is mounted when starting the VM with this command:

packages:

cifs-utils montages
:
[ ’ //mafreebox.freebox.fr/Disque\0404 ', ‘/mnt/Disque-4’, cifs, ‘guest,uid=1000,gid=1000’, ‘0’, ‘0’ ]

Is this the problem?

Yohan

8

Unfortunately, neither network filesystems are supported, include CIFS (SMB, Samba), NFS, SSHFS, etc. The only working network storage protocol is iSCSI.

1 Like
9

Hello
It’s ok my node is ok.
Thanks

1 Like