Howto check number of emails in the mail queue:
exim -bpc
To check the email ID, sender and receiver of the each email:
exim -bp | more
To delete frozen emails from the mail queue, execute:
exim -bp | grep ‘frozen’ | awk ‘{print $3}’ | xargs exim -Mrm
similarly, to delete emails sent using a script’
exim -bp | grep ‘<>’ | awk ‘{print $3}’ | xargs exim -Mrm
To disable Mailman on a cPanel server, remove the execute permissions of the mailman wrapper
chmod -x /usr/local/cpanel/3rdparty/mailman/mail/wrapper
If you ever want to enable it:
chmod +x /usr/local/cpanel/3rdparty/mailman/mail/wrapper
Sometimes Apache stops responding and the error logs states the following
“[error] server reached MaxClients setting, consider raising the MaxClients setting”
this indicates that the maximum number of clients that are allowed to connect Apache webserver has reached and you should consider raising the MaxClients and ServerLimit values.
The changes made in the Apache configuration file directly won’t work as cPanel look the new values in the file /var/cpanel/conf/apache/local. However, you can still make the changes directly in the Apache configuration and run the distiller to save the changes.
# pico /usr/local/apache/conf/httpd.conf
Set the new values i.e.
ServerLimit xxx
MaxClients xxx
and save the file. In order to make the changes permanent and make sure the changes don’t get overwritten on the next cPanel update, execute:
# /usr/local/cpanel/bin/apache_conf_distiller –update –main
# /usr/local/cpanel/bin/build_apache_conf
# /scripts/restartsrv httpd
Sometimes, you may receive the following warning message on restarting the Apache web service, for example:
WARNING: MaxClients of 500 exceeds ServerLimit value of 256 servers, lowering MaxClients to 256. To increase, please see the ServerLimit directive.
In such a case, make sure ServerLimit value should be equal to OR greater than MaxClients.
While adding a cron job from cPanel, you may see an error message as
/usr/bin/crontab permissions are wrong (6755). Please set to 4755.
The reason is quite simple, the “crontab” executable have incorrect permissions as stated in the error message. The permissions of /usr/bin/crontab should be 4755.
root@server [~]# ls -la /usr/bin/crontab
-rwsr-xr-x 1 root root 208810 Jun 1 12:24 /usr/bin/crontab*
In order to set the required permissions, ssh to your server as user ‘root’ and use the the ‘chmod’ command to correct the permissions:
chmod 4755 /usr/bin/crontab
OR
chmod u+s /usr/bin/crontab
Once the permissions are corrected, you will be able to add the cronjobs from cPanel.
Your Ftp server rejects your access to the server on providing the username and do not prompt for a password as well and you may see the following error in the your server logs:
Jan 10 11:22:33 mai1 pure-ftpd: (?@xx.xx.xx.xx) [WARNING] Sorry, cleartext sessions are not accepted on this server. Please
reconnect using SSL/TLS security mechanisms.
Ftp can accept three values:
# 0 : disable SSL/TLS encryption layer (default).
# 1 : accept both traditional and encrypted sessions.
# 2 : refuse connections that don’t use SSL/TLS security mechanisms.
If the “TLS” directive below these options is set to 2, you will receive the face the above stated problem. In order to overcome the issue, change the value of “TLS” from 2 to 1 and restart pure-ftpd service:
/scripts/restartsrv pure-ftpd
This will now allow you to access Ftp without using a SSL/TLS security mechanisms.