Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

(whostmgr (whostmgr)): The subprocess ended prematurely because it received the “KILL” (9) signal.

Discussion in 'General Discussion' started by postcd, May 26, 2016.

  1. postcd

    postcd Well-Known Member

    Oct 22, 2010
    Likes Received:
    Trophy Points:
    When suddenly when i accessed an webpage hosted on a cPanel/WHM server, i got Error 500, it was sudden error during browsing a website so it have to be something with the server, not with the script.

    I had opened a WHM and i clicked Apache Status page, and it said:

    "No response from subprocess (whostmgr (whostmgr)): The subprocess ended prematurely because it received the “KILL” (9) signal."

    whm > tweak settings > "The maximum memory a cPanel process can use before it is killed off (in megabytes)." -- i have 1024

    So from within command line i did:

    free -m


    So there seems to be some free RAM...?

    I did "service cpanel restart" and it returned several errors containing phrasse "The system failed to fork a new process because of an error: Cannot allocate memory"

    I remembered that couple of times i had memory issue and restarting MySQL helped to free RAM, so i did command "service mysql restart" and then cpanel restart worked and Error 500 is away.
    /etc/my.cnf , did my best to tune it according to the mysql tunning script advices

    Please which Linux commands i should do next time this issue happen so i tweak the configurations so this issue no longer happen?
    #1 postcd, May 26, 2016
    Last edited: May 26, 2016
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Apr 11, 2011
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator

    Could you verify if you notice any specific entries in /usr/local/cpanel/logs/error_log when this happens? It's possible your system is running out of memory, as opposed to just cpsrvd.

    Thank you.

Share This Page