So, let’s start.

First we’ll do the Windows-Part.

Grab a copy of NSClient++ (Thanks a lot to Michael Medin for his great work on this AddOn) at http://nsclient.org/nscp/

I prefer the ZIP-Package and a manually installation. But it doesn’t matter if you want to install the MSI. Just take care that you use the 32 or 64 Bit Version.

1. If you have the ZIP-Package as well, just unpack it and move the files to a folder you like (I use C:\Tools\NSClient++).
2. Open nsc.ini and make the following changes:
   1. Line 14: Uncomment NRPEListener.dll
   2. Line 117: allow_arguments=1
   3. Line 121: allow_nasty_meta_chars=1
   4. Line 125: use_ssl=1
   5. Line 135: allowed_hosts=<IP of your Icinga/Nagios Host>

   Explanation: You need allow_arguments and the nasty_meta_chars for Performance Counters, because we need the Backslash to specify them.
   use_ssl and allowed_hosts is just for security reasons, but I suggest to use them
   

3. Start a command prompt and navigate to the directory where you’ve unpacked your NSClient++ Files (make sure you’re running the command prompt as Administrator)
4. Test if NSClient++ is working     =>    “NSClient++.exe” /test
   
   

   If the output looks good (if no error is displayed) exit the Test-Mode with, tada => Exit
   

   This Test-Mode is really handy if a query on the Monitoring-Host doesn’t return the result you expect. Just fire up the Test-Mode and run the query again.
   

    
    

5. Now it’s almost done. Just install the service and start it.
   1. “NSClient++.exe” –install
   2. net start nsclientpp
      
      
6. That’s it, the Windows-Part is done 

So, now it’s time for the Linux-Tasks.

We need the check_nrpe Plugin. You can either install it with aptitude (aptitude install nagios-nrpe-plugin) or grap a copy of the NRPE source at: http://www.nagios.org/download/addons

Again, I’m a fan of compiling such stuff myself. So let’s do it.

1. Unpack the archive    =>    tar –xzf nrpe-2.12.tar.gz
2. Run the configure-command. Just make sure to include the “—enable-command-args” option    => ./configure –enable-command-args –enable-ssl
   Again, –enable-ssl isn’t necessary, but a recommendation. Futhermore maybe it’s necessary to add some other config-switches to fit your environment.
3. Compile the package    =>    make
4. It’s not necessary to install the package, we just the the check_nrpe binary from the ./src directory.
5. Copy the check_nrpe binary to your libexec dir of Nagios or Icinga    => cp src/check_nrpe /usr/local/icinga/libexec/

Last but not least, the Nagios/Icinga Config

First, we’ll create a new command for checking Performance Counters

1. Edit your commands.cfg (by default in /usr/local/icinga/etc/objects/commands.cfg)    =>    sudo vim /usr/local/icinga/etc/objects/commands.cfg
   
   
   
   Again, this is just a recommendation. But I prefer a “generic” command and put the detailed definition into services.
2. Now add a new service (by default in /usr/local/icinga/etc/objects/services.cfg)    => sudo vim /usr/local/icinga/etc/objects/services.cfg
   You must use double Backslashes for the Counters
   
   
3. How to get the name of a Performance Counter?

   Use the Windows Performance Monitor (Start -> Run -> perfmon) and add the counters you want to monitor. After that switch to the properties of your current Performance Monitor Session (Action -> Properties or Right Click to the Graphs -> Properties). At the Data-Tab you’ll find the right name. Just make sure to use double Backslashes in your Icinga/Nagios Config.
   
   

4. Save both files ( :wq ) , check the config and reload Icinga
   1. sudo /etc/init.d/icinga checkconfig
   2. sudo /etc/init.d/icinga reload
5. Look at the results of the check in the Web Interface (I’m sure you’re already running Icinga-Web, or not?
   

Some troubleshooting tips:

1. Before adding a service, run the check on the Linux command line.
   
2. Of you do not get the result you expect with the “remote run” (see above) try to run the check locally on the Windows Machine.
   1. Start NSClient++ in Test-Mode; You can do that while the service is running. You’ll get an error that no socket can be bind, but it’s ok    => “NSClient++.exe” /test
   2. Run the check without double Backslashes (they are just necessary for the remote execution)

      
      

       
       

       
       

Hope this post is helpful for you. If you miss something, or if some steps are not clearly enough just let me know.

Good luck and happy monitoring 

Have a look at http://speedtest.sperrgebiet.org. I’ve included a Speed Test (Bandwidth Test) on my sites. The main part of the Test is from http://www.brandonchecketts.com/open-source-speedtest - Fancy Speed Test. I’ve modified just the web page to modify so it fits my imagination. You can run the Download/Upload Test just by hitting start or if you don’t trust the measurement of the download speed (i had some troubles with it while testing it behind a proxy) you can also just download a simple file (with different file sizes of course). That was primarly done so so (and i too, of course) can also test it with wget or lynx.

The whole stuff is located on my Root-Server at Germany with an average available bandwidth of about 50MBit/s. So it should be enough for testing your DSL-Account

So here is the URL again: http://speedtest.sperrgebiet.org

Cheers
Hans

Based on my other script notify-by-nabaztag.php (see this post)  i’ve wrote another little PHP-Script which gets the Nagios/Icinga Status from the nagiostats/icingastats utility and use my notify-by-nabaztag.php to send out a status message. Here it is: status2nabaztag.php

There are just a few steps to get up and running:

1. Grap my notify-by-nabaztag.php and the status2nabaztag.php scripts

wget http://www.sperrgebiet.org/wp-content/uploads/2010/02/notify-by-nabaztag.txt -O /usr/local/icinga/libexec/notify-by-nabaztag.php

wget http://www.sperrgebiet.org/wp-content/uploads/2010/02/status2nabaztag.txt -O /usr/local/icinga/bin/status2nabaztag.php

2. Change, if required, paths to the binaries. Specially $stats & $php

3. Test it

php /usr/local/icinga/bin/status2nabaztag.php

4. Assuming everything worked as expected you can add an entry to your crontab to regulary executes the script. I know, it would be a nicer to use the Nagios/Icinga timeperiod-definitions, but the crontab-entry is easier

vim /etc/crontab

0 6-23 * * * root /usr/bin/php /usr/local/icinga/bin/status2nabaztag.php

This cron entry will executes the script every day between 6am and 11pm.

It’s just a short post, but i think the script should be self explaining too. Furthermore it’s quite late/early, so i’ll try to get some sleep because i have to get up in 3hours

Hope this script is useful too. Please let me know if you have any troubles to get it running.

Remember: In god we trust, the rest we monitor

So I’ve wrote my own notification script in PHP. You can download it here: notify-by-nabaztag.php

You can watch a video demonstrating it in action here in the following embedded Windows Media Player or at YouTube

The script is quite simple. It’s need two arguments. The first one is the message for the TTL (text-to-speech) and the second one is the “notification type”. The notification type is either the service or host state (OK, WARNING, CRITICAL, UNKNOWN, UP, DOWN, UNREACHABLE).

Depending on the notification type the bunny is flashing in a different color and moves it’s ears to another position:

You can configure the voice which should be used inside the script. I propose to use a US/UK one because the states are in English too. I think the script should be self-explaining. If not, just leave an comment.

When you already have Nagios/Icinga up and running you should also know how to add an new notification command. Otherwise here are the basic steps (assuming you are running Icinga within /usr/local/icinga):

1. We need php-cli installed so we can run the script on the CLI. Depending on your distro run on of the following commands

 aptitude install php-cli
or
yum install php-cli

2. Download the script to your libexec-Directory:

wget http://www.sperrgebiet.org/wp-content/uploads/2010/02/notify-by-nabaztag.txt -O /usr/local/icinga/libexec/notify-by-nabaztag.php

3. Add a host and service notification command. If you want a more detailed output just add it to the right position. You’ll find all available Macros at http://nagios.sourceforge.net/docs/3_0/macrolist.html

vim /usr/local/icinga/etc/objects/commands.cfg

# ‘notify-service-by-nabaztag’ command
define command{
command_name notify-service-by-nabaztag
command_line /usr/bin/php $USER1$/notify-by-nabaztag.php “Monitoring Notification: $NOTIFICATIONTYPE$ on $HOSTNAME$ (Hostalias is $HOSTALIAS$) with Service: $SERVICEDESC$. Current servicestate is $SERVICESTATE$” $SERVICESTATE$
}

# ‘notify-host-by-nabaztag’ command
define command{
command_name notify-host-by-nabaztag
command_line /usr/bin/php $USER1$/notify-by-nabaztag.php “Monitoring Notification: $NOTIFICATIONTYPE$ on $HOSTNAME$ (Hostalias is $HOSTALIAS$). Hoststate is $HOSTSTATE$” $HOSTSTATE$
}

4. I’ve created a new time period, because I don’t want that my bunny is talking to me during the night

vim /usr/local/icinga/etc/objects/timeperiods.cfg

# ‘nabazhours’

define timeperiod{
timeperiod_name nabazhours
alias Where my nabaztag is active
monday 06:00-23:00
tuesday 06:00-23:00
wednesday 06:00-23:00
thursday 06:00-23:00
friday 06:00-23:00
saturday 08:00-23:00
sunday 08:00-23:00
}

5. After that a new contact is created which use the above added notification commands and the right time period

vim /usr/local/icinga/etc/objects/contacts.cfg

define contact{
contact_name nabaztag
use generic-contact
alias My Bunny
service_notification_commands notify-service-by-nabaztag
host_notification_commands notify-host-by-nabaztag
service_notification_period nabazhours
host_notification_period nabazhours
}

6. We should have enough time to run a config-check

/usr/local/icinga/bin/icinga -v /usr/local/icinga/etc/icinga.cfg

7. When no errors or warnings appear reload Nagios/Icinga and wait till problem occur

/etc/init.d/icinga reload

Hope everything works as expected and you’ll find this script useful. Have fun with Nagios/Icinga and your Bunny. J

1. ssh-keygen
2. No PassPhrase (so automatic logon works)
3. Default filename and path is ok
4. cat ~/.ssh/id_rsa.pub
5. Copy content of id_rsa.pub

Host2:

1. Create ~/.ssh
2. Create ~/.ssh/authorized_keys
3. Paste content of clipboard into authorized_keys

Both steps vice vera

At the first logon a warning appears that the hostkey is added

to know_hosts. Yes to proceed.

That’s it

egrep -l NEEDLE * | xargs rm

This command will find all files with NEEDLE in it, pipes the filename (that’s because we need the parameter L) to xargs which then use the STDIN (our filename) and put’s it to rm.

Just play around with it the possible parameters. It would save you a lot of time.