Skip to main content

Email stuck in queue due to server load

Comments

3 comments

  • pixelhub
    I have been looking at the /ect/my.cnf file and installed MySQLTuner form
    https://github.com/major/MySQLTuner-perl
    I made the recommended changes to the variables in the my.cnf file, restarted MYSQL and all seems to be working. there as some general recommendations i don't understand
    Control warning line(s) into /var/lib/mysql/server.domain.co.uk.err file Control error line(s) into /var/lib/mysql/server.domain.co.uk.err file Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
    But after changing the my.cnf file, all is good. hope this helps someone else (if it makes any sense). Cheers Craig
    0
  • Muhammed Fasal
    Do you have CSF firewall installed on your server? If yes, you can disable cpHulkd service on your server safely. Because they both do the same job, CSF will do more than what cpHulkd can do. cPHulk is only Brute Force detection/failed login blocking, whereas a Firewall or a security solution (CSF) includes a lot more. If you need advanced features for your server security like to avoid Apache DDOS attack then only you need to think about CSF otherwise cPHulk will almost do all the other features provided by CSF like auto-blocking of IP address on failed login attempts. Actually, CSF works on top of iptables. The rules you add in CSF will be added to iptables on the back end. While cPHulk uses MySQL database rather than iptables. As I have mentioned cPHulk uses a database, it may consume more resource while on a BruteForce attack. You can check the cPHulkd log entries at: tail -f /usr/local/cpanel/logs/cphulkd.log You can follow this step on Commandline to disable cPHulkd service: /usr/local/cpanel/bin/cphulk_pam_ctl --disable OR /usr/local/cpanel/etc/init/stopcphulkd
    0
  • cPWilliamL
    Hi @pixelhub, I am glad to hear you were able to optimize MySQL. I thought I'd also provide more information on exim and excessive load. To reduce system stress, the exim service will not deliver mail once the load is over 36(default). This is set via 'deliver_queue_load_max' at WHM > Service Configuration > Exim Configuration Manager > Advanced. With that said, addressing the load issue first was certainly the best way to go about fixing this. I'll go ahead and mark this thread solved for you. Thanks for sharing your solution!
    0

Please sign in to leave a comment.