August 5, 2025Aug 5 Hi folks, so recently I noticed that when I lose power only for less than 20 seconds, all my containers get turned off and are not restarted after power return and the cancellation of the shutdown operation.This is quite annoying as this regularly happens where I live, sometimes it's just the AC compressor that makes the power in that room trip for 2-3 seconds before returning, when that occurs for slighlty longer than that, I wake up or return to all my containers turned off, there is no attempt to restart them or anything.Even if that was the case I would still have to log back in into a lot of them.The desired behavior was to shutdown after the 300 seconds that I mentioned in the settings, only after that should the full procedure be engaged and the containers turned off, etc not before, it only takes 30 seconds to turn off all my containers so I don't need it to be done pre-emptively. Just like a regular shutdown if I had pressed the button from the main tab.I am posting about this here because, this is not really related to NUT or the network side of the UPS which I have another issue about I will post elsewhere. This is just related to how the OS behaves when power is lost.Maybe I got something wrong, some setting I missed or anything? I would really like to correct this behaviour to the desired one as it occurs to me several times a week.In comparison, in a regular Linux distro or even Windows, when you set the UPS to shutdown after 300 seconds, it shuts down after 300 seconds, there is no closing all the programs and then wait for the shutdown, closing everything is part of the shutdown procedure and should only be initiated when that time limit is reached.Again I may have missed something here. Please let me know.
August 6, 2025Aug 6 Can you post your diagnostics when this happens next. And a screenshot of the settings for the UPS / Nut
August 6, 2025Aug 6 Author 4 hours ago, Squid said:Can you post your diagnostics when this happens next. And a screenshot of the settings for the UPS / NutMy bad after checking the logs I think this is because of NUT actions defaults so indeed related to the plugin:Aug 5 10:23:23 10.0.0.246 Taichi daemon notice upsmon[4950] UPS [email protected] on batteryAug 5 10:23:23 10.0.0.246 Taichi user notice xnut-notify-hooks.sh ONBATT commands are now executing in background...Aug 5 10:23:23 10.0.0.246 Taichi user notice nut-notify [ups] UPS is on battery. The system will shutdown in 240 seconds.Aug 5 10:23:25 10.0.0.246 Taichi user notice root nut-actions: Stopping Docker containers: nextcloud-aio-apache nextcloud-aio-notify-push nextcloud-aio-nextcloud nextcloud-aio-imaginary nextcloud-aio-redis nextcloud-aio-database nextcloud-aio-mastercontainer stash-s6 binhex-jackett resilio-sync kavita Debian-Bookworm binhex-qbittorrentvpn binhex-nicotineplus TubeArchivist-Redis VideoDuplicateFinder Unraid-Cloudflared-Tunnel P3R-OpenRGB TubeArchivist TubeArchivist-ES EmbyServer binhex-krusaderAug 5 10:23:28 10.0.0.246 Taichi kern info kernel br-f8b8724bae99: port 6(vethfaad1fa) entered disabled stateAug 5 10:23:28 10.0.0.246 Taichi kern info kernel vethd7a1e9c: renamed from eth0Aug 5 10:23:28 10.0.0.246 Taichi daemon notice upsmon[4950] UPS [email protected] on line powerAug 5 10:23:28 10.0.0.246 Taichi user notice xnut-notify-hooks.sh ONLINE commands are now executing in background...Aug 5 10:23:28 10.0.0.246 Taichi user notice nut-notify [ups] UPS is online, any planned shutdowns were cancelled.Aug 5 10:23:28 10.0.0.246 Taichi user notice root nut-actions: 'on_battery' task still running, killing task and running 'on_line' taskAug 5 10:23:28 10.0.0.246 Taichi user notice xnut-notify-hooks.sh TerminatedAug 5 10:23:28 10.0.0.246 Taichi user notice root nut-actions: Starting Docker containers: nextcloud-aio-mastercontainerAug 5 10:23:28 10.0.0.246 Taichi kern info kernel docker0: port 14(vethdf477e4) entered disabled stateAug 5 10:23:28 10.0.0.246 Taichi kern info kernel vethfe1f698: renamed from eth0Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel br-f8b8724bae99: port 3(vethed2ff2f) entered disabled stateAug 5 10:23:28 10.0.0.246 Taichi kern info kernel veth6a4d6f7: renamed from eth0Aug 5 10:23:28 10.0.0.246 Taichi kern info kernel br-f8b8724bae99: port 2(veth843de59) entered disabled stateAug 5 10:23:28 10.0.0.246 Taichi kern info kernel veth63fecb9: renamed from eth0 Edited August 6, 2025Aug 6 by MonadProxy
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.