> -----Original Message----- > From: Jerad Riggin [mailto:[EMAIL PROTECTED] > Sent: Friday, June 22, 2007 10:00 AM > To: Marc Powell > Cc: nagios-users@lists.sourceforge.net > Subject: Re: [Nagios-users] Nagios HTTP monitoring {Disarmed} {Fraud?} > > If I change the hosts.cfg from the IP of the server (10.10.10.7) to the > URL I'm specifying in services.cfg, it works fine. The default site for > 10.10.10.7 is a CRM site which requires basic auth. So even though i'm > specifying a URL in services.cfg, it looks like it's be overridden by the > hosts.cfg so it can't auth. What is the point of the -H switch in > services.cfg if it always uses the IP for the host in hosts.cfg? I tried > that format (-a admin:password) at the end of the check in services.cfg > but it still failed with unauthorized.
It's looking more and more clear that your command{} definition doesn't do what you think it does. You don't usually specify switches such as -H and -a as part of the service definition. Perhaps you should post the host, service and relevant command definitions for us to look at. I know for a fact that check_http can and will work the way you want if properly called. -- Marc ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null