Nagios PROBLEM Service Alert: Localhost/Root Partition Is WARNING

Forums Index
» Dedicated Hosting Forums
» » nagios PROBLEM Service Alert: localhost/Root Partition is WARNING

Nagios PROBLEM Service Alert: Localhost/Root Partition Is WARNING
Post Description:
Post Tags: nagios, problem, service, alert, localhost, root, partition, is, warning
This Post Has Been Viewed 804 Times Since Sun Oct 21, 2007 8:06 pm Posted By hostman with 1 replies

Nagios PROBLEM Service Alert: Localhost/Root Partition Is WARNING

im getting this error on emails:

***** Nagios *****

Notification Type: PROBLEM

Service: Root Partition
Host: localhost
Address: 127.0.0.1
State: WARNING

Date/Time: Sun Oct 21 20:04:26 PDT 2007

Additional Info:

DISK WARNING - free space: / 12944 MB (20% inode=99%):

Leave Your Comments [ dejar commentarios ]

Comments and replies About Nagios PROBLEM Service Alert: Localhost/Root Partition Is WARNING

:: 1 :: #25313 - Reply By hostman On Mon Oct 22, 2007 9:23 am

i figured it out.. these command i used: change directory to were the large ispconfig files are located at

cd /var/log/httpd/

rm -rf /var/log/httpd/ispconfig_access_log_2007*

its ok if it takes a while, its just deleteing thos huge files

now we need to see the symbolic links

ls -la /var/log/httpd/

you need to delete them

.1
.2
.3
.4
etc..

delete uneeded symbolic links

rm -rf ispconfig_access_log.*

see what symbolic link you need to create now

ls -la

now you need to create the files for the links, it will be the name in red to where the symbolic link is linking..

in my example is shows: ispconfig_access_log -> /var/log/httpd/ispconfig_access_log_2008_03_21

for example:

echo > ispconfig_access_log_2008_03_21

this will create a file called ispconfig_access_log_2007_09_23

now when you see the list of directory you wont see the symbolic link broken

ls -la

there are more you need to delete: this is how my looks like:

# ls -la
total 9452936
drwx------ 2 root root      20480 Mar 21 17:29 .
drwxr-xr-x 9 root root       4096 Mar 17 04:09 ..
-rw-r--r-- 1 root root 1108673845 Mar 21 17:29 access_log
-rw-r--r-- 1 root root 1701928260 Mar 17 04:09 access_log.1
-rw-r--r-- 1 root root 1685572467 Mar 10 04:09 access_log.2
-rw-r--r-- 1 root root 1692506058 Mar  3 04:08 access_log.3
-rw-r--r-- 1 root root 2078082323 Feb 25 04:10 access_log.4
-rw-r--r-- 1 root root  194051400 Mar 21 17:29 error_log
-rw-r--r-- 1 root root  289005081 Mar 17 04:09 error_log.1
-rw-r--r-- 1 root root  280225343 Mar 10 04:09 error_log.2
-rw-r--r-- 1 root root  283765458 Mar  3 04:08 error_log.3
-rw-r--r-- 1 root root  356420764 Feb 25 04:10 error_log.4
lrwxrwxrwx 1 root root         46 Mar 21 00:00 ispconfig_access_log -> /var/log/httpd/ispconfig_access_log_2008_03_21
-rw-r--r-- 1 root root          1 Mar 21 17:29 ispconfig_access_log_2008_03_21
-rw-r--r-- 1 root root          0 Aug 20  2006 ssl_access_log
-rw-r--r-- 1 root root        197 Aug 14  2006 ssl_access_log.1
-rw-r--r-- 1 root root        237 Mar 17 04:09 ssl_error_log
-rw-r--r-- 1 root root        237 Mar 10 04:09 ssl_error_log.1
-rw-r--r-- 1 root root       1185 Mar  8 18:32 ssl_error_log.2
-rw-r--r-- 1 root root        237 Feb 25 04:10 ssl_error_log.3
-rw-r--r-- 1 root root        237 Feb 17 04:09 ssl_error_log.4
-rw-r--r-- 1 root root          0 Aug 20  2006 ssl_request_log

i need to delete:
access_log.1
access_log.2
access_log.3
access_log.4

error_log.1
error_log.2
error_log.3
error_log.4

delete the extra access access logs

rm -rf access_log.*

delete the extra access error logs

rm -rf error_log.*

now you can empty the current error and access log file:

empty acess logs

tail -5 access_log > access_log

empty error logs

tail -5 error_log > error_log

ofcourse, a better way to do this would be to back them up in your disk, depends on your disk space

hope this helps