@tatinetteb sinon plus simple en passant par des points de montage du host commun:
Dans ton docker-compose.yml pour duniter:
volumes:
- /var/lib/duniter:/var/lib/duniter
Dans ton docker-compose.yml pour wotwizard:
volumes:
- /var/lib/duniter:/app/data
Peux importe le chemin indiqué à gauche /var/lib/duniter:, tu mets ce que tu veux, tant que c’est un chemin absolu (sans ~ au début du chemin), et que c’est le même pour les deux containers duntier et wotwizard.
A tester.
J’ai supprimé puis refait le noeud dans portainer.
Le noeud V1 a été réalisé sur mon serveur par Pini.
Portainer a mis le le noeud en running, le log ne bouge pas:
2024/03/21 16:50:50 blockchain.go:3117: Adding Centralities to updateList
2024/03/21 16:50:50 run.go:53: WotWizard Server version 5.11.3 Tools version 1.0.8
2024/03/21 16:50:50 blockchain.go:3117: Adding Blockchain to updateList
2024/03/21 16:50:50 blockchain.go:3244: Starting
2024/03/21 16:50:50 blockchain.go:3245:
2024/03/21 16:50:50 blockchain.go:1074: "DBase.data" created
2024/03/21 16:50:50 blockchain.go:1094: "DBase.data" opened
2024/03/21 16:50:50 gqlReceiver.go:479: Listening on 0.0.0.0:8080 ...
2024/03/21 16:50:50 blockchain.go:3038: "updating.txt" erased
2024/03/21 16:50:50 blockchain.go:3039: Looking for /app/data/duniter_default/updating.txt
2024/03/21 16:50:50 blockchain.go:3040:
Voici le fichier le docker compose de wotwizard:
services:
wotwizard:
image: poka/wotwizard:latest
restart: on-failure
ports:
- "8080:8080"
volumes:
- /var/lib/duniter:/app/data
- data:/app/rsrc/duniter/System/
volumes:
data:
Je te mets aussi des captures de portainer:
Duniter V1
Wotwizard
J’espère que tu pourras m’aider a corriger mes erreurs.
J’ai essayé de mettre en network duniterv1-frontend cela ne fonctionné pas.
c’est normal dans ton compose duniter v1 il faut que tu remplace duniterv1_data par /var/lib/duniter, comme je l’ai indiqué.
@Pini et les pro docker vont hurler en voyant ça mais je pense que ça devrait fonctionner.
J’ai modifier le docker compose de duniter v1:
Avant:
Après:
J’ai redemarrer les container et stark dans portainer:
Voici pour duniter V1
Et wotwizard
Les deux sont en running.
Voici le log de wotwizard
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1787 +0x11c
git.duniter.org/gerard94/util/bTree.(*Database).readPageA(0xc0001245a0, 0x87, {0x9a6aa0, 0xcaf1e0})
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1807 +0x2b
git.duniter.org/gerard94/util/bTree.(*Database).pageManager(0xc0001245a0, 0xc00028e9c0, 0xc00028ea20, 0xc00028ea80, 0xc00028eae0, 0xc00028eb40, 0xc00028eba0, 0xc00028ec00, 0xc00028ec60, 0xc00028ecc0, ...)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1018 +0x50d
created by git.duniter.org/gerard94/util/bTree.(*Factory).OpenBase in goroutine 1
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1340 +0xe6d
2024/03/21 17:54:06 run.go:53: WotWizard Server version 5.11.3 Tools version 1.0.8
2024/03/21 17:54:06 blockchain.go:3117: Adding Blockchain to updateList
2024/03/21 17:54:06 blockchain.go:3244: Starting
2024/03/21 17:54:06 blockchain.go:3245:
2024/03/21 17:54:06 blockchain.go:3090: Making a copy of "DBase.data"
2024/03/21 17:54:06 blockchain.go:3101: Copy made
2024/03/21 17:54:06 misc.go:233: *** ERROR ***
2024/03/21 17:54:06 misc.go:241: EOF
2024/03/21 17:54:06 misc.go:245: 20
0
goroutine 36 [running]:
git.duniter.org/gerard94/util/misc.haltCommon({0xc00005bb80, 0x2, 0x9a3380?})
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/misc/misc.go:250 +0x465
git.duniter.org/gerard94/util/misc.Assert(...)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/misc/misc.go:260
git.duniter.org/gerard94/util/gbTree.(*filer).Read(0xc00035ac60, 0x8)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/gbTree/gbTree.go:157 +0x9f
git.duniter.org/gerard94/util/bTree.(*File).readInt64(0xc00034f010)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:795 +0x28
git.duniter.org/gerard94/util/bTree.(*Database).readBaseLength(0xc0001245a0, 0x87?)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1457 +0x37
git.duniter.org/gerard94/util/bTree.(*Database).selectPage(0xc0001245a0, 0x87)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1787 +0x11c
git.duniter.org/gerard94/util/bTree.(*Database).readPageA(0xc0001245a0, 0x87, {0x9a6aa0, 0xcaf1e0})
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1807 +0x2b
git.duniter.org/gerard94/util/bTree.(*Database).pageManager(0xc0001245a0, 0xc0002949c0, 0xc000294a20, 0xc000294a80, 0xc000294ae0, 0xc000294b40, 0xc000294ba0, 0xc000294c00, 0xc000294c60, 0xc000294cc0, ...)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1018 +0x50d
created by git.duniter.org/gerard94/util/bTree.(*Factory).OpenBase in goroutine 1
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1340 +0xe6d
2024/03/21 17:55:07 run.go:53: WotWizard Server version 5.11.3 Tools version 1.0.8
2024/03/21 17:55:07 blockchain.go:3117: Adding Blockchain to updateList
2024/03/21 17:55:07 blockchain.go:3244: Starting
2024/03/21 17:55:07 blockchain.go:3245:
2024/03/21 17:55:07 blockchain.go:3090: Making a copy of "DBase.data"
2024/03/21 17:55:07 blockchain.go:3101: Copy made
2024/03/21 17:55:07 misc.go:233: *** ERROR ***
2024/03/21 17:55:07 misc.go:241: EOF
2024/03/21 17:55:07 misc.go:245: 20
0
goroutine 9 [running]:
git.duniter.org/gerard94/util/misc.haltCommon({0xc00005bb80, 0x2, 0x9a3380?})
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/misc/misc.go:250 +0x465
git.duniter.org/gerard94/util/misc.Assert(...)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/misc/misc.go:260
git.duniter.org/gerard94/util/gbTree.(*filer).Read(0xc000330c48, 0x8)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/gbTree/gbTree.go:157 +0x9f
git.duniter.org/gerard94/util/bTree.(*File).readInt64(0xc00031f010)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:795 +0x28
git.duniter.org/gerard94/util/bTree.(*Database).readBaseLength(0xc0001245a0, 0x87?)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1457 +0x37
git.duniter.org/gerard94/util/bTree.(*Database).selectPage(0xc0001245a0, 0x87)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1787 +0x11c
git.duniter.org/gerard94/util/bTree.(*Database).readPageA(0xc0001245a0, 0x87, {0x9a6aa0, 0xcaf1e0})
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1807 +0x2b
git.duniter.org/gerard94/util/bTree.(*Database).pageManager(0xc0001245a0, 0xc000288960, 0xc0002889c0, 0xc000288a20, 0xc000288a80, 0xc000288ae0, 0xc000288b40, 0xc000288ba0, 0xc000288c00, 0xc000288c60, ...)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1018 +0x50d
created by git.duniter.org/gerard94/util/bTree.(*Factory).OpenBase in goroutine 1
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1340 +0xe6d
2024/03/21 17:56:07 run.go:53: WotWizard Server version 5.11.3 Tools version 1.0.8
2024/03/21 17:56:07 blockchain.go:3117: Adding Blockchain to updateList
2024/03/21 17:56:07 blockchain.go:3244: Starting
2024/03/21 17:56:07 blockchain.go:3245:
2024/03/21 17:56:07 blockchain.go:3090: Making a copy of "DBase.data"
2024/03/21 17:56:07 blockchain.go:3101: Copy made
2024/03/21 17:56:07 misc.go:233: *** ERROR ***
2024/03/21 17:56:07 misc.go:241: EOF
2024/03/21 17:56:07 misc.go:245: 20
0
goroutine 12 [running]:
git.duniter.org/gerard94/util/misc.haltCommon({0xc00005bb80, 0x2, 0x9a3380?})
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/misc/misc.go:250 +0x465
git.duniter.org/gerard94/util/misc.Assert(...)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/misc/misc.go:260
git.duniter.org/gerard94/util/gbTree.(*filer).Read(0xc00031ec48, 0x8)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/gbTree/gbTree.go:157 +0x9f
git.duniter.org/gerard94/util/bTree.(*File).readInt64(0xc000313010)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:795 +0x28
git.duniter.org/gerard94/util/bTree.(*Database).readBaseLength(0xc0001245a0, 0x87?)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1457 +0x37
git.duniter.org/gerard94/util/bTree.(*Database).selectPage(0xc0001245a0, 0x87)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1787 +0x11c
git.duniter.org/gerard94/util/bTree.(*Database).readPageA(0xc0001245a0, 0x87, {0x9a6aa0, 0xcaf1e0})
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1807 +0x2b
git.duniter.org/gerard94/util/bTree.(*Database).pageManager(0xc0001245a0, 0xc000276960, 0xc0002769c0, 0xc000276a20, 0xc000276a80, 0xc000276ae0, 0xc000276b40, 0xc000276ba0, 0xc000276c00, 0xc000276c60, ...)
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1018 +0x50d
created by git.duniter.org/gerard94/util/bTree.(*Factory).OpenBase in goroutine 1
/go/pkg/mod/git.duniter.org/gerard94/util@v1.0.8/bTree/bTree.go:1340 +0xe6d
efface les données de wotwizard avant de le relancer (son volume data), j’ai remarqué ce genre de problème si on relance wotwizard avec un DB vide monté …
Comment je fais pour effacer les données?
Est ce que dans portainer je remove le volume wotwizard data?
oui, je ne connais pas portainer, mais si tu as cette option, oui.
Pour l’instant le log reste sur :
2024/03/21 18:19:39 blockchain.go:3117: Adding Centralities to updateList
2024/03/21 18:19:39 run.go:53: WotWizard Server version 5.11.3 Tools version 1.0.8
2024/03/21 18:19:39 blockchain.go:3117: Adding Blockchain to updateList
2024/03/21 18:19:39 blockchain.go:3244: Starting
2024/03/21 18:19:39 blockchain.go:3245:
2024/03/21 18:19:39 blockchain.go:1074: "DBase.data" created
2024/03/21 18:19:39 blockchain.go:1094: "DBase.data" opened
2024/03/21 18:19:39 blockchain.go:3038: "updating.txt" erased
2024/03/21 18:19:39 blockchain.go:3039: Looking for /app/data/duniter_default/updating.txt
2024/03/21 18:19:39 blockchain.go:3040:
2024/03/21 18:19:39 gqlReceiver.go:479: Listening on 0.0.0.0:8080 ...
Le port 8080 est ouvert dans la freebox.
excuse je viens de voir tes modification de compose, ce n’est pas ça…
relis bien ce que je t’ai écris:
Je pense que tu t’es emmelé les pinceau dans les composes 
Je viens de modifier
Log duniterv1:
2024-03-21T18:37:16+00:00 - info: WS2P: Could not connect to peer DZPakwcP using `WS2P g1.duniter.org 443: WS2P connection timeout`
2024-03-21T18:37:16+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:16+00:00 - info: WS2P: Could not connect to peer 3tBWySvy using `WS2P g1.geragc.es 443: WS2P connection timeout`
2024-03-21T18:37:16+00:00 - info: WS2P: Could not connect to peer 38MEAZN6 using `WS2P g1.e-is.pro 443: WS2P connection timeout`
2024-03-21T18:37:16+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:16+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:16+00:00 - info: WS2P: Could not connect to peer 8iVdpXqF using `WS2P g1.duniter.org 443: WS2P connection timeout`
2024-03-21T18:37:16+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:16+00:00 - info: WS2P: Could not connect to peer 9sbSxsjd using `WS2P dharma.ynh.fr 443: WS2P connection timeout`
2024-03-21T18:37:16+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:16+00:00 - info: WS2P: init: bundle of peers 4/11
2024-03-21T18:37:31+00:00 - info: WS2P: Could not connect to peer FxjjjgcL using `WS2P v1.g1.rendall.fr 443: WS2P connection timeout`
2024-03-21T18:37:31+00:00 - info: WS2P: Could not connect to peer JAP1cAQe using `WS2P 192.162.70.18 20901: WS2P connection timeout`
2024-03-21T18:37:31+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:31+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:31+00:00 - info: WS2P: Could not connect to peer 26JAQuUm using `WS2P kyrnos.online 20900: WS2P connection timeout`
2024-03-21T18:37:31+00:00 - info: WS2P: Could not connect to peer 5od17N1y using `WS2P g1.bounceme.net 20901: WS2P connection timeout`
2024-03-21T18:37:31+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:31+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:31+00:00 - info: WS2P: init: bundle of peers 5/11
2024-03-21T18:37:31+00:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:ebe6ffe9-8190-4088-ab9b-89fdd5b5a389219ea38e-373b-40d6-bffc-3a8b4ccdd2c8
2024-03-21T18:37:31+00:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:C3oqFogSFTWdFxEUs9g7b3ddXUpK1ET7tzMyvootJmW8:45834133-4652-4082-ab32-66eb041dba2d5e865967-da51-4e6d-aba4-85b95ea8f939
2024-03-21T18:37:31+00:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:45834133-4652-4082-ab32-66eb041dba2d5e865967-da51-4e6d-aba4-85b95ea8f939
2024-03-21T18:37:31+00:00 - trace: WS2P >>> registerACK >>> WS2P:ACK:g1:C3oqFogSFTWdFxEUs9g7b3ddXUpK1ET7tzMyvootJmW8:ebe6ffe9-8190-4088-ab9b-89fdd5b5a389219ea38e-373b-40d6-bffc-3a8b4ccdd2c8
2024-03-21T18:37:31+00:00 - trace: WS2P >>> sendOK >>> WS2P:OK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:ebe6ffe9-8190-4088-ab9b-89fdd5b5a389219ea38e-373b-40d6-bffc-3a8b4ccdd2c8
2024-03-21T18:37:31+00:00 - trace: WS2P >>> registerOK >>> WS2P:OK:g1:C3oqFogSFTWdFxEUs9g7b3ddXUpK1ET7tzMyvootJmW8:45834133-4652-4082-ab32-66eb041dba2d5e865967-da51-4e6d-aba4-85b95ea8f939
2024-03-21T18:37:31+00:00 - info: WS2P: connected to peer C3oqFogS using `WS2P g1.duniter.org 443`!
2024-03-21T18:37:41+00:00 - info: Matched 5 zeros 00000F02D3D504F14053000376927BA340BD4E9482D3868C0B64D9ADF89DA60D with Nonce = 10300000146466 for block#713755 by q1wzQ5
2024-03-21T18:37:46+00:00 - info: WS2P: Could not connect to peer DsEx1pS3 using `WS2P g1.copylaradio.com 443: WS2P connection timeout`
2024-03-21T18:37:46+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:46+00:00 - info: WS2P: Could not connect to peer 7bmwxTBx using `WS2P gibraleon.g1server.net 443: WS2P connection timeout`
2024-03-21T18:37:46+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:46+00:00 - info: WS2P: Could not connect to peer A5DdXxCK using `WS2P g1.cuates.net 443: WS2P connection timeout`
2024-03-21T18:37:46+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:46+00:00 - info: WS2P: Could not connect to peer ndYUMsDJ using `WS2P fania.g1server.net 443: WS2P connection timeout`
2024-03-21T18:37:46+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:37:46+00:00 - info: WS2P: init: bundle of peers 6/11
2024-03-21T18:37:46+00:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:9bb8b2f3-38e3-422a-8c08-2d0e57113b687900c809-5767-48ce-a854-3fcb3c29a5b0
2024-03-21T18:37:46+00:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:Bb3eGMnSbxnihY5AYJepZLGbV6Ga3FvgK1GRue1keySb:8edf85a8-c64e-4b48-9a6b-d4832939d1b9a7041963-4533-476e-adb9-d8a9a1d6c0b8
2024-03-21T18:37:46+00:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:8edf85a8-c64e-4b48-9a6b-d4832939d1b9a7041963-4533-476e-adb9-d8a9a1d6c0b8
2024-03-21T18:37:46+00:00 - trace: WS2P >>> registerACK >>> WS2P:ACK:g1:Bb3eGMnSbxnihY5AYJepZLGbV6Ga3FvgK1GRue1keySb:9bb8b2f3-38e3-422a-8c08-2d0e57113b687900c809-5767-48ce-a854-3fcb3c29a5b0
2024-03-21T18:37:46+00:00 - trace: WS2P >>> sendOK >>> WS2P:OK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:9bb8b2f3-38e3-422a-8c08-2d0e57113b687900c809-5767-48ce-a854-3fcb3c29a5b0
2024-03-21T18:37:46+00:00 - trace: WS2P >>> registerOK >>> WS2P:OK:g1:Bb3eGMnSbxnihY5AYJepZLGbV6Ga3FvgK1GRue1keySb:8edf85a8-c64e-4b48-9a6b-d4832939d1b9a7041963-4533-476e-adb9-d8a9a1d6c0b8
2024-03-21T18:37:46+00:00 - info: WS2P: connected to peer Bb3eGMnS using `WS2P duniter.g1.pfouque.xyz 20901`!
2024-03-21T18:37:46+00:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:aaa04ac7-e9b9-47c5-a0a7-d8019fa494d255ca79de-8bca-4063-a74a-f7c945bfb94f
2024-03-21T18:37:46+00:00 - error: WS2P >>> >>> WS ERROR: INCORRECT_PUBKEY_FOR_REMOTE
2024-03-21T18:37:46+00:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:4f203ab2-636e-4a75-8223-be649c40728c6dcd2ab9-df30-49d5-b989-27e450d4ba2e
2024-03-21T18:37:46+00:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:EnFfLNWnonXwxmzipLbbqa1fybSs7xdPoYhmbkMYzR3G:2f11767a-3f4f-4f3f-9cdd-b76aa5c85d6837f58d8b-7758-41c0-89ce-4122515f472b
2024-03-21T18:37:46+00:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:2f11767a-3f4f-4f3f-9cdd-b76aa5c85d6837f58d8b-7758-41c0-89ce-4122515f472b
2024-03-21T18:37:46+00:00 - trace: WS2P >>> registerACK >>> WS2P:ACK:g1:EnFfLNWnonXwxmzipLbbqa1fybSs7xdPoYhmbkMYzR3G:4f203ab2-636e-4a75-8223-be649c40728c6dcd2ab9-df30-49d5-b989-27e450d4ba2e
2024-03-21T18:37:46+00:00 - trace: WS2P >>> sendOK >>> WS2P:OK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:4f203ab2-636e-4a75-8223-be649c40728c6dcd2ab9-df30-49d5-b989-27e450d4ba2e
2024-03-21T18:37:46+00:00 - error: WS2P >>> >>> WS ERROR: INCORRECT_PUBKEY_FOR_REMOTE
2024-03-21T18:37:46+00:00 - trace: WS2P >>> registerOK >>> WS2P:OK:g1:EnFfLNWnonXwxmzipLbbqa1fybSs7xdPoYhmbkMYzR3G:2f11767a-3f4f-4f3f-9cdd-b76aa5c85d6837f58d8b-7758-41c0-89ce-4122515f472b
2024-03-21T18:37:46+00:00 - info: WS2P: connected to peer EnFfLNWn using `WS2P g1.brussels.ovh 443`!
2024-03-21T18:38:01+00:00 - info: WS2P: Could not connect to peer 4bibsssD using `WS2P g1.asycn.io 443: WS2P connection timeout`
2024-03-21T18:38:01+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:38:01+00:00 - info: WS2P: Could not connect to peer 33wEa1Sg using `WS2P g1.madeirawonders.com 443: WS2P connection timeout`
2024-03-21T18:38:01+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:38:01+00:00 - info: WS2P: Could not connect to peer 6Ck8QQcG using `WS2P 77.143.54.4 20900: WS2P connection timeout`
2024-03-21T18:38:01+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:38:01+00:00 - info: WS2P: init: bundle of peers 7/11
2024-03-21T18:38:01+00:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:1d8288b8-2579-4c3f-918f-215ec105b9678836be7c-5504-4d80-bf55-c39898f611b2
2024-03-21T18:38:01+00:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:dc5b745a-4b41-4980-bd89-b714f60d656e8a719f99-2188-458a-a186-65d28c6830ad
2024-03-21T18:38:01+00:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:55oM6F9ZE2MGi642GGjhCzHhdDdWwU6KchTjPzW7g3bp:a14093d4-be3f-4476-bcc1-2686dda143f03a7d7824-55ac-4b18-833d-b28720d2a712
2024-03-21T18:38:01+00:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:a14093d4-be3f-4476-bcc1-2686dda143f03a7d7824-55ac-4b18-833d-b28720d2a712
2024-03-21T18:38:01+00:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:ToN5fH62vNkKPmWN5wNBJoMNJtnVy5pf6J5kduZYVRw:8cdee6cf-523a-4cf5-a0f7-76f06e88b7c067a4a61b-0ee9-48ba-ad4e-2a54b8d5e2a2
2024-03-21T18:38:01+00:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:8cdee6cf-523a-4cf5-a0f7-76f06e88b7c067a4a61b-0ee9-48ba-ad4e-2a54b8d5e2a2
2024-03-21T18:38:01+00:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:0caa8037-114f-438b-83cf-1bd97ddc73add2f6a342-e9f3-4217-9b84-4ade026298bd
2024-03-21T18:38:01+00:00 - trace: WS2P >>> registerACK >>> WS2P:ACK:g1:ToN5fH62vNkKPmWN5wNBJoMNJtnVy5pf6J5kduZYVRw:dc5b745a-4b41-4980-bd89-b714f60d656e8a719f99-2188-458a-a186-65d28c6830ad
2024-03-21T18:38:01+00:00 - trace: WS2P >>> sendOK >>> WS2P:OK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:dc5b745a-4b41-4980-bd89-b714f60d656e8a719f99-2188-458a-a186-65d28c6830ad
2024-03-21T18:38:01+00:00 - trace: WS2P >>> registerOK >>> WS2P:OK:g1:ToN5fH62vNkKPmWN5wNBJoMNJtnVy5pf6J5kduZYVRw:8cdee6cf-523a-4cf5-a0f7-76f06e88b7c067a4a61b-0ee9-48ba-ad4e-2a54b8d5e2a2
2024-03-21T18:38:01+00:00 - info: WS2P: connected to peer ToN5fH62 using `WS2P g1.asycn.io 443`!
(node:31) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 end listeners added. Use emitter.setMaxListeners() to increase limit
(node:31) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 data listeners added. Use emitter.setMaxListeners() to increase limit
2024-03-21T18:38:01+00:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:1eec9adb-36bd-4b41-b8fb-ce7e5e60551a165f5fd0-c14b-451b-a77c-5b74b4b32ddd
2024-03-21T18:38:01+00:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2024-03-21T18:38:01+00:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2024-03-21T18:38:01+00:00 - trace: WS2P >>> registerACK >>> WS2P:ACK:g1:55oM6F9ZE2MGi642GGjhCzHhdDdWwU6KchTjPzW7g3bp:1d8288b8-2579-4c3f-918f-215ec105b9678836be7c-5504-4d80-bf55-c39898f611b2
2024-03-21T18:38:01+00:00 - trace: WS2P >>> sendOK >>> WS2P:OK:g1:q1wzQ5KvSBDHcFRk5SKrH7KaSDHv3JUbzRQd3XF6m4J:1d8288b8-2579-4c3f-918f-215ec105b9678836be7c-5504-4d80-bf55-c39898f611b2
2024-03-21T18:38:01+00:00 - trace: WS2P >>> registerOK >>> WS2P:OK:g1:55oM6F9ZE2MGi642GGjhCzHhdDdWwU6KchTjPzW7g3bp:a14093d4-be3f-4476-bcc1-2686dda143f03a7d7824-55ac-4b18-833d-b28720d2a712
2024-03-21T18:38:01+00:00 - info: WS2P: connected to peer 55oM6F9Z using `WS2P g1.trentesaux.fr 443`!
2024-03-21T18:38:16+00:00 - info: WS2P: Could not connect to peer 2r4y56m5 using `WS2P g1.jef.rendall.fr 443: WS2P connection timeout`
2024-03-21T18:38:16+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:38:16+00:00 - info: WS2P: Could not connect to peer HBsi19D9 using `WS2P g1v1.p2p.legal 443: WS2P connection timeout`
2024-03-21T18:38:16+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:38:16+00:00 - info: WS2P: Could not connect to peer A79nvGns using `WS2P g1.nuaje.fr 443: WS2P connection timeout`
2024-03-21T18:38:16+00:00 - debug: WS2P: init: failed connection
2024-03-21T18:38:16+00:00 - warn: Error: not opened
at WebSocket.send (/duniter/node_modules/ws/lib/WebSocket.js:218:38)
at Promise (/duniter/app/modules/ws2p/lib/WS2PConnection.js:524:21)
at new Promise (<anonymous>)
at WS2PConnection.request (/duniter/app/modules/ws2p/lib/WS2PConnection.js:522:16)
at process._tickCallback (internal/process/next_tick.js:68:7)
2024-03-21T18:38:16+00:00 - info: Block resolution: 0 potential blocks after current#713754...
2024-03-21T18:38:16+00:00 - info: WS2P: connection [ToN5fH62 `WS2P g1.asycn.io 443`] has been closed
2024-03-21T18:38:16+00:00 - info: Block resolution: 0 potential blocks after current#713754...
2024-03-21T18:38:21+00:00 - error: WS2P >>> >>> WS ERROR: ANSWER_TO_UNDEFINED_REQUEST
2024-03-21T18:38:32+00:00 - info: Matched 5 zeros 00000B8D4F67064DF51C63C0DFADE814477895E1AC69D22E5F0FC150D12188A9 with Nonce = 10400000532713 for block#713755 by q1wzQ5
2024-03-21T18:38:33+00:00 - info: Matched 5 zeros 00000A9A3732C7A732473B800AF1CDC330CDD4638F70C90EE828D165B4A8233D with Nonce = 10400000543786 for block#713755 by q1wzQ5
2024-03-21T18:38:57+00:00 - info: Matched 5 zeros 00000E76DD51037D241E9743F18642DC0ACCE1F1C24E2504D1C9CE0164294097 with Nonce = 10100000786578 for block#713755 by q1wzQ5
Log wotwizard
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 ...
Quelle est l’url de ton noeud Ğ1 ?
c’est: duniterv1.shainajabu3.noho.st
d’accords, et toujours rien dans les logs wotwizard ?
Tu es sûr que t’es changements de volume ont bien été appliqués en redémarrant tes containers ?
Dans ce cas je ne sais.
tu vois duniterv1_data est toujours utilisé, donc /var/lib/docker n’est pas utilisé par ton container Duniter je suppose.
Il faudrait faire en ligne de commande
docker inspect --format '{{ range .Mounts }}{{ .Source }}:{{ .Destination }} {{ end }}' NOM_DE_TON_CONTAINER_DUNITER
En remplaçant NOM_DE_TON_CONTAINER_DUNITER par le nom de ton container docker affiché via docker ps.
Là tu verra les volumes réellement utilisés.
Je ne connais malheuresement pas Portner pour t’aider via cette interface.
root@shainajabu3:/# docker inspect --format '{{ range .Mounts }}{{ .Source }}:{{ .Destination }} {{ end }}' duniterv1-duniter-1
/var/lib/docker/volumes/duniterv1_etc/_data:/etc/duniter /var/lib/docker/volumes/duniterv1_data/_data:/var/lib/duniter
root@shainajabu3:/#
donc tu vois c’est toujours le volume duniterv1_data qui est utilisé.
Tu devrais voir /var/lib/duniter:/var/lib/duniter à la place.
Tu dois redémarrer ton container pour que les changements soient appliqués.
Attention ça va resync ta blockchain de zero. c’est ainsi que tu pourra voir que c’est bien appliqué.
Pendant ce temps wotwizard ne dira rien et c’est normal.
Tu pourra toujours repassé sur ton ancien volume duniterv1_data si tu as un problème.
Je redémarre sans supprimer le volume duniter data et voici
Pour supprimer le data dans portainer, je dois supprimer le contenaire, j’ai peur de faire une betise avec le noeud si je supprime le contenaire.
Juste docker compose up -d dans le dossier où se situe le docker-compose.yml de duniter devrait suffire. Pas besoin de supprimer l’ancien volume data pour le moment.
Mais supprimer le container ne risque rien, c’est le but de docker. Les container sont volatile, d’où l’intérêt des volumes montés.
