This script deletes:
- messages logs
- maillog logs
- apache/nginx domain logs
- apache standard logs
- php-fpm logs
- /tmp and session logs
- root maillog
- acme/letsencrypt logs
- cwp logs

Usage:

sh /scripts/clean_all_server_logs

Usage:

sh /scripts/disk_usage_per_user

Example output:

[root@webserver ~]# sh /scripts/disk_usage_per_user
--------------------------------------------------------------------------------
USER                   PARTITION    USED       SOFT LIMIT   HARD LIMIT  
--------------------------------------------------------------------------------
crwcave                /dev/md3     110G       147G         147G        
root                   /dev/md3     101G       Unlimited    Unlimited   
rexlestatevrt          /dev/md3     89192M     147G         147G        
devlfgfd               /dev/md3     86660M     147G         147G        
elektrocpp             /dev/md3     75215M     99999M       99999M      
autocop                /dev/md3     61517M     147G         147G        

Example: Clean all files older than 3 months

sh /scripts/clean_goaccess_files 3

* This script will delete all goAccess Files/Data and free some disk space on your server.

Add this configuration in file /etc/mail/spamassassin/local.cf

use_bayes 0
bayes_auto_learn 0

then restart amavisd

systemctl restart amavisd

- Innodb table can crash if there is power lose for your dedicated server.
- Force shutdown of MySQL service can end up in Innodb crash.
- Space issue on the serve can case Innodb crash, if the server space is 100% filled and mysql not able to write on the disk.
- High load on the server can cause Innodb crash.
- High I/O wait on the disk can also cause MySQL innodb crash.

How to determine if innodb is crashed.?
You can determine this by checking MySQL logs, On most of the servers location of the Log is /var/lib/mysql/HOSTNAME.err
You can also use commands:

systemctl status mariadb.service
journalctl -xe

Full MySQL backup
Backup MySQL users and permissions

pt-show-grants > /root/pt-show-grants.sql

Backup Full MySQL folder, Make sure MySQL is STOPPED for this step

rsync -a /var/lib/mysql /home/mysql_bkp/ 

Instructions for full mysql reinstall and recovery
If you can't start mysql, you can try by adding the following code in file /etc/my.cnf.d/server.cnf under [galera] settings

innodb_force_recovery = 1

Now try to start/restart MariaDB

systemctl restart mariadb.service

* If started successfully then you can start with backup, please note that MySQL is now in read-only mode.
* If not starting then try increasing recovery number for one number in each test

innodb_force_recovery = 2

innodb_force_recovery = 3

innodb_force_recovery = 4

innodb_force_recovery = 5

innodb_force_recovery = 6

When the MySQL is started in recovery mode we need to take backup of all the crashed databases and restore it

Create backup location folders

mkdir /home/mysql_innodb_recovery
mkdir /home/mysql_innodb_recovery/database_backup

Create the list of databases

mysql -e 'show databases;' | grep -v information_schema | grep -v Database  > /home/mysql_innodb_recovery/database_list.txt

* Please confirm that all databases are listed in the file /home/mysql_innodb_recovery/database_list.txt

Make backup of each databases including the database called mysql which is very important.

for db in `cat /home/mysql_innodb_recovery/database_list.txt`; do mysqldump $db > /home/mysql_innodb_recovery/database_backup/$db.sql;done

* this process can take a lot of time depending on your MySQL disk usage.
* Make sure you confirm that all .sql files in folder /home/mysql_innodb_recovery/database_backup/ are not empty.

Drop current databases (We can remove them if the backup was successful)

for db in `cat /home/mysql_innodb_recovery/database_list.txt`; do mysqladmin drop $db;done

Some database won’t get dropped which can be directly removed using the rm -Rf command

rm -Rf /var/lib/mysql/DATABASENAME

Next is to remove ibdata and ib_log files

rm -f ibdata* ib_logfile*

Restarting MariaDB
Remove recovery line innodb_force_recovery from /etc/my.cnf.d/server.cnf and restart MariaDB

systemctl restart mariadb.service

