Hello list,
I am currently using our Nagios 3.5.0 server to monitor our Asterisk servers.
Our monitored services include SIP peers, like, to see if a certain peer is
alive and well through Nagios, using NRPE. However, this only works for a local
peer.
Is there any way for me to monitor remote
There are multiple ways to check you can use
check_procs -c 1: -w 3: -C pocess name
or
check_tcp -H $HOSTADDRESS -p portno
On Mon, Sep 2, 2013 at 5:20 PM, Paul Simons paul.sim...@onair.aero wrote:
Hello
Has anyone developed a check to confirm that Ziproxy (useful compression
proxy) is
To follow up on my own email. It looks like this is not just the upgrade. I
moved my 3.2.1 binary back in, and it still happens.
And I've found that it's not limited to the notification commands:
[1378314473] SERVICE ALERT: Server86;Server86 - Ping;UNKNOWN;SOFT;1;check_ping:
Invalid
Greetings,
It seems during a recent upgrade, my notifications broke! Well, I did digging
and found notification themselves are working, but the macro variables are
completely botched.
I took notify-by-email, and changed it to this:
/usr/bin/printf \%b\ \Notification Type: $NOTIFICATIONTYPE$
Jason,
Looking at your notify-by-email definition, there are a lot of escape
sequences ( \ ). I think that's what's messing you up. My
notify-service-by-email definition is shown below. Start with that and
tweak it to your taste.
# 'notify-service-by-email' command definition
define
Well, I’m not really sure what changed. But it was an issue with
illegal_macro_output_chars=\`\
It somehow got set incorrectly.
From: Jon Adcock [mailto:adco...@leoncountyfl.gov]
Sent: Wednesday, September 04, 2013 1:53 PM
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users]
It’s a bug in the version of lilac I am using. I finally traced it down. What
a mess!
I have to explicitly set it to \”`\”.
The next time changes are made to the ”Other” area, it gets written as just a
backslash.
From: Jason Gauthier [mailto:jgauth...@lastar.com]
Sent: Wednesday, September
I've been trying to sort out radius monitors and ran into a problem.
I've tried multiple check radius plugins (check_radius from plugin,
check_radius.pl, check_radius_ih/etc) but all of them fail. When
monitoring the logs on the radius host they all fail password checks
when I know for a fact
