Imagine you are accessing your Website WHM or cPanel or Webmail hosted (in your VPS) and what if you see this
How to solve this
Pre-Requisites : You should have Shell access (as root) to the Node server.
Mostly this happens due to inode issue. The inodes allocated to the server maybe full. inode is a data structure on a traditional Unix-style file system such as UFS. An inode stores basic information about a regular file, directory, or other file system object.
Steps
Say we are logged into the Node Server. There we are going to list all the Containers existing on the Hardware Node. By default, only running Containers are shown.
[root@linuxvps1 ~]# vzlist -a CTID NPROC STATUS IP_ADDR HOSTNAME 100 18 running 100.20.11.111 WEB.EXAMPLE.COM 101 63 running 100.20.12.203 - 102 169 running 100.20.92.182 server2.example.com 103 81 running 100.20.56.169 example.net 78965 236 running 100.20.77.204 server1.example.com
Assume your container is 103. So simply enter into 103 by this command
[root@linuxvps1 ~]# vzctl enter 103
Check if the inodes are full in the container
[root@linuxvps1 ~]# df -i
Most Probably it should display something like this :
Filesystem Inodes IUsed IFree IUse% Mounted on /dev/vzfs 200000 200000 0 100% / none 65536 95 65441 1% /dev
Bang ! The inodes on /dev/vzfs mounted on / are full. You’ve to go nowhere else to see why that error was delivered. A simple solution will work out, you’ve to increase the inode limit. You’ve two options, either through Shell or through the Node Control Panel (like Parallels Infrastructure Manager)
First we will go through Shell mode with this command :
$ vzctl set veid --diskinodes softlimit:hardlimit
Where ‘veid’ is the VPS ID
root@linuxvps1 ~]# vzctl set 103 --diskinodes 7680100:7680200
Second we are going for Node Control Panel. In the infrastructure, you will see your VPS with a ! sign. That indicates your VPS is having some sort of issue.
So you’ve seen the Alert. Next access the VPS, go to Resources tab. I’m sorry to tell you that I grabbed this screenshot after resolving the issue, but it will help you anyway
You should see the ‘Disk Inodes’ is full under ‘Disk Usage’ category (Here it is not !). Next Click Configure to settle this one
See the Highlighted part, the inodes should be limited to some size. Increase it or remove the check mark to make it unlimited. Make sure you save the changes. Now try again accessing cpanel/WHM/Webmail. It should load with out any issues.That makes a smile in your face, isn’t it ?
As usual, start by checking the error log of cPanel at /usr/local/cpanel/logs/error_log
2009-05-23 15:44:24 info [whostmgr2] [28346] Waiting for lock on /var/cpanel/package-limits.yaml held by /usr/local/cpanel/whostmgr/bin/whostmgr2 – locking /var/cpanel/package-limits.yaml with pid 25968
2009-05-23 15:44:25 info [whostmgr2] [28346] Removing expired lock file /var/cpanel/package-limits.yaml.lock
(internal warning while parsing [stdin]) Sat May 23 23:41:28 2009 [25968] warn: Attempt to free unreferenced scalar.
While the error (internal warning while parsing [stdin]) Sat May 23 23:41:28 2009 [25968] warn: Attempt to free unreferenced scalar floods the error log
Permissions were all right, but suddenly this started happening, but only x86_64 architectures only. Reason being the cPanel is killing the process, since it exceeded the memory usage allowed by cPanel.
Solution would be to increase the memory limit of cPanel by following the instructions below.
WHM -> Server Configuration -> Tweak Settings Choose the setting for:
The maximum memory a cPanel process can use before it is killed off (in megabytes). Values less than 128 megabytes can not be specified. A value of “0″ will disable the memory limits.
The settings had 256M there, and increasing the value to 1024 M helped. Server had 8G RAM, so the value of 1024M was fine here.
Continue ReadingWith cPanel 11, this has become very easy. Assuming that you have mod_proxy and mod_rewrite installed on your apache,
Go to WHM –> Tweak Settings –> Check the following settings
Add proxy VirtualHost to httpd.conf to automatically redirect unconfigured cpanel, webmail, webdisk and whm subdomains to the correct port (requires mod_rewrite and mod_proxy)
Automatically create cpanel, webmail, webdisk and whm proxy subdomain DNS entries for new accounts. When this is initially enabled it will add appropriate proxy subdomain DNS entries to all existing accounts. (Use /scripts/proxydomains to reconfigure the DNS entries manually)
Once enabled let the /scripts/proxydomains run and it will be enabled for all existing domains and new ones to be created. For a server with DNS cluster enabled, please refrain from enabling this, as it requires reload of those many zones of domains in the shared server at your DNS server.
Continue ReadingYou may have already know about the following option: Main –> Server Configuration –> Tweak Settings –> The maximum each domain can send out per hour
We recommend you to set it as low as possible. And then make per domain restrictions as below, to increase the numbers.
And you are done!!!
Continue ReadingToday, a few of the resellers of one of our client had an issue where the “List Accounts” option in WHM fails to show any of their accounts. I had to spend around 15 minutes to figure out the issue. Not so tough, but haven’t seen the issue for a while. So here is what I did. I am including the command here and I leave it to your guys to understand the steps and take risks
You are at your risk, because each step is dependent on the result of previous step.
ls -l /var/cpanel/reseller_username.accts
grep OWNER=reseller_username /var/cpanel/users/*
mv /etc/trueuserowners /etc/trueuserowners.bak
/scripts/updateuserdomains
/scripts/updateuserdomains
ls -l /etc/trueuserowners
diff /etc/trueuserowners /etc/trueuserowners.bak
ls -l /var/cpanel/reseller_username.accts
rm /var/cpanel/reseller_username.accts
And now access the resellers’ WHM and all the accounts should be there. If it is still not there, add it manually. How ? by using the “Fetch CSV” option and manually adding those reseller’s account details to /var/cpanel/reseller_username.accts file. But remember you are messing up with a cPanel file directly and don’t blame me, if it gets overridden.
Continue Reading