The Planet Forums > tmp directroy is 86% full, usr dir is 84% full

Full Version: tmp directroy is 86% full, usr dir is 84% full

The Planet Forums > System Administration > Web Hosting

ns1

Sep 14 2009, 02:45 PM

So I checked and in tmp found

CODE

770M ./eaccelerator

can i delete this directory from /tmp? Since TMP is 996M in size this is taking up the most of the space...

also in /usr i have this:

CODE

root@server2 [/usr]# du -ah --max-depth=1
28M     ./include
124K    ./man
614M    ./lib
76K     ./doc
4.0K    ./tmp
88M     ./src
8.0K    ./games
1.6M    ./kerberos
20K     ./aquota.user
47M     ./sbin
12K     ./etc
257M    ./bin
20K     ./quota.user
24K     ./X11R6
4.1G    ./local
942M    ./share
21M     ./libexec
16K     ./lost+found
6.1G    .

both tmp and usr have started to increase in size slightly over last month. They haven't jumped much, but they are still increasing...

any suggestions?

Tomy Durden

Sep 14 2009, 03:07 PM

As far as /tmp, you may be able to restart eaccelerator(may need to restart apache also) and it should drop, unless it's preallocating the space. I'm unable to find anything about limiting the size of this cache without also limiting the memory cache. I do see a recommendation of moving it to /var/cache/eaccelerator. You might want to consider this if you have space to spare under /var. Of course, your needs may vary.

/usr is a little more tricky since much of the OS and applications run out of that part of the tree. Uninstall any packages that you're 100% sure you don't need and this should reduce the utilization under that directory. Alway check for dependencies so nothing else breaks. You may also want to drill down into /usr/local to see what's taking space up there.

http://eaccelerator.net/wiki/Settings

ns1

Oct 5 2009, 11:49 AM

in time TMP directory cleared it self but USR not... right now it is on 98%, that is

CODE

Filesystem Size Used Avail Use% Mounted on
/dev/sda3 7.8G 7.2G 198M 98% /usr

So i digged and this is what I found (I don't know what, I am just copy-pasteing

)).

First dig:

CODE

root@server2 [/usr]# du -ah --max-depth=1
28M     ./include
124K    ./man
614M    ./lib
76K     ./doc
4.0K    ./tmp
88M     ./src
8.0K    ./games
1.6M    ./kerberos
20K     ./aquota.user
47M     ./sbin
12K     ./etc
257M    ./bin
20K     ./quota.user
24K     ./X11R6
5.1G    ./local
942M    ./share
21M     ./libexec
16K     ./lost+found
7.1G    .
root@server2 [/usr]#

Obviously "local" is using the most of the space. "Share" is also big, but when I looked there, I couldn't find anything what would stand out. So I digged in "local".

Second dig:

CODE

root@server2 [/usr/local]# du -ah --max-depth=1
2.9M    ./include
28K     ./man
33M     ./frontpage
15M     ./Zend
8.0K    ./clamav
4.7M    ./lib
64K     ./les
1.3G    ./cpanel
296K    ./sim
6.0M    ./src
8.0K    ./games
351M    ./apache.backup_archive
108K    ./bandmin
1.7M    ./cpanel-rollback
36M     ./apache.backup
0       ./ssl
24K     ./sbin
12K     ./etc
16M     ./bin
40K     ./spri
152K    ./bfd
2.0M    ./IonCube
344K    ./share
8.0K    ./libexec
3.3G    ./apache
136M    ./BUAgent
5.1G    .
root@server2 [/usr/local]#

However, here also all seems to be ok. Apache is using 3.3gb and Cpanel 1.3G.
So i went in Apache and found out that error log is using most of the space (2.8Gb):

CODE

root@server2 [/usr/local/apache/logs]# du -ah --max-depth=1
0       ./ssl_scache.dir
12K     ./suphp_log
2.8G    ./error_log
4.0K    ./httpd.pid
0       ./fpcgisock
0       ./ssl_scache.pag
0       ./modsec_debug_log
0       ./audit_log
108M    ./suexec_log
4.0K    ./suexec_log.offset
144K    ./modsec_audit.log
258M    ./access_log
3.2G    .
root@server2 [/usr/local/apache/logs]#

What should I do? Can I save existing error log somewhere else and then purge this one? How do I set up a limit for it's size?

ns1

Oct 6 2009, 04:28 AM

Well, I have solved the issue for now. I have activated Log Rotation in WHM Cpanel.

WHM->Apache configuration->Log Rotation

and archived old logs. although space usage is normal now, it's only a matter of time before it runs out. Any suggestions?

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.