It says “Screenly shutdown has started successfully. Soon you will be able to unplug the power from your Raspberry Pi.”, but nope. It’s still going strong.
When you say “nope, still going strong”, are you referring to the actual Pi hardware or the Screenly system still displaying assets?
Sorry for not being clear. It is still displaying assets.
Hmm… since I dont test with the balena I would have to let nico or vik answer this one, but i think these specific options might still be in development since balena uses a different host OS and since you can send a command to the host to shutdown the container, this command might differ in balenaOS/busybox.
The reboot/shutdown Celery tasks doesn’t get received on situations where the number of active tasks reaches the concurrency limit (which defaults to the number of CPUs of the device).
One possible fix is to set time limit for tasks that takes a while to finish, so that it wouldn’t fill up the task queue. The --concurrency value can also be increased. (See here for details.)
EDIT: I created a GitHub issue for this one: Shutdown and reboot is not working via web UI after a while. · Issue #1920 · Screenly/Anthias · GitHub. I also created a PR: Fixes shutdown and reboot not working after a while by nicomiguelino · Pull Request #1921 · Screenly/Anthias · GitHub (for code review).
@pepeu, @ealmonte32 I already merged the pull request for the fix.
- If you’re using the Balena-based Docker images, your Raspberry Pi should already have the latest updates.
- For Anthias installed on RPi OS Lite, you can upgrade by running the install script again, or run
./bin/run_upgrade.sh.- Please backup your data before doing the upgrade. (In the web UI, go to Settings, then click Get Backup).