[Nagios-users] Question on check_mysql_query

2013-02-22 Thread Heeres, Ken
I have a query that says it returns 0. and have a warning value of 2:6 and 
critical value of 7 and am getting a warning.

This is from the debug file:

[1361472169.305131] [2048.1] [pid=2302]  BEGIN MACRO PROCESSING ***
[1361472169.305133] [2048.1] [pid=2302] Processing: '$USER1$/check_mysql_query 
--hostname=$ARG1$ --port
=$ARG2$ --database=$ARG3$ --username=$ARG4$ --password=$ARG5$ --warning=$ARG6$ 
--critical=$ARG7$ --quer
y=$ARG8$'
[1361472169.305154] [2048.1] [pid=2302]   Done.  Final output: 
'/export/nagios/libexec/check_mysql_quer
y --hostname=sd-mysql --port=3308 --database=it_administration 
--username=ituser --password=## -
-warning=2:6 --critical=7 --query="select 
format(datediff(current_timestamp,UPDATE_TIME),0) from inform
ation_schema.tables where TABLE_SCHEMA = 'it_administration' and TABLE_NAME = 
'SD_AD_USERS'"'
[1361472169.305157] [2048.1] [pid=2302]  END MACRO PROCESSING *

This is from the status:
QUERY WARNING: 'select format(datediff(current_timestamp,UPDATE_TIME),0) from 
information_schema.tables where TABLE_SCHEMA = 'it_administration' and 
TABLE_NAME = 'SD_AD_USERS'' returned 0.00

What am I doing wrong?


Thanks,

Ken

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb___
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

Re: [Nagios-users] Help --- email notification problem

2013-02-22 Thread Matsushita, Nobuo
James,

Thank you for your reply!!!

Just before I received your email, I noticed that I missed one required 
directive was missing from my new added object. After I added it, the behavior 
of notification was changed.

After I read your email, I decided to check my all configurations. After that I 
found many required directives were missing from my configurations. After I 
fixed all missing required directives, it is now working great!
Thank you for your advice!

Unfortunately,  "nagios -v " does not check all required directives.

Nobuo

From: James Osbourn [mailto:james.osbo...@citrix.com]
Sent: Wednesday, February 20, 2013 1:58 AM
To: Nagios Users List; Matsushita, Nobuo
Subject: RE: Help --- email notification problem

It would really be helpful to see the configs, at least the person and group 
definitions to determine any issues.  The information that you have provided 
does not given enough details to determine any inheritance from templates.

It should then be possible to see where the final service is actually going to 
email to.

Cheers

James

From: Matsushita, Nobuo [mailto:nobuo.matsush...@childrenscolorado.org]
Sent: 19 February 2013 19:04
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Help --- email notification problem

Hi,

I am using nagios 3.4.4. and RedHat Enterprise v 6.3. And I compiled from the 
source.

I am experiencing strange email notification problems. I have been using nagios 
since 3.2, but I didn't notice this problem until recently. The problem is that 
not only correct contact person gets the notification by email, but also some 
other group people gets the same notification. Depending on which directive 
use, different group gets the notification:

In the template file(service_templates.cfg),

If I use:contacts  personA-email

Then notification goes to personA and group D ( personA is not in the 
Group D)

But If I usecontact_groupstest-C
And in the service file, I put the following directive:
contacts  personA-email

Then the notification goes to person A and Group E ( personA  is not in 
the Group E)

Am I doing wrong ? Does anybody have similar experience?
Since I am subscribing this mailing list using digest mode,  I will be 
appreciated if you can send me a copy to my address.

Thanks in advance

Nobuo

Then the notification goes to






CONFIDENTIALITY NOTICE:  This e-mail, including any attachments, is for the 
sole use of the intended recipient and may contain confidential and privileged 
information.  If you are not an intended recipient, or the person responsible 
for delivering this message to an intended recipient, you are hereby notified 
that reading, copying, using or distributing this message is prohibited. If you 
are not an intended recipient, please contact the sender by reply email and 
destroy all copies of the original message from your computer system.

--
CONFIDENTIALITY NOTICE:  This e-mail, including any attachments, is for the 
sole use of the intended recipient and may contain confidential and privileged 
information.  If you are not an intended recipient, or the person responsible 
for delivering this message to an intended recipient, you are hereby notified 
that reading, copying, using or distributing this message is prohibited. If you 
are not an intended recipient, please contact the sender by reply email and 
destroy all copies of the original message from your computer system.

--
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb___
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

Re: [Nagios-users] Problem sending passive results using NSCA with multi-line output

2013-02-22 Thread Holger Weiß
*  [2013-02-22 09:31]:
> You can't [transmit multiline plugin output] with nsca.

You can, see my earlier responses in this thread:

http://article.gmane.org/gmane.network.nagios.user/74959

Holger

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
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


Re: [Nagios-users] Problem sending passive results using NSCA with multi-line output

2013-02-22 Thread diego.roc...@gmail.com
You can't with nsca. how about using nrpe? You would still have the scripts
running on the monitored system. If you want to stick with passive checks
(as far as you told us, there is no reason) there's a nsca alternative that
use cgi and support multi line.
Il giorno 13/feb/2013 19:09, "Tech Support"  ha
scritto:

> All;
>
> I have a bunch of ( PERL ) plugins that are run passively out of CRON
> with the results sent to the Nagios monitoring host using NSCA. Most of
> them work great, and they return results on dozens of services. I’m doing
> it this way because instead of running dozens of plugins actively, I can
> run one plugin passively. The problem is I have a few that are choking when
> the output contains multi-line output, and I’m not sure how to get around
> that. Basically, my scripts look something like this:
>
> ** **
>
> foreach my $service ( @services ) {
>
> 
>
> $nsca_cmd .= "$nscahost\t$service\t$code\t$output";
>
> };
>
> my $retval = `$system /bin/echo -e "$nsca_cmd" | $nscaprog -H $nagioshost
> -c $nscacfg`;
>
> ** **
>
> Like I said, Nagios is choking when the output contains multi-line output.
> Does anyone have any insight at all on how I can get around this? Any help
> at all would be greatly appreciated.
>
> Thanks;
>
> John
>
> Tech Support
>
> Technical Support
>
> VoIP Business Solutions
>
> 240-215-3479, ext. 305
>
> supp...@voipbusiness.us 
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
>
> --
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
> ___
> 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
>
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb___
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

Re: [Nagios-users] Define Multiple Event Handlers

2013-02-22 Thread Andreas Ericsson
On 02/21/2013 09:16 PM, Travis Runyard wrote:
> I'm trying to define multiple event handlers for a service but am getting
> the error during preflight check:
> Error: Event handler command 'update-nagex,reset-proc' specified in service
> 
> I've tried two different ways to define it in the service:
> 
> event_handler  update-nagex,reset-proc
> 
> and
> 
> event_handler update-nagex
> event_handler reset-proc
> 
> When I define them on separate lines, Nagios seems to only pick up the last
> event_handler defined which is reset-proc
> 
> Any ideas?

Create a wrapper script that runs both handlers with their proper
arguments.

-- 
Andreas Ericsson   andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
___
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