Webmin update failed and cannot access server via webmin or virtualmin now

Hi

I installed the update to Webmin and it installed fine on 2 servers but on the 3rd it did this

Now updating webmin-virtual-server .. Installing package(s) with command apt-get -y install webmin-virtual-server ..

Reading package lists... Building dependency tree... Reading state information... The following packages will be upgraded: webmin-virtual-server 1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3526kB of archives. After this operation, 105MB of additional disk space will be used. Get:1 http://software.virtualmin.com virtualmin-universal/main webmin-virtual-server 3.82-2 [3526kB] Fetched 3526kB in 5s (663kB/s) (Reading database ... 69731 files and directories currently installed.) Preparing to replace webmin-virtual-server 3.81 (using .../webmin-virtual-server_3.82-2_all.deb) ... Unpacking replacement webmin-virtual-server ... Setting up webmin-virtual-server (3.82-2) ...

Error: Webmin server did not write new PID file

Error

Webmin server did not write new PID file

.. install complete.

Now I cannot access the server via Webmin or Virtualmin

Greg

Status: 
Closed (fixed)

Comments

This sounds somewhat familiar... During one upgrade test (which was an upgrade from GPL to Pro though), I witnessed that behavior too.

Back then, if i recall correctly, the problem was mostly that the Webmin server had stopped and not auto-restarted. If that's the case, it should suffice to restart Webmin manually, by executing

/etc/init.d/webmin start

in a shell.

If that does not help, it's possible that an old Webmin process is hanging. You can find that out with

ps aux | grep miniserv.pl

If you get any processes (in addition to the grep one), kill those with

kill -9 pid

with pid being the first number after the username.

Thanks Locutus

That fixed it, there were 2 processes running (webmin and usermin) killed both and then started webmin and all working now.

Many thanks

Greg

You're welcome, glad it works. :)

Looks like this is resolved then ..

Annoyingly, this happens occasionally to users and I have yet to figure out the cause because it never happens for me!

Automatically closed -- issue fixed for 2 weeks with no activity.