Storj - Speicher vermieten

MAteo

Benutzer
Mitglied seit
23. Dez 2018
Beiträge
93
Punkte für Reaktionen
2
Punkte
8
danke für die antwort @luddi , ich habe das jetzt einmal angepasst, die pfade sollten jetzt ja richtig sein.
anscheinend hat er probleme mit der config. kannst du da helfen?

Code:
sudo docker run -d --restart unless-stopped --stop-timeout 300 \
-p 28967:28967/tcp \
-p 28967:28967/udp \
-p 14002:14002 \
-e WALLET="xxxxx" \
-e EMAIL="xxxxx@gmx.de" \
-e ADDRESS="sxxxxxxx:28967" \
-e STORAGE="10.2TB" \
--mount type=bind,source="/volume1/docker/storj/node1/identitiy/storagenode_01",destination=/app/identity \
--mount type=bind,source="/volume2/Storj/storagenode_01",destination=/app/config \
--name storagenode_01 storjlabs/storagenode:latest

Code:
root@DS918:~# docker logs b2cfd878aed7
2024-10-06 06:14:27,621 INFO Set uid to user 0 succeeded
2024-10-06 06:14:27,631 INFO RPC interface 'supervisor' initialized
2024-10-06 06:14:27,631 INFO supervisord started with pid 1
2024-10-06 06:14:28,634 INFO spawned: 'processes-exit-eventlistener' with pid 9
2024-10-06 06:14:28,635 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:28,636 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:29,645 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-06 06:14:29,646 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:29,647 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:31,650 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:31,651 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:34,655 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:34,655 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2024-10-06 06:14:34,656 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:34,656 INFO gave up: storagenode-updater entered FATAL state, too many start retries too quickly
2024-10-06 06:14:36,659 WARN received SIGQUIT indicating exit request
2024-10-06 06:14:36,659 INFO waiting for processes-exit-eventlistener to die
2024-10-06 06:14:38,662 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2024-10-06 06:14:45,067 INFO Set uid to user 0 succeeded
2024-10-06 06:14:45,075 INFO RPC interface 'supervisor' initialized
2024-10-06 06:14:45,076 INFO supervisord started with pid 1
2024-10-06 06:14:46,079 INFO spawned: 'processes-exit-eventlistener' with pid 9
2024-10-06 06:14:46,080 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:46,081 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:47,090 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-06 06:14:47,091 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:47,092 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:49,094 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:49,094 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:52,099 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:52,099 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2024-10-06 06:14:52,100 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:52,100 INFO gave up: storagenode-updater entered FATAL state, too many start retries too quickly
2024-10-06 06:14:54,103 WARN received SIGQUIT indicating exit request
2024-10-06 06:14:54,103 INFO waiting for processes-exit-eventlistener to die
2024-10-06 06:14:56,106 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2024-10-06 06:15:02,645 INFO Set uid to user 0 succeeded
2024-10-06 06:15:02,653 INFO RPC interface 'supervisor' initialized
2024-10-06 06:15:02,654 INFO supervisord started with pid 1
2024-10-06 06:15:03,658 INFO spawned: 'processes-exit-eventlistener' with pid 10
2024-10-06 06:15:03,659 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:03,660 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:04,669 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-06 06:15:04,670 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:04,670 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:06,673 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:06,673 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:09,678 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:09,678 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2024-10-06 06:15:09,678 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:09,679 INFO gave up: storagenode-updater entered FATAL state, too many start retries too quickly
2024-10-06 06:15:11,681 WARN received SIGQUIT indicating exit request
2024-10-06 06:15:11,682 INFO waiting for processes-exit-eventlistener to die
2024-10-06 06:15:13,685 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2024-10-06 06:15:20,323 INFO Set uid to user 0 succeeded
2024-10-06 06:15:20,332 INFO RPC interface 'supervisor' initialized
2024-10-06 06:15:20,332 INFO supervisord started with pid 1
root@DS918:~# docker logs b2cfd878aed7
2024-10-06 06:14:27,621 INFO Set uid to user 0 succeeded
2024-10-06 06:14:27,631 INFO RPC interface 'supervisor' initialized
2024-10-06 06:14:27,631 INFO supervisord started with pid 1
2024-10-06 06:14:28,634 INFO spawned: 'processes-exit-eventlistener' with pid 9
2024-10-06 06:14:28,635 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:28,636 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:29,645 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-06 06:14:29,646 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:29,647 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:31,650 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:31,651 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:34,655 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:34,655 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2024-10-06 06:14:34,656 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:34,656 INFO gave up: storagenode-updater entered FATAL state, too many start retries too quickly
2024-10-06 06:14:36,659 WARN received SIGQUIT indicating exit request
2024-10-06 06:14:36,659 INFO waiting for processes-exit-eventlistener to die
2024-10-06 06:14:38,662 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2024-10-06 06:14:45,067 INFO Set uid to user 0 succeeded
2024-10-06 06:14:45,075 INFO RPC interface 'supervisor' initialized
2024-10-06 06:14:45,076 INFO supervisord started with pid 1
2024-10-06 06:14:46,079 INFO spawned: 'processes-exit-eventlistener' with pid 9
2024-10-06 06:14:46,080 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:46,081 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:47,090 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-06 06:14:47,091 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:47,092 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:49,094 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:49,094 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:52,099 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:14:52,099 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2024-10-06 06:14:52,100 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:14:52,100 INFO gave up: storagenode-updater entered FATAL state, too many start retries too quickly
2024-10-06 06:14:54,103 WARN received SIGQUIT indicating exit request
2024-10-06 06:14:54,103 INFO waiting for processes-exit-eventlistener to die
2024-10-06 06:14:56,106 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2024-10-06 06:15:02,645 INFO Set uid to user 0 succeeded
2024-10-06 06:15:02,653 INFO RPC interface 'supervisor' initialized
2024-10-06 06:15:02,654 INFO supervisord started with pid 1
2024-10-06 06:15:03,658 INFO spawned: 'processes-exit-eventlistener' with pid 10
2024-10-06 06:15:03,659 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:03,660 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:04,669 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-06 06:15:04,670 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:04,670 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:06,673 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:06,673 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:09,678 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:09,678 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2024-10-06 06:15:09,678 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:09,679 INFO gave up: storagenode-updater entered FATAL state, too many start retries too quickly
2024-10-06 06:15:11,681 WARN received SIGQUIT indicating exit request
2024-10-06 06:15:11,682 INFO waiting for processes-exit-eventlistener to die
2024-10-06 06:15:13,685 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2024-10-06 06:15:20,323 INFO Set uid to user 0 succeeded
2024-10-06 06:15:20,332 INFO RPC interface 'supervisor' initialized
2024-10-06 06:15:20,332 INFO supervisord started with pid 1
2024-10-06 06:15:21,336 INFO spawned: 'processes-exit-eventlistener' with pid 10
2024-10-06 06:15:21,337 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:21,338 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:22,346 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-06 06:15:22,347 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:22,347 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:24,350 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:24,350 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:27,355 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:27,355 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2024-10-06 06:15:27,356 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:27,356 INFO gave up: storagenode-updater entered FATAL state, too many start retries too quickly
2024-10-06 06:15:29,359 WARN received SIGQUIT indicating exit request
2024-10-06 06:15:29,359 INFO waiting for processes-exit-eventlistener to die
2024-10-06 06:15:31,362 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2024-10-06 06:15:37,784 INFO Set uid to user 0 succeeded
2024-10-06 06:15:37,792 INFO RPC interface 'supervisor' initialized
2024-10-06 06:15:37,793 INFO supervisord started with pid 1
2024-10-06 06:15:38,796 INFO spawned: 'processes-exit-eventlistener' with pid 9
2024-10-06 06:15:38,798 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:38,798 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:39,808 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-10-06 06:15:39,809 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:39,809 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
2024-10-06 06:15:41,812 INFO spawnerr: command at '/app/config/bin/storagenode' is not executable
2024-10-06 06:15:41,812 INFO spawnerr: command at '/app/config/bin/storagenode-updater' is not executable
 
