Submitted by RyanJohnson on Mon, 08/24/2015 - 00:51
Hi,
I am running Cloudmin Pro version 8.3 and am seeing the following error on the List Managed Systems page:
HTTP/1.0 500 Perl execution failed Server: MiniServ/1.760 Date: Mon, 24 Aug 2015 05:43:11 GMT Content-type: text/html; Charset=iso-8859-1 Connection: close
Error - Perl execution failed
Undefined subroutine &server_manager::type_kvm_get_cpu_count called at /usr/share/webmin/server-manager/index.cgi line 477.
See attached screen shot
Status:
Closed (fixed)
Comments
Submitted by andreychek on Mon, 08/24/2015 - 09:41 Comment #1
Howdy -- what is the output of this command:
dpkg -l 'webmin-virtual-server*'
Submitted by RyanJohnson on Mon, 08/24/2015 - 15:33 Comment #2
Hi,
Thanks for getting back to me .. here is the output:
root@duke:~# dpkg -l 'webmin-virtual-server*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-====================================-=======================-=======================-=============================================================================
ii webmin-virtual-server-mobile 2.3 all Webmin theme 'Virtualmin Mobile Theme'
ii webmin-virtual-server-theme 9.2 all Webmin theme 'Virtualmin Framed Theme'
Submitted by JamieCameron on Mon, 08/24/2015 - 23:13 Comment #3
Actually, this looks like a Cloudmin error. Which version of Cloudmin are you running there?
Submitted by RyanJohnson on Mon, 08/24/2015 - 23:59 Comment #4
Hi Jamie,
I have 8.3 Pro .. it's not happening on our dev server which is the same version .. there must be something up with one of the systems
Submitted by JamieCameron on Tue, 08/25/2015 - 00:02 Comment #5
One possible cause is an incomplete upgrade - try running
/etc/webmin/restart
as root from the shell.Submitted by RyanJohnson on Tue, 08/25/2015 - 00:10 Comment #6
That did the trick .. sorry to bother you.
Cheers, ryan
Submitted by JamieCameron on Tue, 08/25/2015 - 00:15 Comment #7
No worries - this should have happened automatically during upgrade.
Submitted by Issues on Tue, 09/08/2015 - 00:17 Comment #8
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by Issues on Tue, 09/08/2015 - 00:17 Comment #9
Automatically closed -- issue fixed for 2 weeks with no activity.