If you are seeing the following error in the exim logs, you will need to reset the exim databases. “The Exim database is most likely corrupted and the following steps should be followed” To reset exim’s database of retry, reject, and wait-report_smtp attempts on cPanel, I find the safest way is to run the following commands. /usr/sbin/exim_tidydb -t 1d /var/spool/exim retry > /dev/null /usr/sbin/exim_tidydb -t 1d /var/spool/exim reject > /dev/null /usr/sbin/exim_tidydb -t 1d /var/spool/exim wait-remote_smtp > /dev/null service exim restart…

Another little fix for a issue I came across this week relating to CloudLinux’s LVEstats2 I had a server running 100% CPU, and doing an huge amount of read/write I/O - causing issues with the SAN shelf. After looking at top, I noticed the LVE process (which collects usage data on users) was consuming most of the CPU, and having a lot of read/write to the disk. After some investigation, and looking at the lve sqlite database (/var/lve/lvestats2.…

While installing packages via npm, it failed with just the message “Killed”. Automatically this triggers me to believe it is memory related. I was after all running the VM with only 1G memory. Fix npm install Killed So to resolve this, you need to create and extend a swap file. You can do this in Ubuntu 14.04 and 16.04 with the following commands: sudo fallocate -l 1G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile sudo swapon –show sudo cp /etc/fstab /etc/fstab.…