Closed h0bb3 closed 2 months ago
c3712ed19a0a13b0282ccdabe4a0f6aa: 0 9694f577127c187693daaef05c5e2641: 1
Updated death counts. On a positive note none have gone offline and so probably just lost some data.
9694f577127c187693daaef05c5e2641: 2 c3712ed19a0a13b0282ccdabe4a0f6aa: 0 64982aec4c678fa35ef10b63e05dcfc1: 1 5e43744fa806560e453a7650c2deca56: 2 babcb2098d6bc9bb02734f61e225018b: 0
Updated total values, uptime in parenthesis
9694f577127c187693daaef05c5e2641: 2 (674168913) c3712ed19a0a13b0282ccdabe4a0f6aa: 0 (674257165) 64982aec4c678fa35ef10b63e05dcfc1: 3 (674302714) 5e43744fa806560e453a7650c2deca56: 2 (674405945) babcb2098d6bc9bb02734f61e225018b: 0 (674301563)
9694f577127c187693daaef05c5e2641: 2 (794923391) c3712ed19a0a13b0282ccdabe4a0f6aa: 0 (794978680) 64982aec4c678fa35ef10b63e05dcfc1: 5 (794878884) - it also seems to have been offline in the explorer graph 5e43744fa806560e453a7650c2deca56: 2 (795072887) babcb2098d6bc9bb02734f61e225018b: 0 (794989500)
9694f577127c187693daaef05c5e2641: 2 (963719328) c3712ed19a0a13b0282ccdabe4a0f6aa: 0 (963773057) 64982aec4c678fa35ef10b63e05dcfc1: 7 (963823089) 5e43744fa806560e453a7650c2deca56: 2 (964064616) babcb2098d6bc9bb02734f61e225018b: 0 (963960749)
9694f577127c187693daaef05c5e2641: 4 (1123276927) c3712ed19a0a13b0282ccdabe4a0f6aa: 0 (17226729) - seems to have been rebooted for some reason. Was offline in explorer 9:10 - 11:10 27 June. 64982aec4c678fa35ef10b63e05dcfc1: 7 (1123325072) 5e43744fa806560e453a7650c2deca56: 2 (1123426561) babcb2098d6bc9bb02734f61e225018b: 0 (1123342206)
9694f577127c187693daaef05c5e2641: 4 (1285995869) c3712ed19a0a13b0282ccdabe4a0f6aa: 0 (150988431) 64982aec4c678fa35ef10b63e05dcfc1: 7 (1286082629) 5e43744fa806560e453a7650c2deca56: 4 (1286234160) babcb2098d6bc9bb02734f61e225018b: 0 (1286162130)
9694f577127c187693daaef05c5e2641: 11 (2093228284) c3712ed19a0a13b0282ccdabe4a0f6aa: 3 (958087082) 64982aec4c678fa35ef10b63e05dcfc1: 11 (2093035376) 5e43744fa806560e453a7650c2deca56: 3 (646171626) babcb2098d6bc9bb02734f61e225018b: 0: (2093215965)
will do one more check during the week if possible. But basically the preemtive revive unfortunately does not work.
Final check:
9694f577127c187693daaef05c5e2641: 13 (2350296678) c3712ed19a0a13b0282ccdabe4a0f6aa: 0 (119598937) 64982aec4c678fa35ef10b63e05dcfc1: 13 (2350466835) 5e43744fa806560e453a7650c2deca56: 4 (903470003) babcb2098d6bc9bb02734f61e225018b: 0 (2350540072)
in realtion to #175 were we had to manually revive 10 times.
We are now running the revive script every 45 minutes with hopes that this will work as a pre-emptive measure to avoid crypto death. However, there are already eGWs that report having been affected by crypto problems. This can be monitored by checking the crypto endpoint as it now also reports the chipDeathCount
Running the revive script when the signing fails is maybe a better idea. The major downside is that running the revive script takes a couple of seconds and this could be a problem in some contexts (therefore the preemptive strategy was a better option).
Lets keep monitoring this a while and decide on a way forward.