Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com

Login

Remember Me

check_vhosts

Rating
0 votes
Favoured:
0
Current Version
0.3
Last Release Date
2013-01-14
Compatible With
  • Nagios 3.x
Owner
License
GPL
Hits
47306
Files:
FileDescription
check_vhostsThe bash script check_vhosts

Help Support Ethan Galstad's New Project:

Help Support Ethan

A Message From The Founder...

As the founder of Nagios, I'm asking for your help in a cause that's dear to my heart.

I'm launching a new project to help better the world by providing the information, ideas, and inspiration that I believe can improve the lives of people everywhere.

I know you're busy managing networks, but I would appreciate it if you would consider liking my Facebook page and showing your support for the content and messages I produce by sharing them with your friends and family.

You can learn more about my project by visiting ethangalstad.me/nagios. Thank you for your time. I wish you all the best in your endeavors, whatever they may be.

- Ethan

When running a webserver with multiple vhosts, this plugin can test each vhost separately and report the status as a single service result.
The plugin uses a textfile as input with a single vhost per line, so when adding new vhosts or removing vhosts, the input file can be modified and the changes will take effect when the next check is run.

It has options to use an IPnumber instead of the vhost name to bypass routes caused by hostname resolution and it can use a different port (e.g. -p 8080 to check vhosts on a tomcat server)

Any kind of failure will result in CRITICAL, I couldn't find a reason to include WARN as state (let me know if you know any good reason).

v0.2 is more like the plugin guidelines suggest, though I haven't figured out yet how to skip creating temporary files.

new in v0.2 is the -d flag, which makes the script save the downloaded files in /tmp so you can check which strings to use for validation.

v0.3 fixes the use of wget's exit status and knows the difference between wget versions < 1.12 and >= 1.12

USAGE:

command definition:
define command {
command_name check_vhosts
command_line $USER1$/check_vhosts -H $ARG1$ -f $ARG2$ -v 1
}

in the service definition:

check_command check_vhosts!$HOSTADDRESS$!/path/to/vhostsfile

vhostsfile:
fqdn1URIString expected back
fqdn2URIString expected back for fqdn2
...