Sep 13, 2004
I have a VPS, every month I need to order 20Gb without reason...

Its just a 1 site VPS.

When I checked disk space uses in Cpanel
we see its just 19GB of files
we dont have any backup service turned on. or any backups.

Command: df -h

shows this...

Filesystem Size Used Avail Use% Mounted on
/dev/vzfs 200G 183G 18G 92% /
none 1.5G 4.0K 1.5G 1% /dev

Command: du -sh * | sort -hr | head -n10
shows this...

du: cannot access `proc/5350/task/5350/fd/4': No such file or directory
du: cannot access `proc/5350/task/5350/fdinfo/4': No such file or directory
du: cannot access `proc/5350/fd/4': No such file or directory
du: cannot access `proc/5350/fdinfo/4': No such file or directory
152G var
19G home
11G usr
105M root
28M opt
26M lib64
11M lib
7.8M etc
7.5M bin
7.4M sbin

[email protected] [/var]# du -sh * | sort -hr | head -n10
139G log
6.8G cpanel
3.7G spool
2.7G lib
49M cache
6.2M named
860K db
340K run
64K profiles
40K tmp

[email protected] [/var/log]# du -sh * | sort -hr | head -n10
135G messages
2.7G j
601M exim_mainlog
486M btmp
323M secure
162M maillog
113M cron
84M messages.tar.gz
83M exim_rejectlog
44M exim_mainlog-20160316.gz

so what the Hell is messages? how to get rid of it?

can anybody help please?

Log rotation size threshold is 300MB but why its going beyond.... how to delete it?
Last edited by a moderator:


cPanel Technical Analyst
Staff member
Oct 4, 2017
cPanel Access Level
Root Administrator

Syslog is a standard logging facility which collects messages of various programs and services including the kernel, and stores them, depending on setup, in a bunch of log files typically under /var/log/.

You can read about Syslog below:

syslog - Wikipedia

The file /var/log/messages aims at storing valuable, non-debug and non-critical messages. This log should be considered the "general system activity" log.

I would recommend reviewing the contents of the log to determine what is causing this specific log to grow in size, regarding your logs not being properly rotated I was able to locate a similar issue which previously occurred that may provide assistance:

logrotate problem

Please feel free to open up a ticket with us so that we can investigate this further