cPanel Troubleshooting
MySQL refuses to start
Sunday, June 3rd, 2007If MySQL refuses to start, please do the following:
1. Check the logs! `tail -f /var/lib/mysql/$(hostname).err`
2. Correct the permissions on /tmp. `chmod 1777 /tmp`
This should in most cases resolve your issue.
All quotas are listing as unlimited for all users
Sunday, June 3rd, 2007There may be a time where all of a sudden all your users are set to an unlimited quota. To fix this, please take the following steps:
1. Confirm quota reports are failing with repquota (repquota -ua)
2. If quotas are reported right, rm -f /home/*/.cpanel/datastore/quota*
3. Verify that quota support is enabled.
4. Determine quota enabled file systems with `mount` or `quota -v`mount -o remount,usrquota /mount/point
5. Reinitialize quotas with /scripts/initquotas
6. Completely rebuild all quota databases with /scripts/fixquotas
This should resolve your issue.
Unable to connect to WHM
Sunday, June 3rd, 2007There may be times when you may not be ableto connect to WHM. Do the following to resolve the issue.
1. Check the error log!
2. Check to see if cpsrvd running:
ps auxww | grep cpsrvd
3. Check to see if the required ports open, and bound by cpsrvd?
netstat -lnp | grep :208
iptables -L -n
4. Check to see if the traffic reaching the server:
tcpdump -n dst port 2087
One of these should resolve the issue and will allow you back into the WHM.
MySQL is using 100% CPU and /var is full
Tuesday, May 8th, 2007Some symptoms that I noticed before I figured out the problem was:
- /var was 100% full
- top showed mysql at the top using 98%-100% CPU (but the load was not too bad)
- ‘mysqladmin proc’ showed many ‘killed’ and sleeping connections for 10000’s of seconds
- mysql would not restart (failed on stop and start)
- when I looked in /var/lib/mysql there were many large files like the following:
-rw-rw---- 1 mysql mysql 743908873 Nov 19 20:38 server23-bin.000001
-rw-rw---- 1 mysql mysql 195841952 Nov 23 07:19 server23-bin.000002
-rw-rw---- 1 mysql mysql 58204739 Nov 24 09:28 server23-bin.000003
-rw-rw---- 1 mysql mysql 79 Nov 24 11:56 server23-bin.000004
-rw-rw---- 1 mysql mysql 122848408 Nov 28 08:11 server23-bin.000005
-rw-rw---- 1 mysql mysql 148310361 Dec 2 05:21 server23-bin.000006
-rw-rw---- 1 mysql mysql 352310491 Dec 14 05:59 server23-bin.000007
-rw-rw---- 1 mysql mysql 23323812 Dec 15 14:12 server23-bin.000008
-rw-rw---- 1 mysql mysql 1073741989 Feb 15 09:28 server23-bin.000009
-rw-rw---- 1 mysql mysql 1073742439 Mar 24 00:00 server23-bin.000010
-rw-rw---- 1 mysql mysql 654110720 Apr 11 18:54 server23-bin.000011
-rw-rw---- 1 mysql mysql 39881 Apr 11 18:59 server23-bin.000012
-rw-rw---- 1 mysql mysql 264 Apr 11 18:56 server23-bin.index
The solution is easy:
- edit /etc/my.cnf and comment out the following lines:
# log-bin
# server-id=1
- save, close, and stop mysql
- remove those ‘bin’ files in /var/lib/mysql
- then restart mysql


























