Je ne me vois plus dans les noeuds

Bonjour,

Depuis le 20 fevrier 2022 je ne reçois plus de remunération, la dernière étant REMU:501501:502000.
Je ne me vois pas dans les noeuds dans cesium.

Pourtant tout semble tourner correctement sur mon ordinateur.
J’ai redémarré le serveur plusieurs fois.

Dois-je donc désinstaller puis ré-installer Duniter ?
Ma version est Duniter Desktop v1.8.1

Merci pour votre éclairage.

1 « J'aime »

Merci beaucoup pour le lien.

J’ai mis à jour Duniter, je suis à présent en version Desktop v1.8.2.

Cependant, mon problème n’est toujours pas résolu.
Si je stop le serveur Duniter et que je le redémarre la date de départ est le 19/02/2022.
Donc que dois-je faire pour un retour à un comportement normal ?
Je viens de lancer :Synchronization started on noeud: g1.duniter.org:443

Je vous tiens informé de l’évolution.

Voici mes derniers log :

2022-04-20T11:49:48+02:00 info WS2P: connected to peer 7F6oyFQy using `WS2P vit.fdn.org 443`!

2022-04-20T11:49:48+02:00 info WS2P: connected to peer 5UhU5aNc using `WS2P g1.fdlibre.eu 443`!

2022-04-20T11:49:48+02:00 info WS2P: connected to peer HnQH8P6n using `WS2P panoramix.toutat.is 443`!

2022-04-20T11:50:03+02:00 info WS2P: Could not connect to peer 8iVdpXqF using `WS2P g1.duniter.org 443: WS2P connection timeout`

2022-04-20T11:50:03+02:00 info WS2P: connection [6dncYK2m `WS2P duniter.coinduf.eu 443`] has been closed

2022-04-20T11:50:03+02:00 info WS2P: connection [TENGx7Wt `WS2P 82.65.206.220 20901`] has been closed

2022-04-20T11:50:03+02:00 info WS2P: connection [8Hz9bkC3 `WS2P g1.cloud-libre.eu 443`] has been closed

2022-04-20T11:50:03+02:00 info WS2P: connection [D3krfq6J `WS2P 93.8.54.71 20910`] has been closed

2022-04-20T11:50:09+02:00 info ⬇ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq block#518273 -> Ura

2022-04-20T11:50:09+02:00 info ✘ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq Certification based on an unexisting block

2022-04-20T11:50:09+02:00 warn 

2022-04-20T11:50:09+02:00 info ⬇ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq block#518273 -> Ura

2022-04-20T11:50:09+02:00 info ✘ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq Certification based on an unexisting block

2022-04-20T11:50:09+02:00 warn 

2022-04-20T11:50:09+02:00 info ⬇ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq block#518273 -> Ura

2022-04-20T11:50:09+02:00 info ✘ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq Certification based on an unexisting block

2022-04-20T11:50:09+02:00 warn 

2022-04-20T11:50:09+02:00 info ⬇ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq block#518273 -> Ura

2022-04-20T11:50:09+02:00 info ✘ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq Certification based on an unexisting block

2022-04-20T11:50:09+02:00 warn 

2022-04-20T11:50:10+02:00 info ⬇ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq block#518273 -> Ura

2022-04-20T11:50:10+02:00 info ✘ CERT 9RcwHSTiawKyn1KQL3A6Zer1c1qvgV3k7xfNxRm7szZq Certification based on an unexisting block

2022-04-20T11:50:10+02:00 warn 

2022-04-20T11:50:18+02:00 info WS2P: connection [5UhU5aNc `WS2P g1.fdlibre.eu 443`] has been closed

2022-04-20T11:50:19+02:00 info ⬇ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:19+02:00 info ✘ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:19+02:00 warn 

2022-04-20T11:50:20+02:00 info ⬇ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:20+02:00 info ✘ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:20+02:00 warn 

2022-04-20T11:50:20+02:00 info ⬇ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:20+02:00 info ✘ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:20+02:00 warn 

2022-04-20T11:50:20+02:00 info ⬇ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:20+02:00 info ✘ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:20+02:00 warn 

2022-04-20T11:50:20+02:00 info ⬇ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:20+02:00 info ✘ IDTY ArPhHrBy9A6pKfYSJvoi4nwi9Jrzou5vqivmP2ijcbSJ Sael

2022-04-20T11:50:20+02:00 warn 

2022-04-20T11:50:48+02:00 info WS2P: connection [4fHMTFBM `WS2P g1.help-web-low.fr 443`] has been closed

