Since I booted my first mirror node, it seems that it is not working properly.
I can see a lot of connection loss/timeout in logs, but also fork issues, PoW issues and It’s usually not up-to-date. When I restart it, it grabs everything missing and get on par with the longest branch, but when I leave it running it doesn’t. At the time of writing, it is stuck on the block 402199 while the chain is at 402329. Here is an extract of logs:
2021-02-26T19:47:15+00:00 - info: WS2P: init: bundle of peers 6/7
2021-02-26T19:47:15+00:00 - info: WS2P: connected to peer Abpio1ZP using `WS2P g1.bourdon.eu.org 443`!
2021-02-26T19:47:15+00:00 - info: WS2P: connected to peer 8iVdpXqF using `WS2P g1.duniter.org 443`!
2021-02-26T19:47:15+00:00 - info: WS2P: connected to peer 7F6oyFQy using `WS2P vit.fdn.org 443`!
2021-02-26T19:47:15+00:00 - info: WS2P: connected to peer 2ny7YAdm using `WS2P 82.65.206.220 20900`!
2021-02-26T19:47:15+00:00 - info: WS2P: connected to peer HnQH8P6n using `WS2P obelix.toutat.is 443`!
2021-02-26T19:47:15+00:00 - info: WS2P: init: bundle of peers 7/7
2021-02-26T19:47:15+00:00 - info: WS2P: connected to peer 3bGqhAEL using `WS2P duniter2.lucho14.website 443`!
2021-02-26T19:47:16+00:00 - info: WS2P: connected to peer 5UhU5aNc using `WS2P g1.fdlibre.eu 443`!
2021-02-26T19:47:30+00:00 - info: WS2P: connection [74RBUM4V `WS2P monit.g1.nordstrom.duniter.org 443`] has been closed
2021-02-26T19:47:30+00:00 - info: WS2P: connection [8iVdpXqF `WS2P g1.duniter.org 443`] has been closed
2021-02-26T19:47:30+00:00 - info: WS2P: connection [Abpio1ZP `WS2P g1.bourdon.eu.org 443`] has been closed
2021-02-26T19:47:45+00:00 - info: WS2P: connection [2ny7YAdm `WS2P 82.65.206.220 20900`] has been closed
2021-02-26T19:47:48+00:00 - info: SIDE Block #402328-00000010 added to the blockchain in 0 ms
2021-02-26T19:47:48+00:00 - info: Block resolution: 0 potential blocks after current#402199...
2021-02-26T19:47:48+00:00 - info: Fork resolution: 24 potential block(s) found...
2021-02-26T19:48:03+00:00 - warn: Security trigger: proof-of-work process seems stuck
2021-02-26T19:48:03+00:00 - warn: Local node is not a member. Waiting to be a member before computing a block.
[...]
2021-02-26T19:49:25+00:00 - info: [AdmpBbkt] ⬇ PEER 74RBUM4V 402298-0
2021-02-26T19:49:25+00:00 - warn: Unknown reference block of peer
My node’s key is AdmpBbktXNwAdLYRtxaxn4PKDNG51gdghKSeD5AjLkLK.
Now, thoughts and questions:
- The proof of work warning might be simply because the mirror node does not do anything, so in this case the warning could be ignored? Possibly shouldn’t be written at all.
- The node detects a potential fork with ahead, yet it doesn’t switch to it. Config has
switchOnHeadAdvance
so I’d expect it to switch, why doesn’t it switch? - How come I get that much timeouts, is it normal behaviour?