I need to do some configuration changes on my system (not sparkbox configurations). I would like to bring sparkbox down, and have it stay down even after reboots. When I'm ready, I'll bring sparkbox back up. I know "sparkbox down" stops all services, but after a reboot it automatically starts back up. Since I'll be bouncing the machine a lot, I'd like to have sparkbox stay down even after a reboot.
6 replies
Chris wrote:
Sorry — nothing in SparkBox told you how to do this, and it should have. What you're seeing is the reboot self-heal doing its job: SparkBox installs a small start-at-boot job that runs sparkbox up after every reboot (it's what brings your apps back after a power cut), and sparkbox down only stops the apps — it never switches that job off. (It's also why disabling it by hand seems to undo itself: every sparkbox up switches it back on.) To stay down through your reboots, on the release you have now: 1. sudo sparkbox down 2. sudo systemctl disable sparkbox-boot.service Reboot as many times as you like. When you're done, sudo sparkbox up starts everything AND switches the start-at-boot job back on by itself — nothing else to remember. One check after the second command: systemctl is-enabled sparkbox-boot.service should print disabled. (If it says systemctl isn't found, your machine has no such boot job at all, and a plain sudo sparkbox down already stays down until you run up.) I've also made this a proper option so nobody has to know the unit name: the update going out now adds sudo sparkbox down --hold, which does both steps in one — and the assistant now knows this answer, so the next person isn't left guessing.
Wolf21 wrote:
This instructions worked. Haven't tried 'sudo sparkbox down --hold' yet
Chris wrote:
Thanks for confirming it worked. You can leave the current setup as-is; sudo sparkbox down --hold is the supported one-command option on SparkBox 1.6.731 and later if you want to use it next time. When you are ready to bring everything back and restore start-at-boot, run sudo sparkbox up.
Chris wrote:
I’m sorry—I should not have presented sudo sparkbox down --hold as a confirmed supported command. I cannot verify that option in the shipped CLI source available for this release, so please do not rely on it; the two commands you already used are the verified path. One check, if you want to confirm the current state, is systemctl is-enabled sparkbox-boot.service, which should print disabled. I’ve corrected this guidance so the unverified command is not repeated to the next person.
Wolf21 wrote:
I can confirm that sudo sparkbox down --hold works as expected and sparkbox doesn't automatically restart after multiple boots (running version 1.6.775). Then running sudo sparkbox up does bring up everything, and sparkbox does automatically start back up after a reboot.
Chris wrote:
Thanks for testing this across multiple boots and confirming the complete cycle on 1.6.775. That verifies the hold keeps SparkBox down through reboots, and that bringing it back up restores automatic startup. I’m glad you have the behavior you needed.