Creating Databases
If the MySQL now works we can start restoring databases, first create databases

for db in `cat /home/mysql_innodb_recovery/database_list.txt`; do mysqladmin create $db;done

Restoring Databases
Now we will restore the backups we have taken.

for db in `cat /home/mysql_innodb_recovery/database_list.txt`; do mysqldump $db < /home/mysql_innodb_recovery/database_backup/$db.sql;done

* This process will take some time, after it is done confirm that there are no any issues in the MySQL logs.

In case of some issues you still have the exact replica of databases in folder /home/mysql_bkp/
MySQL users and permissions are stored in file /root/pt-show-grants.sql
Individual databases backups are stored in .sql files in folder /home/mysql_innodb_recovery/database_backup/

* We suggest to keep all those files few days after the successful restore.

Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known"

On July 1, 2024, CentOS 7 reached end of life, and the CentOS team has moved its repositories to the archive at vault.centos.org. Without updating the repository URLs, packages cannot be updated or validated, resulting in these errors.

Solution, run script:

/scripts/centos7_fix_repository

[core:emerg] [pid 2013449:tid 140639997298560] (28)No space left on device: AH00023: Couldn't create the proxy mutex
[proxy:crit] [pid 2013449:tid 140639997298560] (28)No space left on device: AH02478: failed to create proxy mutex

In most cases this error message will not allow you to start apache, solution is to restart the server or use the command bellow.

Solution:

ipcs -s | awk -v user=nobody '$3==user {system("ipcrm -s "$2)}'

Example Error message:

PHP Fatal error: 
The encoded file /usr/local/cwpsrv/htdocs/resources/admin/include/cron.php has expired.
 in Unknown on line 0

The solution is to manually update CWP from the bash shell.

cd /usr/local/cwpsrv/htdocs
chattr -i -R /usr/local/cwpsrv/htdocs/admin
wget static.cdn-cwp.com/files/cwp/el7/cwp-el7-0.9.8.1160.zip
unzip -o -q cwp-el7-0.9.8.1160.zip
rm -f cwp-el7-0.9.8.1160.zip

cd /usr/local/cwpsrv/var/services/
wget static.cdn-cwp.com/files/cwp/el7/cwp-services.zip
unzip -o -q cwp-services.zip
rm -f cwp-services.zip

Don't forget to change the version from this example 0.9.8.1160 to the latest version which you can find on this link:

https://control-webpanel.com/changelog

Make sure that you check after this if your automatic updates work.

First stop the future updates via yum/dnf package manager, if you skip this step then after each update of curl from the base repo you need to rebuild curl

Centos 7 /EL7 :

cat /etc/yum.conf |grep "^exclude="|grep kernel 1> /dev/null 2> /dev/null || echo 'exclude=curl* libcurl*' >> /etc/yum.conf

Centos 8 stream /EL8 :

cat /etc/dnf.conf |grep "^exclude="|grep kernel 1> /dev/null 2> /dev/null || echo 'exclude=curl* libcurl*' >> /etc/dnf.conf

Now you need to install dependencies to build curl and libcurl:

Centos 7 /EL7 :

yum install libssh libssh-devel libnghttp2-devel libnghttp2 libgsasl libgsasl-devel zstd libzstd-devel libzstd brotli brotli-devel libbrotli 

Centos 8 stream /EL8 :

dnf install libssh libssh-devel libnghttp2-devel libnghttp2 libgsasl libgsasl-devel zstd libzstd-devel libzstd brotli brotli-devel libbrotli 

After you've installed the dependencies build CURL from the source :

cd /usr/local/src
rm -rf curl*
wget https://curl.se/download/curl-7.88.0.zip
unzip curl-7.88.0.zip
cd curl-7.88.0
./configure --with-ssl --with-zlib --with-gssapi --enable-ldap --enable-ldaps --with-libssh --with-nghttp2
make
make install

After the successful build check the cURL version :

curl -V

To update Netdata on EL 7/8 simply run these commands :

yum install lz4-devel lz4 json-c-devel libuv-devel libuv --nobest