I’ve been using Webmin and Virtualmin for few years, but I still consider myself a “Newbie”
A month ago I was forced to migrate from So You Start to a new bare metal server hosted by OVH.
The OS installation (OVH Image) went smoothly and without any issues.
But since then, almost every time an automatic kernel update takes place (leading into a required reboot), when I perform the reboot from the webmin interface, after the shutdown, the server does not reboot and a hardware reset has to be performed which needs a time-consuming intervention.
I don’t see anything wrong in syslog; only a blank once the shutdown has been completed.
Nothing in kern.log either.
Extensive offline hardware tests have been performed without any error being detected.
CPU temperatures are always well within limits.
Has anybody experienced a similar issue?
Any suggestions?
I just done one.
In fact it was needed to update from kernel 5.15.0-117-generic to 5.15.0-118-generic.
It went OK, no hardware reset needed
Any thoughts?
Change of hosting provider. Especially considering the bad reputation they have.
If I’m allowed (feel free to delete my post if it’s forbidden) I would recommand Kernelhost (my provider). They, according to me, have the most professional support I ever saw and never got technical problems (from their side).
I just tried again using the Webmin reboot and the server hung again.
This time it looks like I will have to move to “rescue mode” to find out what went wrong
I will post the outcome when I (hopefully) I know more…
At the end the “rescue mode” reboot was not needed but a physical hardware reset had to be performed.
Since then I tried a reboot from the Webmin interface and another from the CLI and they both went fine
As part of the intervention, I’ve been told the BIOS has also been updated , I´m not sure if this is really the solution
Anyway, I guess this is not Webmin/Virtualmin related.
A Webmin reboot is just sending a shutdown -r now, which is the same thing that happens when you do a reboot in the CLI (whether you call it with the shorthand reboot or the shutdown command, they’re all just links to systemctl now).
There is no reason it would be differently when done from Webmin. I think you must be seeing some other problem that only happens intermittently, and it’s just happened to randomly occur when you rebooted from Webmin.
I agree with you, but I was wandering if there was anything specific to Webmin that could cause this behaviour?
It seems to occur when a new kernel has been automatically installed and I get the notification that a reboot is required for this new kernel to be applied…
I also have a ticket open with OVH, but their response time is rather slow.
Thanks for the feedback, regards,
Eric
@ Tactikast Thank you for the hint about Kernelhost, they seem to have very positive feedback, I will keep it mind…
It may also happen that the pre-installed OS Image have some problems.
As Joe said It should not be related to Virtualmin. But more the configuration of the installed Ubuntu OS.
In the worst case scenario (if it’s not too much work to reinstall everything), and if the problem come back, Maybe you can install your own OS (your own image directly downloaded from the official Platform; Here Ubuntu)
Hosting provider have their custom Image, sometime they may lead to unexpected behaviour. Still if you would install your own, I can not guarantee the server will work because it may depend how their infrastructure is setup (Maybe I’m saying a mistake, I’m really not sure about this last part). But if it’s a dedicated server it should be fine.
I’m not envisaging migrating again or reinstalling everything, I would rather prefer to identify what is wrong.
I will try to find out more about the customization performed by the hosting provider.
