Submitted by benjamin_dk on Mon, 09/05/2016 - 03:59
After a reboot this night Webmin takes a lot of CPU power:
root 2782 99.2 0.9 81056 18700 ? Rs 04:22 244:50 /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
The only changes I can think of that I have made, are changes to fcgid.conf. It that now looks like
<IfModule mod_fcgid.c> AddHandler fcgid-script .fcgi FcgidMaxRequestLen 1073741824 FcgidOutputBufferSize 1073741824 FcgidMinProcessesPerClass 0 FcgidMaxRequestsPerProcess 0 FcgidInitialEnv PHP_FCGI_MAX_REQUESTS 0 FcgidInitialEnv PHP_FCGI_CHILDREN 0 FcgidMaxProcesses 40 FcgidMaxProcessesPerClass 20 FcgidFixPathinfo 1 FcgidIdleTimeout 30 FcgidBusyTimeout 300 FcgidProcessLifeTime 300 FcgidIOTimeout 300 FcgidIdleScanInterval 1 FcgidErrorScanInterval 1 FcgidZombieScanInterval 1 </IfModule>
I am running:
Ubuntu 14.04
Webmin version 1.801
Virtualmin Pro version 5.04
Theme version Authentic Theme 18.02
Status:
Active
Comments
Submitted by benjamin_dk on Mon, 09/05/2016 - 04:00 Comment #1
Submitted by benjamin_dk on Mon, 09/05/2016 - 04:47 Comment #2
Restarting Webmin made no difference. But killing the process manually seems to have solved the problem. The question still remains why the CPU usage went so high. I am suspecting it could be related to the monit service monitoring the process.
Submitted by andreychek on Mon, 09/05/2016 - 10:38 Comment #3
Howdy -- the FCGID changes wouldn't affect Virtualmin. I suspect monit wouldn't either.
I'm not sure why that occurred, but my best guess is that when you restart Webmin, it didn't stop the process that was running at high CPU.
So is that working okay now?
Submitted by JamieCameron on Mon, 09/05/2016 - 10:50 Comment #4
If this happens again, check if some action in Webmin or Virtualmin triggered the high CPU use.
Submitted by benjamin_dk on Mon, 09/05/2016 - 13:19 Comment #5
Everything is back to normal. It must have been something in the restart process that triggered the issue. Now that I think about it I am pretty sure there were two webmin processes and one usermin process running. Will take a closer look if it happens again.