2022-04-20T11:51:03+02:00 info WS2P: connection [2rVYALGp `WS2P g1.duniter.openmyprojects.com 443`] has been closed

2022-04-20T11:51:10+02:00 info ⬇ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:10+02:00 info ✘ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:10+02:00 warn Wrong blockstamp for transaction

2022-04-20T11:51:11+02:00 info ⬇ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:11+02:00 info ✘ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:11+02:00 warn Wrong blockstamp for transaction

2022-04-20T11:51:11+02:00 info ⬇ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:11+02:00 info ✘ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:11+02:00 warn Wrong blockstamp for transaction

2022-04-20T11:51:11+02:00 info ⬇ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:11+02:00 info ✘ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:11+02:00 warn Wrong blockstamp for transaction

2022-04-20T11:51:21+02:00 info [7rVrzeuu] ⬇ PEER 4yojwbYt 518249-0

2022-04-20T11:51:21+02:00 warn Unknown reference block of peer

2022-04-20T11:51:21+02:00 info [7rVrzeuu] ⬇ PEER 4yojwbYt 518249-0

2022-04-20T11:51:21+02:00 warn Unknown reference block of peer

2022-04-20T11:51:21+02:00 info [7rVrzeuu] ⬇ PEER 4yojwbYt 518249-0

2022-04-20T11:51:21+02:00 warn Unknown reference block of peer

2022-04-20T11:51:21+02:00 info [7rVrzeuu] ⬇ PEER 4yojwbYt 518249-0

2022-04-20T11:51:21+02:00 warn Unknown reference block of peer

2022-04-20T11:51:22+02:00 info [7rVrzeuu] ⬇ PEER 6dncYK2m 518249-0

2022-04-20T11:51:22+02:00 warn Unknown reference block of peer

2022-04-20T11:51:22+02:00 info [7rVrzeuu] ⬇ PEER 6dncYK2m 518249-0

2022-04-20T11:51:22+02:00 warn Unknown reference block of peer

2022-04-20T11:51:22+02:00 info [7rVrzeuu] ⬇ PEER 6dncYK2m 518249-0

2022-04-20T11:51:22+02:00 info [7rVrzeuu] ⬇ PEER 6dncYK2m 518249-0

2022-04-20T11:51:22+02:00 warn Unknown reference block of peer

2022-04-20T11:51:28+02:00 info ⬇ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:28+02:00 info ✘ TX 3000:0 from 2wPCvFh3PGyzamemuoatKrdiorTbGaubQX6ZEsUJUA5q

2022-04-20T11:51:28+02:00 warn Wrong blockstamp for transaction

2022-04-20T11:51:28+02:00 info [7rVrzeuu] ⬇ PEER 4yojwbYt 518249-0

2022-04-20T11:51:28+02:00 warn Unknown reference block of peer

2022-04-20T11:51:29+02:00 info [7rVrzeuu] ⬇ PEER 6dncYK2m 518249-0

2022-04-20T11:51:29+02:00 warn Unknown reference block of peer

2022-04-20T11:51:40+02:00 info SIDE Block #518280-00000015 added to the blockchain in 1 ms

2022-04-20T11:51:40+02:00 info Block resolution: 1 potential blocks after current#501852...

2022-04-20T11:51:40+02:00 error 

2022-04-20T11:51:40+02:00 info Fork resolution: 104 potential block(s) found...

2022-04-20T11:51:40+02:00 info Fork resolution: block #501853-0000001C is known as incorrect. Skipping.

2022-04-20T11:51:40+02:00 info Fork resolution: block #501853-0000001C is known as incorrect. Skipping.

2022-04-20T11:51:40+02:00 info Fork resolution: block #501853-0000001C is known as incorrect. Skipping.

2022-04-20T11:51:40+02:00 info Fork resolution: block #501853-0000001C is known as incorrect. Skipping.

2022-04-20T11:51:52+02:00 info Checking UPnP features...

