Hello there
Each time I restart my server, the webmin UI is not accessible for minutes. I really have to wait for about 15 minutes until I can access it.
It is really weird. All the other services on my server work insanely fast after reboot except Virtualmin / Webmin. How come?
Is Webmin's miniserv.pl process actually running during this period?
The issue may be that it is blocked behind other services in the boot order. If you have access to the console during bootup you should be able to see this.
Okay, I checked the log and see it's having issues during boot:
[23/May/2014:19:35:01 +1200] miniserv.pl started
[23/May/2014:19:35:01 +1200] IPv6 support enabled
[23/May/2014:19:35:01 +1200] Using MD5 module Digest::MD5
[23/May/2014:19:35:01 +1200] PAM authentication enabled
[23/May/2014:20:07:24 +1200] Reloading configuration
Failed to initialize SSL connection
When I manually start with
sudo service webmin startfew minutes later, it works. Weird.Those are just warning and diagnostic messages though - they don't indicate startup failure.
At what time did you reboot the system?
Ifound out, that VirtualMin/Webmin use lots of memory. Didn't have enough on my server so I had to buy more. Now Webmin starts faster.
Ok, that would explain it.
Sweet. But tell me, how can I reduce Webmin's numbers of instances?
I see there are many in my process list:
18586 root 129992 kB /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
18587 root 129992 kB /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
18588 root 129992 kB /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
19047 root 129992 kB /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
19048 root 129992 kB /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
19051 root 129992 kB /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
4359 root 125764 kB /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
Those instances share most of their memory, so it won't make much of a difference to reduce them. The number is driven by the number of concurrent browser connections.