Hello

I am having problems with my server. I am a newbie on dedicated servers.

Please note that my host is non-managing and don't care.

Service Status - in WHM shows the following...

Disk information

Device Mount point Usage
/tmp /var/tmp 2% (11,089 of 495,844)
/dev/sda1 / 89% (8,564,700 of 10,158,008)
/dev/sda2 /home 2% (28,324,328 of 1,927,440,916)
/usr/tmpDSK /tmp 2% (11,089 of 495,844)


As you can see, /dev/sda1 is 89% full and its increasing.

I don't know what it is thats making it increase and I was wondering if you guys can help me sort it out so my server can update cpanel/run smoothly as possible.

If you have questions please ask as I don't know what to give (don't want to give info away that can cause security problems for my server.

Its nearly 1am, and I am going to bed, so no replies till I wake up. Sorry... I hope to get this sorted tomorrow sometime.

/dev/sdaq is mounted on / (root) there are many directories under root / e.g /var/ or /usr/. Most probably may cause under /var/log/* . It is filling up because some daemon/service producing too much logging .e.g apache creates log files in /var/log/apache2/*Filename* some other service logging in /var/log/messages. You can check it with the command
This command will show you the directory name occupying more space e.g it shows you /var/ most space. Then run again the command
again

and so on. Ultimately you will find which directory/file is occupying most space.

Hope it helps

Would be good to know what distro+version you're running
Check logs as above; the most likely problem.

See the logrotate tool which is pretty std on major distros. On RHEL/Centos the main conf is in /etc/logrotate.conf and individual confs in /etc/logrotate.d

Hello

KinnowGrower -

Thanks for the ssh commands

3.3G /var/lib not log... I am going to pin point it down... as you suggested.

3.2G /var/lib/mysql

1.5G /var/lib/mysql/logaholicDB_taffy


chrism01 -

CentOS release 6.4 (Final)
CentOS release 6.4 (Final)
CentOS release 6.4 (Final)
cpe:/o:centos:linux:6:GA

I strongly recommend for servers that you use a logical-volumes filesystem for "pretty much everything." Not only do you not ever want to "run out of space on" a disk drive, but you don't want to direct a preponderance of the traffic to a single head/disk assembly.

When looking at "file sizes," pay attention to open files, which are consuming space on the drive but whose actual size may not be up-to-date in the directory entry. Commands like lsof can help you to see what files are open.