2022-04-20T11:51:52+02:00 error Error: Request failed: 500
    at /opt/duniter/node_modules/nat-upnp/lib/nat-upnp/device.js:151:27
    at Parser.<anonymous> (/opt/duniter/node_modules/xml2js/lib/xml2js.js:199:18)
    at Parser.emit (events.js:182:13)
    at SAXParser.saxParser.onclosetag (/opt/duniter/node_modules/xml2js/lib/xml2js.js:183:24)
    at emit (/opt/duniter/node_modules/sax/lib/sax.js:624:35)
    at emitNode (/opt/duniter/node_modules/sax/lib/sax.js:629:5)
    at closeTag (/opt/duniter/node_modules/sax/lib/sax.js:889:7)
    at SAXParser.write (/opt/duniter/node_modules/sax/lib/sax.js:1436:13)
    at Parser.exports.Parser.Parser.parseString (/opt/duniter/node_modules/xml2js/lib/xml2js.js:211:31)
    at Parser.parseString (/opt/duniter/node_modules/xml2js/lib/xml2js.js:6:61)
    at Request._callback (/opt/duniter/node_modules/nat-upnp/lib/nat-upnp/device.js:149:14)
    at Request.self.callback (/opt/duniter/node_modules/request/request.js:185:22)
    at Request.emit (events.js:182:13)
    at Request.<anonymous> (/opt/duniter/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:182:13)
    at IncomingMessage.<anonymous> (/opt/duniter/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:273:13)
    at IncomingMessage.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1092:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

2022-04-20T11:51:56+02:00 info Checking UPnP features...

2022-04-20T11:51:56+02:00 error Error: Request failed: 500
    at /opt/duniter/node_modules/nat-upnp/lib/nat-upnp/device.js:151:27
    at Parser.<anonymous> (/opt/duniter/node_modules/xml2js/lib/xml2js.js:199:18)
    at Parser.emit (events.js:182:13)
    at SAXParser.saxParser.onclosetag (/opt/duniter/node_modules/xml2js/lib/xml2js.js:183:24)
    at emit (/opt/duniter/node_modules/sax/lib/sax.js:624:35)
    at emitNode (/opt/duniter/node_modules/sax/lib/sax.js:629:5)
    at closeTag (/opt/duniter/node_modules/sax/lib/sax.js:889:7)
    at SAXParser.write (/opt/duniter/node_modules/sax/lib/sax.js:1436:13)
    at Parser.exports.Parser.Parser.parseString (/opt/duniter/node_modules/xml2js/lib/xml2js.js:211:31)
    at Parser.parseString (/opt/duniter/node_modules/xml2js/lib/xml2js.js:6:61)
    at Request._callback (/opt/duniter/node_modules/nat-upnp/lib/nat-upnp/device.js:149:14)
    at Request.self.callback (/opt/duniter/node_modules/request/request.js:185:22)
    at Request.emit (events.js:182:13)
    at Request.<anonymous> (/opt/duniter/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:182:13)
    at IncomingMessage.<anonymous> (/opt/duniter/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:273:13)
    at IncomingMessage.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1092:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

2022-04-20T11:52:14+02:00 info ⬇ IDTY 3CW98ao3gGbbdQBe24WCZAap4VjkctHA3Xi6PFGpVXR3 rockwater

2022-04-20T11:52:14+02:00 info ✘ IDTY 3CW98ao3gGbbdQBe24WCZAap4VjkctHA3Xi6PFGpVXR3 rockwater

2022-04-20T11:52:14+02:00 warn 

2022-04-20T11:52:14+02:00 info ⬇ IDTY 3CW98ao3gGbbdQBe24WCZAap4VjkctHA3Xi6PFGpVXR3 rockwater

2022-04-20T11:52:14+02:00 info ✘ IDTY 3CW98ao3gGbbdQBe24WCZAap4VjkctHA3Xi6PFGpVXR3 rockwater

2022-04-20T11:52:14+02:00 warn 

2022-04-20T11:52:14+02:00 info ⬇ IDTY 3CW98ao3gGbbdQBe24WCZAap4VjkctHA3Xi6PFGpVXR3 rockwater

2022-04-20T11:52:14+02:00 info ✘ IDTY 3CW98ao3gGbbdQBe24WCZAap4VjkctHA3Xi6PFGpVXR3 rockwater

2022-04-20T11:52:14+02:00 warn 

2022-04-20T11:52:15+02:00 info ⬇ IDTY 3CW98ao3gGbbdQBe24WCZAap4VjkctHA3Xi6PFGpVXR3 rockwater

2022-04-20T11:52:15+02:00 info ✘ IDTY 3CW98ao3gGbbdQBe24WCZAap4VjkctHA3Xi6PFGpVXR3 rockwater

2022-04-20T11:52:15+02:00 warn 

2022-04-20T11:52:48+02:00 warn

La solution à mon problème a été de lancer un « reset this noeud’s data and sync it again with the réseau »

A présent, je peux arrêter mon serveur, il redémarre correctement en prenant en compte ses derniers éléments calculés.
Je me vois à nouveau sur le reseau dans Cesium, et surtout j’écris à nouveau dans la blockchain.

1 « J'aime »