OK, I've rebooted this thing at least 4 times in a row and it is working perfectly. For these recent tests, I've been connecting to the #HestiaPi's WiFi acess point and gracefully rebooting the device.
So next, I'm going to completely shut down the machine (gracefully), and once it has soft powered down, unplug it for a few seconds and then plug it back in.
I expect it will work fine after I do this.
My hypothesis is that something might be getting corrupted when I abruptly yank the power and when it is powered back on, the process that reads this corrupted cache doesn't recover properly and is just chewing up memory and CPU power. This prevents the system from "settling down", which is what is causing the eternal loading screen.
My next test will be to cut power repeatedly until I can reproduce the issue. If I can't repro the problem, it casts doubt on my hypothesis. If I can, then maybe it'll lead me closer to the answer.
And for the record, I feel people should absolutely be able to cut the power abruptly on their thermostat and not have any problems. So that is what I plan on making be the case, if at all possible.
Hestia Hacker
npub1ydh…erpq
2023-12-16 04:30:20
in reply to nevent1q…edly
Author Public Key
npub1ydhmq6k7zshd5chdfrmpqpy44jyn02z7amw98knaqascw2flnpzq5serpqPublished at
2023-12-16 04:30:20Event JSON
{
"id": "7a6857f279d4c3771bee9ad2cbd351f1925fad7c73f563edfd06f4e09b8e0800",
"pubkey": "236fb06ade142eda62ed48f6100495ac8937a85eeedc53da7d076187293f9844",
"created_at": 1702697420,
"kind": 1,
"tags": [
[
"e",
"8dccac2dea6faaeff37b9263552db65003eb9d2cbde78a745e00dc7989a82343",
"",
"root"
],
[
"p",
"236fb06ade142eda62ed48f6100495ac8937a85eeedc53da7d076187293f9844"
],
[
"t",
"HestiaPi"
],
[
"t",
"hestiapi"
]
],
"content": "OK, I've rebooted this thing at least 4 times in a row and it is working perfectly. For these recent tests, I've been connecting to the #HestiaPi's WiFi acess point and gracefully rebooting the device.\n\nSo next, I'm going to completely shut down the machine (gracefully), and once it has soft powered down, unplug it for a few seconds and then plug it back in.\n\nI expect it will work fine after I do this.\n\nMy hypothesis is that something might be getting corrupted when I abruptly yank the power and when it is powered back on, the process that reads this corrupted cache doesn't recover properly and is just chewing up memory and CPU power. This prevents the system from \"settling down\", which is what is causing the eternal loading screen.\n\nMy next test will be to cut power repeatedly until I can reproduce the issue. If I can't repro the problem, it casts doubt on my hypothesis. If I can, then maybe it'll lead me closer to the answer.\n\nAnd for the record, I feel people should absolutely be able to cut the power abruptly on their thermostat and not have any problems. So that is what I plan on making be the case, if at all possible.",
"sig": "3ba557f44eb40045908bac75e5a9e470d4ef717b625fa9e21dd692a5db923301842ef26488da2cf247be1d2cf9d795f1b1f108d8373969afc347be1e2b2cdf47"
}