Probleme connexion node satellite

pascal · September 21, 2022, 6:19am

J’utilise notepad++ et j’ai mis la premiere ligne comme exemple. Mais sinon je mets tout normalement.

Alexey · September 21, 2022, 6:22am

Tu as tout à fait raison. Vérifiez votre commande dans Notepad++, il doit y avoir une barre oblique inverse \ après chaque ligne sauf la dernière, ou écrivez toute la commande sur une seule ligne.

Si toutes les lignes étaient là, assurez-vous que vous n’avez pas de doubles tirets transformés en tirets, de guillemets droits " transformés en fantaisie, etc. (de telles conversions se produisent généralement lors de l’utilisation de Word, WordPad, etc.).

pascal · September 21, 2022, 6:35am

Merci ca a marché !!!

Mais la le contenaire n’arrete pas de redemarrer.

pascal · September 21, 2022, 6:41pm

Ca ne semble toujours pas marché
C’est compliqué… Quel est le probleme maintenant ?

Merci a toi Alexey

Pac · September 21, 2022, 8:38pm

Ne serait-il pas possible de nous copier/coller les logs pertinents sous format textuel sur ce forum plutôt que des copies d’écran pour nous permettre d’avoir davantage de lignes et nous faciliter leur recherche ?

En utilisant la procédure décrite par @Alexey pour qu’ils soient bien formatés :

    ```
    Vos lignes des logs ici
    ```

Cela nous aiderait à voir les erreurs en entier notamment.

Alexey · September 21, 2022, 9:12pm

Veuillez copier les lignes du journal sous forme de texte, il est difficile de comprendre quelque chose à partir des captures d’écran de morceaux arbitraires du journal, désolé.

pascal · September 21, 2022, 9:46pm

Oui désolé. Ce sont les 20 dernieres lignes de log.

