Reboot hangs constantly

I am a relative Linux newbie so apologies if this appears to be a daft question.
I have two VMs with IONOS in the UK. The following problem applies to both VMs. When rebooting after updates (and on other random occasions) from either the Virtualmin/Webmin interface, the system hangs and won’t reboot. Same thing happens if I reboot remotely using SSH

In order to reboot properly, I have to go into my IONOS account. According to IONOS, the reboot command initiated from the IONOS dashboard is simply reboot -r (same as I use in PUTTY and in VirtualMin/Webmin. However the dashboard reboot always works.
If I reboot from Webmin immediately after a successful reboot from the IONOS dashboard, that too completes successfully.
I have looked at the system logs and the main thing I see is " [TTM] Buffer eviction failed" several times during the shutdown process, but that appears to be a graphics driver issue which is not appropriate to my use of the machines.
My assumption is that IONOS shutdown process MUST be different from the one I use, but I wanted to find out if anyone using Virtualmin/Webmin has had any similar experience, because I am pretty sure they will blame the software rather than the OS
Any insight is appreciated

SYSTEM INFORMATION
OS type and version Rocky Linux 9.7
Webmin version
Virtualmin version 7.50.2 Professional

i have rebooted a Ubuntu 24 VM this morning (after prompted to do so) and everything ran through ok
probably no help but it did work.

You can force it.
man reboot is your friend.

Depends on the image used by IONOS. :frowning:

@Ilia / @Jamie Should a force option be added?

1 Like

I don’t understand what is being discussed here.

The OP, new to Linux, is having trouble rebooting. Their machine hangs unless rebooting from the IONOS console. Two different VM’s. I’m just wondering if they should have/need the --force option.

1 Like

Hi Ilia
Basically, the Virtualmin/Webmin reboot function (I believe it issues a reboot -r command) hangs when I am prompted to reboot after an update. Same experience if I SSH into the server and issue reboot -r
I can remedy the situation and reboot successfully directly from the IONOS dashboard. Virtualmin, Apache and Email are uncontactable until then. IONOS says that their dashboard reboot function issues exactly the same command. I suspect that is not the case. I wanted to rule out Virtualmin as a possible cause before I raise it again with IONOS.

Ah, I see now! Thanks for clearing that up! So, it’s usually not really “hung”. Some service or filesystem is taking too long to stop or unmount cleanly. When that happens, systemd waits up to a timeout, often 90 seconds or more, so it looks stuck.

What I’d do is watch it live during a reboot using KVM/IPMI/VPS console. You’d normally see messages like “A stop job is running for …” that tell you exactly which service is holding things up.

After it finally comes back up, you can also check the previous boot’s logs for clues:

journalctl -b -1 -p warning..err
journalctl -b -1 | grep -i 'A stop job is running'

I don’t think anything should be making the --force option easy to use. You ought to know what you’re doing if using it.

1 Like

This would make things clearer.

No, it’s not really going to help because the command is configurable in the module config, and can be just about anything, so on “Reboot” page we just say which command is used, and the button text uses general text without any specifics.

1 Like