[1]
Comme il me reste maintenant un Rpi3 et qu’on m’a dit de créer un nœud et de traîner autour du réseau ğ1(-test) d’abord pour me faire une idée, avant de lancer ma propre devise, j’ai essayé de le configurer à nouveau sur mon Rpi3.
Actuellement, je suis 502 Bad Gateway erreur lors de l’essai de se connecter à la page webui.
Un autre indice de ce qui se passe est que le démon duniter_default n’est pas en cours d’exécution.
admin@Yroklaus:~ $ ps -ef | grep duniter
duniter 929 1 0 Apr02 ? 00:00:00 /bin/bash /usr/bin/duniter webstart --home /var/lib/duniter/.config/duniter --mdb duniter_default
duniter 1047 929 47 Apr02 ? 00:00:09 /opt/duniter/node/bin/node /opt/duniter/bin/duniter webstart --home /var/lib/duniter/.config/duniter --mdb duniter_default
admin 1848 1831 0 00:00 pts/0 00:00:00 grep --color=auto duniter
admin@Yroklaus:~ $ sudo systemctl status duniter.service
● duniter.service - Duniter node
Loaded: loaded (/lib/systemd/system/duniter.service; enabled)
Active: activating (start) since Tue 2018-04-03 00:00:15 CEST; 5s ago
Control: 1885 (duniter)
CGroup: /system.slice/duniter.service
├─1885 /bin/bash /usr/bin/duniter webstart --home /var/lib/duniter/.config/duniter --mdb duniter_default
└─1887 /opt/duniter/node/bin/node /opt/duniter/bin/duniter webstart --home /var/lib/duniter/.config/duniter --mdb duniter_default
[mise-à-jour]
[2]
Je crois que j’ai trouvé le problème. Il me manquait des guillemets dans une des lignes de conf.json.
J’aimerais toujours avoir de l’aide pour mieux déterminer ce genre d’erreurs.
admin@Yroklaus:~ $ /bin/bash /usr/bin/duniter direct_start --home /var/lib/duniter/.config/duniter --mdb duniter_default
2018-04-03T00:10:02+02:00 - debug: Plugging file system...
2018-04-03T00:10:02+02:00 - debug: Loading conf...
2018-04-03T00:10:02+02:00 - error: SyntaxError: Unexpected token g in JSON at position 15
at JSON.parse (<anonymous>)
at CFSCore.readJSON (/opt/duniter/app/lib/dal/fileDALs/CFSCore.js:167:25)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
[3]
C’est parce que, actuellement, le programme s’exécute sous l’utilisateur admin, alors qu’il devrait être exécuté par l’utilisateur duniter d’une manière ou d’une autre?
admin@Gildurklaus:~ $ /bin/bash /usr/bin/duniter direct_start --home /var/lib/duniter/.config/duniter --mdb duniter_default
2018-04-03T00:10:44+02:00 - debug: Plugging file system...
2018-04-03T00:10:45+02:00 - debug: Loading conf...
2018-04-03T00:10:45+02:00 - error: Configuration could not be saved: Error: EACCES: permission denied, open '/var/lib/duniter/.config/duniter/duniter_default/keyring.yml'
2018-04-03T00:10:45+02:00 - error: Error: Error: EACCES: permission denied, open '/var/lib/duniter/.config/duniter/duniter_default/keyring.yml'
at Stack.processCommand (/opt/duniter/index.js:314:23)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
[4]
Parce que je ne peux pas tester complètement duniter de cette façon avec des permissions refusées.
Je ne sais maintenant que lancer duniter via un daemon systemd.
[1]
Since I’ve got an Rpi3 left now and I’ve been told to create a node and hang around the g1(-test) network first to get a feel for it, before starting my own currency, I’ve been trying to set it up on my Rpi3 again.
Currently I’m 502 Bad Gateway error when trying to connect to the webui page.
More clues to what’s going on is that the duniter_default demon is not running.
[2]
I think I’ve found the problem. I was missing quotes in one of the lines in conf.json.
I still would like help in order how to determine these kinds of errors better.
[3]
This is because currently this causes the program to run under user admin, while it should be run by user duniter somehow?
[4]
Because I can’t fully test duniter this way with permissions being denied.
I now only know how to run duniter via a systemd daemon.