GoWilkes

Well-Known Member
Sep 26, 2006
611
24
168
cPanel Access Level
Root Administrator
I'm kind of confused by something, I'm hoping you guys and gals can shed some light on it.

My server is a CentOS 6.10 xen hvm, running WHM v. 78.0.49.

Under server information, I see that /dev/xvda2 is 99G in size, and I'm using 93G. But I have 477M left, putting it at 100%... what happened to those other 6.5G?

Also, tmpfs (mounted on /dev/shm) is 1.9G and uses 0%, and /usr/tmpDSK (mounted on /tmp) is 3.2G and uses 323M. Is there an easy way to shift 1.5G of tmpfs and 2G of /usr/tmpDSK to /dev/xvda2 without formatting or anything?
 

GoWilkes

Well-Known Member
Sep 26, 2006
611
24
168
cPanel Access Level
Root Administrator
I'm so sorry to leave you hanging on this, @cPanelLauren ! I didn't get an email that you had replied, of course :-(

This is the output, though:

Code:
# df -kh
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda2       99G   89G  4.5G  96% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
/dev/xvda1      248M   79M  157M  34% /boot
/usr/tmpDSK     3.2G  103M  2.9G   4% /tmp
I don't know why tmpfs and /usr/tmpDSK are so large, but I can't find a way to recover that space. I know that I'll have to upgrade servers in the near future, I'm just trying to push it off for as long as I can for financial reasons.

I've made a few modifications that have cleared up about 5G, though. One major change was to /etc/logrotate.conf: I set it to rotate daily instead of weekly, to compress log files, and then I added this when I saw that /var/log/munin was taking up over 3G by itself:

Code:
/var/log/munin/munin-graph.log
/var/log/munin/munin-html.log
/var/log/munin/munin-limits.log
/var/log/munin/munin-node.log
/var/log/munin/munin-update.log {
    missingok
    notifempty
    create 640 munin munin
}
Otherwise, my biggest hogs are MySQL and a few hosting clients that insist on keeping their emails on the server :-( So other than squeezing a little here and there, there's not much more that I can do.


Addendum:

I found a directory at /usr/local/apache.ea3/... I migrated to EasyApache 4 last year, and this looks like a bunch of log files that were just backed up. Can I safely delete this entire directory? That's almost 1G by itself.

There's also /usr/local/apache.backup/ and /usr/local/apache.backup_archive/... they're only 46M combined, but can I safely delete them?

I also have almost 1G of log files at /usr/local/cpanel/logs/archive that go back to 2014! Why aren't they rotating out? Can I safely add something like this to /etc/logrotate.conf ?:

Code:
/usr/local/cpanel/logs/archive {
    missingok
    notifempty
}
 
Last edited: