Skip to main content

excessive resource usage with script

Comments

5 comments

  • cPanelMichael
    So my question is: since the executable is php-cgi does this mean that the memory is being used by PHP (as opposed to MySQL or cron or something else). If I can narrow this down to definitely being PHP I can start looking through the scripts for potential memory leaks with some confidence that I'm using my time effectively.

    Hello, Yes, it would relate to the specific PHP script referenced under the "Command Line" section of that notification. Keep in mind this notification stems from CSF/LFD as opposed to cPanel, so you'd need to check with their support team if it's not correctly reporting data. Thank you.
    0
  • Ryan_G
    Good to know - thanks for the information.
    0
  • jasoncollege24
    I'm having the same problem, but the command line is not the same. Resource: Virtual Memory Size Exceeded: 434 > 360 (MB) Executable: /opt/cpanel/ea-php70/root/user/bin/php-cgi Command Line: /opt/cpanel/ea-php70/root/user/bin/php-cgi I've increased the allotted Virtual memory size in lfd 3 times now, and no matter how much i increase it, this still happens. My server only has 500MB of virtual memory, and if this keeps up, i'm going to go over that very quickly. Today, I switched the one site i had using PHP7.0 to 5.6. This will let me find out if it's the site, or some issue with PHP 7. If this is a problem with PHP 7, would there be a way to resolve it, without uninstalling?
    0
  • cPanelMichael
    Hello @jasoncollege24, It's unlikely to relate to the version of PHP utilized on the system. What PHP handler and MPM option is enabled on the server? Is the website using a specific script (e.g. WordPress)? Thank you.
    0
  • jasoncollege24
    The subdomain in question was using mod_mpm_prefork for the MPM Home > Software > MultiPHP Manager says that cgi is the PHP handler for PHP 7 I believe this was caused by using OwnCloud on a server with low memory, and have removed the owncloud software as a test, but thank you! Your question has possibly sent me in the right direction to resolve another minor issue I've had for a while, that may be resolved by changing PHP handlers
    0

Please sign in to leave a comment.