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!

WHM and CPanel not opening

Discussion in 'General Discussion' started by lawrence.dcosta, Oct 28, 2006.

  1. lawrence.dcosta

    lawrence.dcosta Active Member

    Oct 6, 2005
    Likes Received:
    Trophy Points:
    Hi Everyone,

    We are unable to open WHM, CPanel and Webmail link, but other services are wokring fine. If someone want to send and receive mails he is able to via MS Outlook/ Outlook Express but not through web interface. It is really confusing becuase other web sites hosted on the server are working fine. We also saw that upcp was running but doesn't seems to have comlpeted and shows the following output:

    ps -ef | grep upcp
    root 17417 17415 0 Oct16 ? 00:00:13 cPanel Update (upcp) - Master
    root 17429 17417 0 Oct16 ? 00:00:00 cPanel Update (upcp) - Slave

    Load on the server is fine and also tried restarting httpd service but it did not work. Our server was configured not to autoupdate so it is like a mystry as how can system run upcp?

    We used command dmesg also found that it did not generate expected output instead it gave following message:

    VFS: file-max limit 131072 reached

    We will be oblidged if someone can please suggeste what is the problem and how to rectify it.

  2. ujr

    ujr Well-Known Member

    Mar 19, 2004
    Likes Received:
    Trophy Points:
    VFS file-max limit reached means that you reached the maximum number of open file handles you cna have on your system.

    To see what your max limit is type:

    cat /proc/sys/fs/file-max

    to change it type

    echo XXXXXXXXX > /proc/sys/fs/file-max ### where XXXXXXXXX is the new file limit.

    Make sure your box has plenty of resources to handle all the files.

    You may also want to find out why it is using all file handlers it in the first place.

    As to upcp not finishing, I would kill the pid(s), kill anything else taking large resources and then try a upcp --force.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice