[solved?] Reboot no longer working

Started by rkubes, April 09, 2025, 08:00:51 AM

Previous topic - Next topic
Print
Go Down Pages1
User actions
April 09, 2025, 08:00:51 AM Last Edit: April 09, 2025, 08:12:48 AM by rkubes Reason: Working now
Hello

Today I noticed a number of my services were in a stopped state, including Acme. I was able to manually restart them all except Acme. I had to go to its settings and hit apply again to get it working.

I then saw some threads on here about certain services "not auto starting" after a reboot. So I decided to try to reboot to see if that was my problem. The UI had the spinning wheel like it was rebooting, then after some time just displayed the dashboard again (not even requiring a new login). I knew this was strange so I looked at my uptime, which is about 25 days. I always reboot after upgrades, so I know for sure I also attempted a reboot last week as well.

Reading about the past CrowdSec issue, I know this is probably indicating some service is not cleanly stopping and is holding up the reboot. (Hence why some services stop but it never actually reboots.) With that said, I'm not sure how to identify which service is holding up the reboot.

Edit/Update: I was looking at the commands people ran for the CrowdSec issue, but couldn't find a process named crowdsec. So I just tried the reboot command from SSH to see if it would output any errors, but the system actually rebooted immediately. After it booted, I'm now able to also reboot from the GUI again. I'm not sure what I did to fix it.
April 09, 2025, 09:09:46 AM #1
Quote from: rkubes on April 09, 2025, 08:00:51 AMReading about the past CrowdSec issue, I know this is probably indicating some service is not cleanly stopping and is holding up the reboot. (Hence why some services stop but it never actually reboots.) With that said, I'm not sure how to identify which service is holding up the reboot.

You can identify those hanging processes with (serial) console. And the crowdsec issue is still there. What I do not understand is why the offending processes are not forcefully killed (SIGKILL) after some timeout period. This is also a long standing issue on OPNsense upgrades.

On another note, I never use the GUI for upgrades or reboots. Just way too unreliable, too many factors that can go wrong there.
Print
Go Up Pages1
User actions