Timeline for 1.35.3 not syncing since epoch 365
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 27, 2022 at 3:07 | vote | accept | Matthias Sieber | ||
Sep 27, 2022 at 2:18 | answer | added | larissamarcus | timeline score: 0 | |
Sep 26, 2022 at 21:38 | answer | added | Matthias Sieber | timeline score: 1 | |
Sep 25, 2022 at 17:18 | history | edited | Matthias Sieber | CC BY-SA 4.0 |
added 58 characters in body
|
Sep 25, 2022 at 16:28 | comment | added | Matthias Sieber | Connections between BP and relays were stable. Connections to other nodes are impermanent and break soon after they were registered in gLiveView. I don't have any indication that the block was accepted by other pools as the tip is on the las slot in epoch 364. | |
Sep 25, 2022 at 13:50 | comment | added | ADA Capital - ADACT | To be of help I would need a bit more info. Are you running in P2P mode, how many incoming/outgoing connections for your block producer and relays? Was the block you were leader for accepted in gLiveView but not by other pools? | |
Sep 25, 2022 at 12:04 | answer | added | OYSTR Pool | timeline score: 0 | |
Sep 25, 2022 at 5:21 | comment | added | Matthias Sieber | I upgraded all nodes. | |
Sep 25, 2022 at 4:22 | comment | added | Erik de Castro Lopo | You say you upgraded the block producer machine, but did you also upgrade the relays? They must all be upgraded. Also, you should use the git tag rather than just using a particular commit near the tag. | |
Sep 25, 2022 at 1:20 | history | asked | Matthias Sieber | CC BY-SA 4.0 |