release-0.3.6 plan: PC 2 and the Mac after the publish, the node restart loop on the PCs

This commit is contained in:
igneum-labs 2026-10-05 09:50:05 +00:00
parent 8ac875bc06
commit ff5cc18db1

View file

@ -501,7 +501,13 @@ on app 0.3.5, node 2.1.0-20139145; rotation 0 of 6 on the new key and folder.
| Machine | Seen on 0.3.6 | What its log shows |
|---|---|---|
| PC 1 ae432dc7 (Windows, the first over-the-air update through the fixed helper) | 09:37:31Z watch tick (the first tick after the restart); the 0.3.6 engine's first line is at 09:35:17Z, 71 s after the manifest went live | run `win-ae432dc7-20261005-093517`: `IGNEUM-APP version=0.3.6 machine=ae432dc7 platform=windows`; `[ok] updated to Igneum Miner 0.3.6 from 0.3.5`; `config: intake ... key 477bb0ef (packaged); manifest .../dl/<token>/igneum-app-latest.json folder ed9c4d2e (packaged)` (the NEXT key and folder: rotation 1 of 6); `node proof verifier: command (...\igneum-prove-verify.exe)`; `igneumd started (pid 26572)`; `update check: 0.3.6 is current`; `wake: listening at https://relay.igneum.network/wake`, and at 09:36:47Z `update to 0.3.6 complete (from 0.3.5); keeping the previous version for a rollback`; 09:37:15Z a wake stamp change fetched the jobs file within seconds (the instant-jobs path live on Windows). The 0.3.5 engine's own download, stage and helper lines were not uploaded before it quit (its last app-log upload was 09:30:14Z; the node log kept uploading to 09:35:14Z): fetched afterwards with a collect job (below) |
| PC 1 ae432dc7 (Windows, the first over-the-air update through the fixed helper) | 09:37:31Z watch tick (the first tick after the restart); the 0.3.6 engine's first line is at 09:35:17Z, 71 s after the manifest went live | run `win-ae432dc7-20261005-093517`: `IGNEUM-APP version=0.3.6 machine=ae432dc7 platform=windows`; `[ok] updated to Igneum Miner 0.3.6 from 0.3.5`; `config: intake ... key 477bb0ef (packaged); manifest .../dl/<token>/igneum-app-latest.json folder ed9c4d2e (packaged)` (the NEXT key and folder: rotation 1 of 6); `node proof verifier: command (...\igneum-prove-verify.exe)`; `igneumd started (pid 26572)`; `update check: 0.3.6 is current`; `wake: listening at https://relay.igneum.network/wake`, and at 09:36:47Z `update to 0.3.6 complete (from 0.3.5); keeping the previous version for a rollback`; 09:37:15Z a wake stamp change fetched the jobs file within seconds (the instant-jobs path live on Windows). The 0.3.5 engine's own download, stage and helper lines were not uploaded before it quit (its last app-log upload was 09:30:14Z; the node log kept uploading to 09:35:14Z): fetched afterwards with a collect job (below). Then the node: the console showed node 2.1.0-20139145 until 09:44Z, then `2.1.0` with no commit and 0.0 MH/s: the new igneumd.exe does not start (section 9) |
| PC 2 1ccfe586 (Windows) | 09:39:51Z watch tick; engine restart at 09:38:40Z (unix 1791193120: `[ok] updated to Igneum Miner 0.3.6 from 0.3.5`), 4 min 34 s after the manifest went live | run `win-1ccfe586-20261005-093840`: the same header and `config:` fingerprints (477bb0ef, ed9c4d2e); `igneumd started (pid 26476)` 09:38:53Z, then `[error] igneumd exited with code -1073741511 after 6 s; restarting` (0xC0000139, STATUS_ENTRYPOINT_NOT_FOUND), again after 3 s, again after 95 s, and so on: the watchdog restarts it every few seconds; `update to 0.3.6 complete (from 0.3.5); keeping the previous version for a rollback` 09:40:10Z. Mining 0.0 MH/s from the restart (the app marks the update complete on its own health, not the node's: a 0.3.7 item) |
| Mac d937c69d | 09:39:51Z watch tick; engine restart 09:37:35Z (unix 1791193055), 3 min 29 s after the publish | run `mac-d937c69d-20261005-093735`: `[ok] updated to Igneum Miner 0.3.6 from 0.3.5`, fingerprints 477bb0ef/ed9c4d2e, `igneumd started (pid 81496)` from the bundle's bin, `node proof verifier: command (.../igneum-prove-host)` and ten seconds later `node proof verifier reported: command` (the first app node on the network with a verifier), `update to 0.3.6 complete` 09:39:05Z; node 2.1.0-2b6d23ef on the console from 09:39:51Z, mining on |
| Sam's Mac 3a9bf309 | not by 09:48Z (silent 6 min at that tick; its 0.3.5 app checks on its own hourly slot) | |
| PC 37ba0461 | not by 09:48Z (0.3.5, hourly slot) | |
Rotation (`logs.mjs --rotation`): 3 of 6 on the new key and folder from 09:39:51Z (the three machines above), 3 not yet.
## 9. Incident 09:4x BST and the 0.3.7 hotfix