2022-09-21T21:44:48.017Z        INFO    Configuration loaded    {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2022-09-21T21:44:48.018Z        INFO    Anonymized tracing enabled      {"Process": "storagenode"}
2022-09-21T21:44:48.040Z        INFO    Operator email  {"Process": "storagenode", "Address": "xxxxxxxxx@gmail.com"}
2022-09-21T21:44:48.040Z        INFO    Operator wallet {"Process": "storagenode", "Address": "0xXXXXXXXXXXXXXXXXXXXXXXX"}
Error: Error starting master database on storagenode: database: info opening file "config/storage/info.db" failed: attempt to write a readonly database
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:324
        storj.io/storj/storagenode/storagenodedb.(*DB).openExistingDatabase:306
        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabases:281
        storj.io/storj/storagenode/storagenodedb.OpenExisting:248
        main.cmdRun:193
        storj.io/private/process.cleanup.func1.4:378
        storj.io/private/process.cleanup.func1:396
        github.com/spf13/cobra.(*Command).execute:852
        github.com/spf13/cobra.(*Command).ExecuteC:960
        github.com/spf13/cobra.(*Command).Execute:897
        storj.io/private/process.ExecWithCustomConfigAndLogger:93
        main.main:478
        runtime.main:255
2022-09-21 21:44:48,061 INFO exited: storagenode (exit status 1; not expected)
2022-09-21 21:44:49,062 INFO gave up: storagenode entered FATAL state, too many start retries too quickly

pascal · September 21, 2022, 9:49pm

Ici un autre

        storj.io/storj/storagenode/storagenodedb.(*DB).openDatabases:281
        storj.io/storj/storagenode/storagenodedb.OpenExisting:248
        main.cmdRun:193
        storj.io/private/process.cleanup.func1.4:378
        storj.io/private/process.cleanup.func1:396
        github.com/spf13/cobra.(*Command).execute:852
        github.com/spf13/cobra.(*Command).ExecuteC:960
        github.com/spf13/cobra.(*Command).Execute:897
        storj.io/private/process.ExecWithCustomConfigAndLogger:93
        main.main:478
        runtime.main:255
2022-09-21 21:48:19,902 INFO exited: storagenode (exit status 1; not expected)
2022-09-21 21:48:20,904 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2022-09-21 21:48:22,148 WARN received SIGQUIT indicating exit request
2022-09-21 21:48:22,148 INFO waiting for processes-exit-eventlistener, storagenode-updater to die
2022-09-21T21:48:22.149Z        INFO    Got a signal from the OS: "terminated"  {"Process": "storagenode-updater"}
2022-09-21 21:48:22,150 INFO stopped: storagenode-updater (exit status 0)
2022-09-21 21:48:23,152 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
2022-09-21 21:48:32,070 INFO RPC interface 'supervisor' initialized
2022-09-21 21:48:32,071 INFO supervisord started with pid 1

pascal · September 22, 2022, 4:07am

Peut etre je devrais supprimer le node et recommencer du debut ?
Car la je ne comprends pas le probleme

Alexey · September 22, 2022, 8:22am

Cette erreur indique des problèmes d’accès au dossier de données.
Si j’ai bien deviné, vous utilisez Synology.
Dans ce cas, vous êtes obligé de toujours utiliser sudo pour exécuter les commandes docker, de sorte que seul l’utilisateur root est susceptible d’avoir l’autorisation d’accéder aux données. Ensuite, essayez d’arrêter et de supprimer le conteneur et de recommencer avec toutes vos options, mais sans l’option --user $(id -u):$(id -g).

pour arrêter et supprimer le conteneur, exécutez les commandes suivantes:

docker stop -t 300 storagenode
docker rm storagenode

Ensuite, relancez le conteneur avec toutes vos options, mais sans l’option --user $(id -u):$(id -g) \.
Après cela, vérifiez à nouveau les journaux.

pascal · September 23, 2022, 4:00am

Wow j’ai l’impression que ca marche !

2022-09-23T03:58:44.811Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "YQVCXVY7NWTBJG4BPD4PKESQSROWPHZBTJXCSEAUAIMRXBIZIVCA", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Action": "PUT", "Size": 2319360}
2022-09-23T03:58:45.349Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "V5Y2SBNVQP24YHCGGO6DGPRW6467FRZRC4DXLV3SCNMAD7LLK3OQ", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Available Space": 3999994924288}
2022-09-23T03:58:45.627Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "V5Y2SBNVQP24YHCGGO6DGPRW6467FRZRC4DXLV3SCNMAD7LLK3OQ", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Size": 23040}
2022-09-23T03:58:46.297Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "DTKXDC26ZMO5FHARCD6WRKOQUTURGM47DX3OSPPHDSCEL3WD2H3A", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Available Space": 3999994900736}
2022-09-23T03:58:46.561Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "DTKXDC26ZMO5FHARCD6WRKOQUTURGM47DX3OSPPHDSCEL3WD2H3A", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Size": 20736}
2022-09-23T03:58:46.853Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "KAA75X3RSJ22UOC2BWTOHP6UBL4SFXYQTSFZYGJYN2KOVW3KGPCQ", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Available Space": 3999994879488}
2022-09-23T03:58:47.219Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "KAA75X3RSJ22UOC2BWTOHP6UBL4SFXYQTSFZYGJYN2KOVW3KGPCQ", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Size": 181504}
2022-09-23T03:58:49.135Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "4GA474BZHFLY2CFSOMU56ZVD4AZGI7MMD52XKCMR2R3EHZMJ7APA", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "PUT", "Available Space": 3999994697472}
2022-09-23T03:58:50.181Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "JUTSWTDBOKOG7QHMOX7NQM5KCM7ZH5XFVO5SJHZDROCOFUKDG4SA", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "PUT", "Available Space": 3999994697472}
2022-09-23T03:58:51.924Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "R7QIAMKG5VZVNZDABHA7IGS4RB3Z2NTCE2SFQERP4VTL7CBRCR2Q", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Available Space": 3999994697472}
2022-09-23T03:58:52.032Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "R7QIAMKG5VZVNZDABHA7IGS4RB3Z2NTCE2SFQERP4VTL7CBRCR2Q", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Size": 21248}
2022-09-23T03:58:53.240Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "JUTSWTDBOKOG7QHMOX7NQM5KCM7ZH5XFVO5SJHZDROCOFUKDG4SA", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "Action": "PUT", "Size": 2174464}
2022-09-23T03:58:53.261Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "NL7FBBOPXMGKELSIPJFGNQVL5JS7FMGQJAGU6YWBXYFD5G44RKUA", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Action": "PUT", "Available Space": 3999992500736}
2022-09-23T03:58:53.315Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "NL7FBBOPXMGKELSIPJFGNQVL5JS7FMGQJAGU6YWBXYFD5G44RKUA", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Action": "PUT", "Size": 4608}
2022-09-23T03:58:54.875Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "AJDU7LK6K2G3C3YPTEQIA7LHV4K6TMNR34JAOP2ODZ255PBYOQLA", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Action": "PUT", "Available Space": 3999992495616}
2022-09-23T03:58:55.023Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "AJDU7LK6K2G3C3YPTEQIA7LHV4K6TMNR34JAOP2ODZ255PBYOQLA", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Action": "PUT", "Size": 4864}
2022-09-23T03:58:55.451Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "PKXLQ7ZHNUSQAUIVUINDZHOLR72RXKK3B74EXLVUPTLZECYQIAMQ", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Available Space": 3999992490240}
2022-09-23T03:58:55.557Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "PKXLQ7ZHNUSQAUIVUINDZHOLR72RXKK3B74EXLVUPTLZECYQIAMQ", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Action": "PUT", "Size": 24576}
2022-09-23T03:59:00.242Z        INFO    piecestore      upload started  {"Process": "storagenode", "Piece ID": "QOGKMTXTXFYTOK4LADCG6FE77F2VU6LIYAEQAQZAQUUWMVKQSDTA", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Action": "PUT", "Available Space": 3999992465152}
2022-09-23T03:59:00.457Z        INFO    piecestore      uploaded        {"Process": "storagenode", "Piece ID": "QOGKMTXTXFYTOK4LADCG6FE77F2VU6LIYAEQAQZAQUUWMVKQSDTA", "Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "Action": "PUT", "Size": 4352}

pascal · September 23, 2022, 4:07am

Ca a marché Alexey, tu es un génie !
Par contre j’ai eu un autre message d’erreur dans le log.

INFO failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB)

Comment je résous ca ?

Merci

Alexey · September 23, 2022, 6:32am

Tu es la Bienvenue!
Pour éviter cet avertissement, vous devez configurer un paramètre système, voir Linux Configuration for UDP | Storj Docs
Voir également Linux, "failed to sufficiently increase receive buffer size"

Pac · September 23, 2022, 9:26pm

@pascal : @Alexey c’est un peu notre ange gardien technique Storj, aucun problème ne lui résiste
Même quand ce n’est pas dans sa langue ! Bravo à lui !

Gardez un œil sur votre Node et son dashboard sur les prochains jours pour s’assurer que les métriques et les scores évoluent dans le bon sens.
Si tout semble en ordre, c’est que c’est en bonne voie !

Cela étant dit, c’est une bonne idée de configurer un outil externe de vérification que le Node continue de répondre sur le long terme, de façon à être prévenu par e-mail si se retrouve déconnecté du réseau Internet. Le service “uptimerobot” est utilisé par beaucoup d’entre-nous ici pour vérifier que le port technique de nos nodes répondent, mais il en existe d’autres.

N’hésitez pas à parcourir ce forum, c’est une mine d’informations

PS : Enfin, si la l’anglais ne vous fait pas peur, sachez que beaucoup plus de membres de la communauté seront à même de vous aider et de vous conseillez s’il vous est possible de rédiger vos prochains posts en anglais. Juste pour info ^^

pascal · September 24, 2022, 2:19am

Bizarre car la commande ci dessous fonctionne :
sysctl -w net.core.rmem_max=2500000

mais pas celle ci :
echo “net.core.rmem_max=2500000” >> /etc/sysctl.conf
sysctl -w net.core.rmem_max=2500000

Ca repond :
-sh: /etc/sysctl.conf: Permission denied

LOL quel est le probleme maintenant ?

pascal · September 24, 2022, 5:20am

I can’t access to my dashboard via internet. I opened the port 14002 on my router (with local ip, not the one of my nas)…
I tried those address :
→ ipnas:14002/
->127.0.0.1:14002/
→ ipddns:14002/

I just tried Open Port Check Tool - Test Port Forwarding on Your Router and it says port 14002 is closed. Which is strange since it’s supposed to be open. What did i do wonrg ?

Nothing works. Any idea ?

Alexey · September 24, 2022, 7:54am

Cette commande doit être exécutée en tant que root, essayez ceci:

sudo echo "net.core.rmem_max=2500000" >> /etc/sysctl.conf

Alexey · September 24, 2022, 8:00am

Please do not expose the port 14002 on your router, you exposing your personal information to the whole internet, use this guide instead: How to remote access the web dashboard | Storj Docs or use the [Tech Preview] Multinode Dashboard Binaries on your other device to have an access to your node statistics over Internet.

If you would like to have an insecure access from your other device in the same local network, you may remove 127.0.0.1: from the port mapping, however I highly recommend to do not expose this port to the Internet anyway.

pascal · September 24, 2022, 4:34pm

That’s what I did and it still denied

pascal · September 24, 2022, 5:24pm

I removed the port 14002 from the router. And my docker I used the command -p 14002:14002. It worked. I have access to the dashboard now.

But I noticed when I reboot the docker, even if it worked, I got some strange messages from the log.

	INFO Invalid configuration file value for key {"Process": "storagenode-updater", "Key": "log.encoding"}
2022-09-24T16:49:20.829978172Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "console.address"}
2022-09-24T16:49:20.829866946Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2022-09-24T16:49:20.829834414Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.address"}
2022-09-24T16:49:20.829796983Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2022-09-24T16:49:20.829763346Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.enabled"}
2022-09-24T16:49:20.829729140Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet"}
2022-09-24T16:49:20.829693805Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.private-address"}
2022-09-24T16:49:20.829657710Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.email"}
2022-09-24T16:49:20.829612348Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "contact.external-address"}
2022-09-24T16:49:20.829574531Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.details"}
2022-09-24T16:49:20.829517426Z	stdout	2022-09-24T16:49:20.828Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-bandwidth"}
2022-09-24T16:49:20.829278808Z	stdout	2022-09-24T16:49:20.828Z INFO Configuration loaded {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}

What does it mean, should I worry ?