[blockquote]Plugins are not located in Nagios-plugins. This fodler does not exist.
Plugins show in /usr/local/nagios/libexec[/blockquote]Thats more normal... I'm not sure what build process put's them into nagios-plugins but it's not current manual build... maybe installing via YUM or APT or something does that... not to worry anyway.
[blockquote]Is this a problem. I cannot run check_http when i go into the libexec folder. get command not found error.
I get a response when i put ./ before check_http. Is this right?[/blockquote]Yes, if you run a command in the libexec directory from the CLI in the libexec directory you'd need to precede it with ./
[blockquote]Also cannot find a http.cfg file. Any plugin details seem to be under a command.cfg.[/blockquote]Yes, that's the one you want. You need to add the basic auth parameter in your check_http command object - this is the -a switch as can bee seen in the plugin help:
[root@localhost libexec]# ./check_http --help
check_http v1861 (nagios-plugins 1.4.11)
Copyright (c) 1999 Ethan Galstad <email@example.com>
Copyright (c) 1999-2006 Nagios Plugin Development Team
This plugin tests the HTTP service on the specified host. It can test
normal (http) and secure (https) servers, follow redirects, search for
strings and regular expressions, check connection times, and report on
certificate expiration times.
Usage: check_http -H <vhost> | -I <IP-address> -u <uri>] -p <port>]
-w <warn time>] -c <critical time>] -t <timeout>] -L]
-a auth] -f <ok | warn | critcal | follow>] -e <expect>]
-s string] -l] -r <regex> | -R <case-insensitive regex>] -P string]
-m <min_pg_size>:<max_pg_size>] -4|-6] -N] -M <age>] -A string]
-k string] -S] -C <age>] -T <content-type>]
NOTE: One or both of -H and -I must be specified
Username:password on sites with basic authentication...
[blockquote]Have i totally messed up the installation of the plugins?? [/blockquote]Nope
Shout if you want another clue