Virtualmin updates have caused Webmin to no longer be available

5 posts / 0 new
Last post
#1 Mon, 01/08/2018 - 10:57
MattWilcox

Virtualmin updates have caused Webmin to no longer be available

I've just run the latest updates on one of our servers and Webmin is no longer running. When I try restarting it from the console via

sudo service webmin restart

I get an error:

Job for webmin.service failed because the control process exited with error code. See "systemctl status webmin.service" and "journalctl -xe" for details.

Looking into the systemctl status webmin.service I can see this:

Failed to start LSB: web-based administration interface for Unix systems.

It looks like something is wrong in a rather profound way after running the latest updates.

I'm running Ubuntu 16.04.3 LTS

Mon, 01/08/2018 - 15:30
Jfro

You didn;t say from what version to which version updated.

2 users her to https://www.virtualmin.com/node/54951#comment-790068

But also try a search for the error. ;) https://www.google.com/search?q=Failed+to+start+LSB:+web-based+administr...

Tue, 01/09/2018 - 03:01
MattWilcox

Updating to the latest version, whatever that is. It's tough to know because Webmin isn't running for me to look at ;)

By running

/etc/webmin/start

I get a different error - looks like one of the sub-servers SSL certs is invalid. For some reason, that's stopping Webmin from running.

Failed to open SSL key /home/ACCOUNTNAME/ssl.key at /usr/share/webmin/miniserv.pl line 4403.

If I edit

/etc/webmin/miniserver.conf

and set sll=0 then webmin starts, but I can't actually log in because Webmin then complains that my browser doesn't support cookies (it does).

Any ideas on how to get around this? How do I disable the SSL just for that account?

Tue, 01/09/2018 - 03:08
MattWilcox

SOLUTION:

https://kallelilja.com/2017/10/failed-open-ssl-key-service-webmin-start/

It turns out there's some sort of problem when a site has been disabled / deleted, but had a LetsEncrypt SSL key, it remains in the config file when it really shouldn't.

I also had to reboot the server. A webmin restart did not suffice as it believed there was something still running on port 10000

Wed, 01/10/2018 - 02:56
MattWilcox

Further details: Apache did not restart after this.

I believe the root cause of all these cryptic errors had been a partially failed deletion of a 'virtual server' account. Although the account did not show up in the main Virtualmin drop-down, it was still there when looking at Webmin > Servers > Apache Webserver > Existing Virtual Hosts.

After deleting it from there Apache was able to restart.