Hi Rama, Please do not hijack another user's thread - please start a new one. Additionally, this question would be best suited on the nagiosplug-help list (cc'd.) I think this is because you're giving the full path to the mysql_config binary. --with-mysql requires the installation folder as an argument, it will locate mysql_config itself.
e.g. ./configure --with-nagios-user=nagios --with-nagios-group=nagios --with-mysql=/usr Andy ADMIN AADHEE wrote: > Hello Friends, > I have a different problem with Nagios plugins.I am using current version > 1.4.12.The problem is I was trying to issue command > ./configure --with-nagios-user=nagios --with-nagios-group=nagios > --with-mysql=/usr/bin/mysql_config > It is skipping mysql_check compilation and giving warning like install mysql > client libraries. Even I installed Mysql client libraries problem remains > same. > > I am using 32bit Fedora8,mysql is 5.0.45,nagios3 plug-in 1.3.12. > And I have seen plugins directory there was mysql_check.c file exists. > Can any one help > > > Rama Krishna > Email : [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Andy > Shellam > Sent: Sunday, July 06, 2008 1:55 AM > To: mcalautt > Cc: nagios-user Mailinglist > Subject: Re: [Nagios-users] [Nagiosplug-help] plugin help > > Hi Mike, > > Firstly don't forget to CC in the list so others can benefit from answers. > Secondly, the config file you've given doesn't contain the definition > for the service "Current Http" which is what Nagios is complaining about. > > Therefore it's either defined in a different config file, or you haven't > given us the complete localhost.cfg (which would be better if you > attached it or only paste the relevant section of it.) > > Nagios isn't complaining that the "check_http" command isn't defined > (which as you've identified, it is) - it's complaining that a command > called "check_http -H 192.168.0.5" isn't defined, which means you've got > an incorrect syntax in the service definition for "Current Http" on > "localhost." > > I think you need to read up more about how to define services, and using > macros such as $HOSTADDRESS$ to your advantage. > > Andy > > mcalautt wrote: > >> ya the check_http entry was already in my commands.cfg by default I >> assume ? >> >> grep http commands.cfg >> # 'check_http' command definition >> command_name check_http >> command_line $USER1$/check_http -H $HOSTADDRESS$ >> >> the check_http plugin was not in the plugins directory with the >> standard install. >> btw, i did this with YUM in fedora. >> then I install the base plugin pkg with YUM as well and that gave me >> the check_http script in the plugins >> dir. >> so when I didnt see it on the web gui I assumed I had to make an entry >> in the localhost.cfg >> I copied the check_load entry and made changes to use the check_http >> and thats when I get the error. >> >> I pasted the localhost.cfg below. >> >> >> >> >> > ############################################################################ > ### > >> # LOCALHOST.CFG - SAMPLE OBJECT CONFIG FILE FOR MONITORING THIS MACHINE >> # >> # Last Modified: 11-27-2006 >> # >> # NOTE: This config file is intended to servce as an *extremely* simple >> # example of how you can create your object configuration file(s). >> # >> >> > ############################################################################ > ### > >> >> >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # >> # TIME PERIODS >> # >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # This defines a timeperiod where all times are valid for checks, >> # notifications, etc. The classic "24x7" support nightmare. :-) >> >> define timeperiod{ >> timeperiod_name 24x7 >> alias 24 Hours A Day, 7 Days A Week >> sunday 00:00-24:00 >> monday 00:00-24:00 >> tuesday 00:00-24:00 >> wednesday 00:00-24:00 >> thursday 00:00-24:00 >> friday 00:00-24:00 >> saturday 00:00-24:00 >> } >> >> >> # 'workhours' timeperiod definition >> define timeperiod{ >> timeperiod_name workhours >> alias "Normal" Working Hours >> monday 09:00-17:00 >> tuesday 09:00-17:00 >> wednesday 09:00-17:00 >> thursday 09:00-17:00 >> friday 09:00-17:00 >> } >> >> >> # 'nonworkhours' timeperiod definition >> define timeperiod{ >> timeperiod_name nonworkhours >> alias Non-Work Hours >> sunday 00:00-24:00 >> monday 00:00-09:00,17:00-24:00 >> tuesday 00:00-09:00,17:00-24:00 >> wednesday 00:00-09:00,17:00-24:00 >> thursday 00:00-09:00,17:00-24:00 >> friday 00:00-09:00,17:00-24:00 >> saturday 00:00-24:00 >> } >> >> >> # 'none' timeperiod definition >> define timeperiod{ >> timeperiod_name none >> alias No Time Is A Good Time >> } >> >> >> >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # >> # COMMANDS >> # >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # NOTE: Sample command definitions can now be found in the sample >> commands.cfg >> # file >> >> >> >> >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # >> # CONTACTS >> # >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # In this simple config file, a single contact will receive all alerts. >> # This assumes that you have an account (or email alias) called >> # "nagios-admin" on the local host. >> >> define contact{ >> contact_name nagios-admin >> alias Nagios Admin >> service_notification_period 24x7 >> host_notification_period 24x7 >> service_notification_options w,u,c,r >> host_notification_options d,r >> service_notification_commands notify-by-email >> host_notification_commands host-notify-by-email >> email [EMAIL PROTECTED] >> } >> >> >> >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # >> # CONTACT GROUPS >> # >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # We only have one contact in this simple configuration file, so there is >> # no need to create more than one contact group. >> >> define contactgroup{ >> contactgroup_name admins >> alias Nagios Administrators >> members nagios-admin >> } >> >> >> >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # >> # HOSTS >> # >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # Generic host definition template - This is NOT a real host, just a >> template! >> >> define host{ >> name generic-host ; The name of >> this host template >> notifications_enabled 1 ; Host notifications >> are enabled >> event_handler_enabled 1 ; Host event handler >> is enabled >> flap_detection_enabled 1 ; Flap detection is >> enabled >> failure_prediction_enabled 1 ; Failure prediction >> is enabled >> process_perf_data 1 ; Process performance >> data >> retain_status_information 1 ; Retain status >> information across program restarts >> retain_nonstatus_information 1 ; Retain non-status >> information across program restarts >> notification_period 24x7 ; Send host notifications at any time >> register 0 ; DONT REGISTER THIS >> DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE! >> } >> >> >> # Linux host definition template - This is NOT a real host, just a >> template! >> >> define host{ >> name linux-server ; The name of this host template >> use generic-host ; This template inherits other values from the >> generic-host template >> check_period 24x7 ; By default, Linux hosts are checked round the >> clock >> max_check_attempts 10 ; Check each Linux host 10 times (max) >> check_command check-host-alive ; Default command to >> check Linux hosts >> notification_period workhours ; Linux admins hate to be woken up, so >> we only notify during the day >> ; Note that the notification_period variable is being overridden >> from >> ; the value that is inherited from the generic-host template! >> notification_interval 120 ; Resend notification every 2 hours >> notification_options d,u,r ; Only send notifications for specific >> host states >> contact_groups admins ; Notifications get sent to the admins by >> default >> register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, >> JUST A TEMPLATE! >> } >> >> >> # Since this is a simple configuration file, we only monitor one host >> - the >> # local host (this machine). >> >> define host{ >> use linux-server ; Name of host >> template to use >> ; This host definition will inherit all variables that are defined >> ; in (or inherited by) the linux-server host template definition. >> host_name localhost >> alias localhost >> address 127.0.0.1 >> } >> >> >> >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # >> # HOST GROUPS >> # >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # We only have one host in our simple config file, so there is no need to >> # create more than one hostgroup. >> >> define hostgroup{ >> hostgroup_name test >> alias Test Servers >> members localhost >> } >> >> >> >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # >> # SERVICES >> # >> >> > ############################################################################ > ### > >> > ############################################################################ > ### > >> # Generic service definition template - This is NOT a real service, >> just a template! >> >> define service{ >> name generic-service ; The 'name' >> of this service template >> active_checks_enabled 1 ; Active service >> checks are enabled >> passive_checks_enabled 1 ; Passive service >> checks are enabled/accepted >> parallelize_check 1 ; Active service >> checks should be parallelized (disabling this can lead to major >> performance problems) >> obsess_over_service 1 ; We should obsess >> over this service (if necessary) >> check_freshness 0 ; Default is to NOT >> check service 'freshness' >> notifications_enabled 1 ; Service >> notifications are enabled >> event_handler_enabled 1 ; Service event >> handler is enabled >> flap_detection_enabled 1 ; Flap detection is >> enabled >> failure_prediction_enabled 1 ; Failure prediction >> is enabled >> process_perf_data 1 ; Process performance >> data >> retain_status_information 1 ; Retain status >> information across program restarts >> retain_nonstatus_information 1 ; Retain non-status >> information across program restarts >> is_volatile 0 ; The service is not >> volatile >> register 0 ; DONT REGISTER THIS >> DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE! >> } >> >> >> # Local service definition template - This is NOT a real service, just >> a template! >> >> define service{ >> name local-service ; The name of this service template >> use generic-service ; Inherit default values from the >> generic-service definition >> check_period 24x7 ; The service can be >> checked at any time of the day >> max_check_attempts 4 ; Re-check the service up >> to 4 times in order to determine its final (hard) state >> normal_check_interval 5 ; Check the service every 5 >> minutes under normal conditions >> retry_check_interval 1 ; Re-check the service >> every minute until a hard state can be determined >> contact_groups admins ; Notifications get >> sent out to everyone in the 'admins' group >> notification_options w,u,c,r ; Send notifications about warning, >> unknown, critical, and recovery events >> notification_interval 60 ; Re-notify about service >> problems every hour >> notification_period 24x7 ; Notifications can be >> sent out at any time >> register 0 ; DONT REGISTER THIS >> DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE! >> } >> >> >> # Define a service to "ping" the local machine >> >> define service{ >> use local-service ; Name of >> service template to use >> host_name localhost >> service_description PING >> check_command check_ping!100.0,20%!500.0,60% >> } >> >> >> # Define a service to check the disk space of the root partition >> # on the local machine. Warning if < 20% free, critical if >> # < 10% free space on partition. >> >> define service{ >> use local-service ; Name of >> service template to use >> host_name localhost >> service_description Root Partition >> check_command check_local_disk!20%!10%!/ >> } >> >> >> >> # Define a service to check the number of currently logged in >> # users on the local machine. Warning if > 20 users, critical >> # if > 50 users. >> >> define service{ >> use local-service ; Name of >> service template to use >> host_name localhost >> service_description Current Users >> check_command check_local_users!20!50 >> } >> >> >> # Define a service to check the number of currently running procs >> # on the local machine. Warning if > 250 processes, critical if >> # > 400 users. >> >> define service{ >> use local-service ; Name of >> service template to use >> host_name localhost >> service_description Total Processes >> check_command check_local_procs!250!400!RSZDT >> } >> >> >> >> # Define a service to check the load on the local machine. >> >> define service{ >> use local-service ; Name of >> service template to use >> host_name localhost >> service_description Current Load >> check_command check_local_load!5.0,4.0,3.0!10.0,6.0,4.0 >> } >> >> >> >> THANKS >> MIKE >> >> ----- Original Message ----- From: "Andy Shellam" >> <[EMAIL PROTECTED]> >> To: "mcalautt" <[EMAIL PROTECTED]> >> Cc: <[EMAIL PROTECTED]> >> Sent: Friday, July 04, 2008 1:35 PM >> Subject: Re: [Nagiosplug-help] plugin help >> >> >> >>> Hi Mike, >>> >>> It looks Nagios is trying to find a command called "check_http -H >>> 192.168.0.5." >>> >>> What is your service definition for the "localhost" host (in >>> localhost.cfg) ? >>> The relevant line should be: >>> >>> service { >>> ... >>> check_command check_http >>> ... >>> } >>> >>> I'm guessing at the minute it says something like >>> >>> service { >>> ... >>> host localhost >>> ... >>> check_command check_http -H $HOSTADDRESS$ >>> ... >>> } >>> >>> which is incorrect. Your command definition looks fine. >>> >>> http://nagios.sourceforge.net/docs/3_0/objectdefinitions.html#service >>> http://nagios.sourceforge.net/docs/3_0/objectdefinitions.html#command >>> >>> Andy >>> >>> mcalautt wrote: >>> >>>> trying to implement the check_http plugin. >>>> when ever I add the entry to the localhost.cfg and run a sanity >>>> check I get. >>>> Checking services... >>>> Error: Service check command 'check_http -H 192.168.0.5' specified >>>> in service 'Current Http' for host 'localhost' not defined anywhere! >>>> I cant find any docs on how to add the plugin. >>>> there is reference to it in commands.cfg but it is not displayed on >>>> the webpage under service details. >>>> everything else listed in >>>> pwd >>>> /etc/nagios >>>> grep check_http *|grep -vi sampl >>>> commands.cfg:# 'check_http' command definition >>>> commands.cfg: command_name check_http >>>> commands.cfg: command_line $USER1$/check_http -H >>>> $HOSTADDRESS$ >>>> thanks >>>> mike >>>> >>>> > ------------------------------------------------------------------------ > >>>> >>>> > ------------------------------------------------------------------------- > >>>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >>>> Studies have shown that voting for your favorite open source project, >>>> along with a healthy diet, reduces your potential for chronic lameness >>>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >>>> ------------------------------------------------------------------------ >>>> > > >>>> _______________________________________________ >>>> Nagiosplug-help mailing list >>>> [EMAIL PROTECTED] >>>> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help >>>> ::: Please include plugins version (-v) and OS when reporting any >>>> issue. ::: Messages without supporting info will risk being sent to >>>> /dev/null >>>> >>>> >> > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > 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 > > > ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ 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
