Tag Info

Hot answers tagged

4

It is complaining that there is only 10% free space left, which is not good. It is saying 99% of the inodes are free.


3

I actually fixed this by installing RPMforge, which just so happens to aim at DAG repository, and then all yum commands to install nagios worked great. Try yum remove nagios-nrpe (etc), then see this page, install the update, then try the command yum install nagios-nrpe again and see if that works.


3

You need to relabel the files with the right selinux type: semanage fcontext -a -s system_u -t httpd_sys_script_exec_t /usr/local/nagios/sbin/*


2

Process accounting (package psacct) can also help.


2

Maybe it would be a good idea to replace: # -------- get dataset of filesystem DATASET=`df -h $1 | grep -v Filesystem | awk '{print $1}'` with the following: # -------- get dataset of filesystem DATASET=`df -h $1 | awk '{print $1}' | tail -n 1` Because of localization issues on some installations, some distros think it's a good idea to replace such ...


2

The user that Nagios runs as requires sudo rights just like with your normal account. You can use a command like this to see what sudo right a user has: $ su - nagios -c "sudo -l" Matching Defaults entries for nagios on this host: requiretty, !visiblepw, env_reset, env_keep="COLORS DISPLAY HOSTNAME HISTSIZE INPUTRC KDEDIR LS_COLORS MAIL PS1 PS2 QTDIR ...


2

The problem is likely that Nagios is never killed/restarted so that it starts logging to a new log file. Here are a couple examples that show how you'd go about doing the postrotate action. /var/log/nagios/nagios.log { daily rotate 180 compress dateext missingok notifempty sharedscripts postrotate /sbin/service nagios reload > /dev/null ...


2

If you are using vhost internaly it is always better solution to make vhost configuration with different ports, so in this case you can setup nagios domain on 8083 port: first step: In httpd.conf you need to spicify listening ports: Listen 8080 Listen 80 Listen 8083 In httpd-vhosts.conf add a NameVirtualHost for every virtual host you want to add. ...


1

The plugins within Nagios are really the secret sauce of what makes Nagios so powerful. The check that performs the HTTP check is this one: $ /usr/lib64/nagios/plugins/check_http check_http: Could not parse arguments Usage: check_http -H <vhost> | -I <IP-address> [-u <uri>] [-p <port>] [-w <warn time>] [-c <critical ...


1

With help from another colleague, we worked out why it didn't work. 3 things: First, we have agentaddress tcp:x.x.x.x:161 in snmpd.conf, just deleted the line Second, iptables is blocking udp port 161, added rules to allow udp port 161 Third, something wrong with the script as you can see the error message about line 319, changed < to lt


1

The problem The error is actually pretty self explanatory. Error: Could not find any hostgroup matching 'allhosts' You have this line in your define host{...} block: hostgroups allhosts ; Host groups this printer is associated with Solution You need to create a hostgroup called allhosts. In the file /etc/nagios/hostgroups.cfg, most ...


1

Nagios actually uses external commands to send email—it doesn't send them directly. For example, in our config here, /etc/nagios3/commands.cfg contains (in part): define command{ command_name notify-host-by-email command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: ...


1

According to your comment your goal is not to actually increase the load on the server, you only want to test the Nagios alert in the case of high load. For doing this, I wouldn't try to actually increase the load of the server, the server load is hard to artificially control so this isn't a very reliable test scenario. Instead you could store the output ...


1

bind failed (Address already in use (errno = 98)). service = nsca indicates that the port (5667) is already in use. Check if nsca is already running. Try netstat -tuan to see if anything else has the port in use. Verify that there is no copy of the nsca file in /etc/xinet.d so that xinetd is trying to start it twice.


1

Take a closer look at snmpd (snmpd.conf). If compiled with the right options you can set trigger actions for a number of things - one of these is CPU-load.


1

It was permissions. This process is trying to start under user "nagios" but root:root is the user:group owner of /usr/local/nagios and user nagios isn't a member of the root group: # groups nagios nagios: nagios centreon Anyway, the solution is (I think): # chmod -R 770 /usr/local/nagios # chgrp -R nagios /usr/local/nagios It now starts right up: # ...


1

Finally found the fix for this: [root@localhost]# make [root@localhost]# make cgis [root@localhost]# make install-cgis


1

Possibly it's an environment issue (the script is relying on something in its environment that is not available when run by nagios). I would change your script (temporarily for debugging only) to: #!/bin/bash exec 2> /tmp/log."$$" set -x wall "Script execution started"; /usr/bin/sudo /root/scripts/disableServer.sh force And add another set -x at the ...


1

First let me tell you that i am extremely sorry for not answering your question as i was a little busy these last few days. Here I am going to provide you two answers to your question . First Answer :(Flat and non innovative): !/bin/sh # # Log file pattern detector plugin for Nagios ...


1

You could run ps aux >> logfile every minute with cron. It includes CPU usage.



Only top voted, non community-wiki answers of a minimum length are eligible