Zuletzt bearbeitet:

MAteo

Benutzer
Mitglied seit
23. Dez 2018
Beiträge
93
Punkte für Reaktionen
2
Punkte
8
hab es hinbekommen, anscheinend gab es eine änderung, welche genau und ob bei synology oder storj kann ich nicht sagen, aber der hauptproblem war, das der updater nicht mehr angelaufen werden konnte.....
lösung auch in den synology forum gefunden:

sudo chmod +x /volume2/Storj/storagenode_01/bin

berechtigung auf den bin ordner muss gegeben werden...

evtl. mal pinnen :)

LG
Mateo
 
  • Like
Reaktionen: DKeppi

ikorbln

Benutzer
Mitglied seit
26. Nov 2017
Beiträge
346
Punkte für Reaktionen
34
Punkte
28
Hallo Leute,

heute wurde mein "gracefull exit" abgeschlossen, nun liegen hier 330 Tokens rum (bei myetherwallet).
Vor ein paar Jahren hatte ich schonmal, mit viel Aufwand, Tokens in EUR umgewandelt.
Aber diese Wege funktionieren heute nicht mehr.

Kann mir jemand sagen, wie ich die Tokens möglichst günstig als EUR auf mein Konto bekomme?

Liebe Dank ;-)
 

DKeppi

