Dev {Tricks}

You are here: Home / Archives for Server and Hosting / Web Control Panel / CentOS Web Panel

by

Disk Usage Check | CWP | CWPpro

In most cases, full disk space usage on a server is caused by backups or logs but it can be also many other things.
Lets find out the cause and fix it.
List partitions and usage

df -h

Check Disk Usage per User

repquota -a -s

Show only accounts with usage in Gbytes

repquota -a -s | grep G

Check Disk Usage per Partition ignoring links
* You can replace /home with the parition or folder you want to check
Let’s check /home partition

du -hx --max-depth 1 /home

Show only folders with usage in Gbytes

du -hx --max-depth 1 /home | grep G

Check /var partition

du -hx --max-depth 1 /var

Show only folders with usage in Gbytes

du -hx --max-depth 1 /var | grep G

Check Mail folder /var/vmail

du -hx --max-depth 1 /var/vmail

Show only folders with usage in Gbytes

du -hx --max-depth 1 /var/vmail | grep G

Check MySQL folder /var/lib/mysql

du -hx --max-depth 1 /var/lib/mysql

Show only folders with usage in Gbytes

du -hx --max-depth 1 /var/lib/mysql | grep G

Check Backups

du -hx --max-depth 1 /backup

Show only folders with usage in Gbytes

du -hx --max-depth 1 /backup | grep G

Show only daily backup folder with usage in Gbytes

du -hx --max-depth 1 /backup/daily | grep G

Now when you know how to check the partitions and folders here are some useful commands to check files in the folder sorted by size:

ls -lahS /folder/location

Example for MySQL folder /var/lib/mysql/

ls -lahS /var/lib/mysql/

Some useful scripts we already have are checking the most frequent folders:
/var/log/
/usr/local/apache/logs/
/usr/local/apache/domlogs/
/usr/local/cwpsrv/logs/
/tmp
/root
/var/lib/mysql/

/scripts/disk_check

Delete Files
Now when you know how to check, the question is how can you delete or empty files.
Note that you shouldn’t delete files other than logs or backups as all others can crash your server.

Log files are in use by the programs so in case you want to clean big active log files you can’t just delete them as they will remain invisible until you restart the service.
The solution is to empty the file, example:

:> /usr/local/apache/logs/access_log

However all other logs files you can simply delete, examples

rm -f  filename

An example case when you have active log files and logrotated which are not active and are renamed with -DATE

Delete single log file NOT currently in use by service

rm -f /var/log/maillog-20211108

Delete all maillog files NOT currently in use by service

rm -f /var/log/maillog-*

Empty active log file which is in use by the service

:> /var/log/maillog

* If you are not sure it’s better to grab a support service and have the experienced sysadmin to check this for you.

by

How to clean all log files in CWP or CWP Pro | Control Web Panel

CWP – Delete All Log Files

First create a file in /root dir :

cd /root
vi clearlog.sh

Then paste this Bash script and save it by press ctrl+x:

#!/bin/bash

truncate -s 0 /usr/local/apache/logs/*bytes
truncate -s 0 /usr/local/apache/logs/*log
truncate -s 0 /usr/local/apache/domlogs/*bytes
truncate -s 0 /usr/local/apache/domlogs/*log
truncate -s 0 /var/log/messages
truncate -s 0 /var/log/maillog
truncate -s 0 /var/log/*log
truncate -s 0 /opt/alt/*/usr/var/log/php-fpm.log
truncate -s 0 /usr/local/cwpsrv/logs/access_log
truncate -s 0 /usr/local/cwpsrv/logs/error_log
truncate -s 0 /var/log/cron
truncate -s 0 /var/log/secure
truncate -s 0 /var/log/cwp/services_action.log
truncate -s 0 /var/log/cwp/cwp_sslmod.log
truncate -s 0 /var/log/cwp/cwp_cron.log
truncate -s 0 /var/log/cwp/cwp_backup.log
truncate -s 0 /var/log/cwp/activity.log
rm -rf /var/log/maillog-*
rm -rf /var/log/monit.log-*
rm -rf /var/log/spooler-*
rm -rf /var/log/messages-*
rm -rf /var/log/secure-*
rm -rf /var/log/pureftpd.log-*
rm -rf /var/log/yum.log-*
rm -rf /var/log/monit.log-*
rm -rf /var/log/cron-*

Change the permission :

chmod 755 /root/clearlog.sh

Now run this command to run the clear log script:

sh /root/clearlog.sh

Thats it the logs will be cleared you can go and check to the respected locations of the log.

Cron Job :

You can also create cron job like below by following solution 2 and create this cron job task according to your needs :

TO run DAILY :

0 0 * * * /usr/bin/sh /root/clearlog.sh

TO run Weekly :

0 0 * * 0 /usr/bin/sh /root/clearlog.sh

TO run Monthly:

0 0 1 * * /usr/bin/sh /root/clearlog.sh

That’s All!
It will save lot’s of space.

by

MySQL: Error Code: 1118

  • #1118 – Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.
  • Change limit for “Mysql Row size too large”
  • Row size too large 8126 Changing some columns
  • 1118 Row size too large

The error was: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

  • Solution
  • Login to phpMyAdmin with root previllege
  • Go to Variables
  • Then edit Innodb Strict Mode as follows 
    innodb_strict_mode = 0

 

by

How To Create a New User and Grant Permissions in MySQL

Access MariaDB Server

mysql -u root -p

Create new database

CREATE DATABASE bdhostidb;

Check whether the database created

SHOW DATABASES;




GRANT ALL PRIVILEGES ON 'sqI_bdhositit_co'.* TO 'sqI_bdhositit_co'@localhost;

by

Move files in the Linux terminal

The mv command moves file(s) from one location to another.

To move a file from one directory to another with mv, remember the syntax below

mv <source> <destination>

For example,

mv example.zip /home

Check whether, it moves example.zip

ls /home

Rename the file as you move it

mv example.zip /home/newexample.zip

Rename a file without moving it to another location

mv example.zip renameexample.zip

Moving a directory

mv exampledir /home

Moving a file safely

mv --interactive example.zip /home

This will ask

mv: overwrite '/home/example.zip'?

If you do not want to manually intervene, use –no-clobber or -n instead.

mv --no-clobber example.zip /home