• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

sw-engine-cgi is using much swap area

U

ugurcane

Guest
Hello,

i am seeing sw-engine-cgi is using so much swap area instead of memory.when swap area is filled, so operating system cannot running as well and become the down.

PID=481 - Swap used: 8552k - (sw-engine-cgi )
PID=482 - Swap used: 8808k - (sw-engine-cgi )
PID=483 - Swap used: 8808k - (sw-engine-cgi )
PID=551 - Swap used: 2620k - (sw-engine-cgi )

and i am seeing a lot of process as below when i checked whic process has much use swap area.

is there any suggestion to fix this trouble?
 
thanks for the reply IgorG,
But we are using the 9.5.4 version of plesk that is running linux, so our configuration file name is "plesk.conf" in /etc/sw-cp-server/applications.d directory.When i change these values as related to solution link, plesk doesn't start and getting failed message.

Also i am seeing four values in plesk.conf file unlike 2 values.

egrep 'max-procs|min-procs' /etc/sw-cp-server/applications.d/plesk.conf
"max-procs" => 1,
"min-procs" => 0,
"max-procs" => 1,
"min-procs" => 0,

which can i change values in these lines to resolve processing problem ?
Any suggestions would be greatly appreciated.
 
Last edited by a moderator:
also i have wonder that what does "1" and "0" values mean?
 
IgorG,

today I had an issue with starting qmail, /usr/local/psa/var/log/maillog told me that too many files were opened.
Grepping on the lsof output, I found that sw-engine-cgi had over 23000 files open.

So I killed all instances, and started Plesk again.

Issue still existed, so I took the guideline of ugurcane and opened up /etc/sw-cp-server/applications.d/plesk.conf
We had seen this issue before, and my colleague had changed the min-procs to 1 in /etc/sw-cp-server/applications.d/plesk.socket.sh
Applying the same fix to /etc/sw-cp-server/applications.d/plesk.conf did the trick for us.


A side note, we have only experienced this with Xen VM's running CloudLinux 5.



PS: IgorG, the KB article has been taken offline: 'Sorry, but this article is outdated.'
It is not, and it would be wise to put it back online, so that others may benefit from it.
 
Back
Top