Benutzer
Mitglied seit
01. Apr 2011
Beiträge
3.222
Punkte für Reaktionen
76
Punkte
114
Warum bist du ausgestiegen?
Ich verdiene aktuell immer noch um die 4$ pro Monat mit 3TB

Ich würds sie vermutlich an Coinbase senden, dort verkaufen und dann kostenlos via Paypal auszahlen
Bei Paypal kann man dann ja aufs Konto transferieren, entweder gegen Gebühr in wenigen Sekunden oder kostenlos in 2-3 Tagen
 
Zuletzt bearbeitet:

ikorbln

Benutzer
Mitglied seit
26. Nov 2017
Beiträge
346
Punkte für Reaktionen
34
Punkte
28
Ich bin immer mal wieder rein und raus aus dem Projekt, aktuell bin ich mal wieder in der "Infrastruktur reduzieren" phase ;-)
Coinbase hat mich erstmal auf die Warteliste gesetzt, da muss ich auf die Verifizierung warten. Bei Kraken ging das innerhalb von 30min. Bei Anycoin scheitert im Moment die Reaktivierung meines alten Account. Aber auch da muss dann verifiziert werden. Und dann mal schauen wer nen guten Preis hat....
 
  • Like
Reaktionen: DKeppi

DKeppi

Benutzer
Mitglied seit
01. Apr 2011
Beiträge
3.222
Punkte für Reaktionen
76
Punkte
114
Wie lange hat dein "gracefull exit" gedauert, und vor allem für wieviel freigegebenen Speicher?
 

maalik

Benutzer
Mitglied seit
05. Feb 2016
Beiträge
708
Punkte für Reaktionen
11
Punkte
38
Meiner hat 30 Tage gedauert und war danach "abgeschlossen" laut Node, aber freigegeben hat er nix. Musste dann 2 Tage lang Hunderttausende Dateien löschen.
 

ikorbln

Benutzer
Mitglied seit
26. Nov 2017
Beiträge
346
Punkte für Reaktionen
34
Punkte
28
Ich hatte 1,5TB geteilt. Nach dem Absenden des Befehls hat es ca. 30 Tage gedauert, musste den Befehl aber für einen Satelliten wiederholen, dann ging es nach 5 Tagen los mit dem automatischen löschen. Das Löschen hatte dann auch nochmal gut 1 1/2 Tage gedauert.
 
  • Like
Reaktionen: DKeppi


 

Kaffeautomat

Wenn du das Forum hilfreich findest oder uns unterstützen möchtest, dann gib uns doch einfach einen Kaffee aus.

Als Dankeschön schalten wir deinen Account werbefrei.

:coffee:

Hier gehts zum Kaffeeautomat