Hi Andrew,
It depends on your firewall configuration on the Nagios server - but
yes, the Nagios server will an outbound rule to allow traffic to
destination port 5666 on your nrpe client, and also an inbound rule to
allow traffic from source port 5666 on your nrpe client.
Your client will need
On 12/29/06, John Giaccotto <[EMAIL PROTECTED]> wrote:
Has anyone evaluated either GroundWork Monitor Open Source or GroundWork
Monitor Professional?
If you want an easy way to evaluate Groundwork Monitor Open Source, I would
suggest using Rich Trezza's excellent VMWare appliance from
http:/
I configured the ip tables on both the nagios server and the nrpe client to
allow all inbound and outbound traffic. Additionally, I made sure the
/etc/services file on both systems had port 5666 open to tcp and udp traffic.
I was able to telnet to port 5666 on the nrpe client, but I was still get
Hi!
Try to "su" to the user nagios is running under and try the command with
that user. Seems to me, u got premission problems
Regards,
D.
Kaplan, Andrew H. pravi:
> I configured the ip tables on both the nagios server and the nrpe client to
> allow all inbound and outbound traffic. Additi
Kaplan, Andrew H. wrote:
> I configured the ip tables on both the nagios server and the nrpe client to
> allow all inbound and outbound traffic. Additionally, I made sure the
> /etc/services file on both systems had port 5666 open to tcp and udp traffic.
>
> I was able to telnet to port 5666 on th
The Nagios and NRPE users on the server are set to nologin. These are the
packages that came bundled with operating system. How can I get around that?
-Original Message-
From: David Gerbec [mailto:[EMAIL PROTECTED]
Sent: Friday, December 29, 2006 8:53 AM
To: Kaplan, Andrew H.
Cc: Andy
Hi!
Kaplan, Andrew H. pravi:
> The Nagios and NRPE users on the server are set to nologin. These are the
> packages that came bundled with operating system. How can I get around that?
>
When posting problems, it's allways good to give away MORE info then
less :o).
I don't know which operating
I ran the chsh command to change the nologin shell for the nagios user to
/bin/bash, and also provided a password for the nagios account. After that,
I ran the check_nrpe command again from the command line, ie: manually, and was
able to get a response back from the nrpe client.
Listed below are
Hi!
Kaplan, Andrew H. pravi:
> I ran the chsh command to change the nologin shell for the nagios user to
> /bin/bash, and also provided a password for the nagios account. After that,
> I ran the check_nrpe command again from the command line, ie: manually, and
> was
> able to get a response bac
> If i understand correctly, u ran the plugin su'ed to the nagios user and
> the command completed successfully?
That is correct.
> If that's the case, then please check if the xinetd daemon is running
> and what the setting for nagios-nrpe are for xinetd.
As far as the client is concerned, nrp
Andrew,
Please don't forget to copy the list in to all your replies, so others
can either get more info to help you (I've been watching for a reply),
and to help other people with the same issues in the future when these
mails get archived for ever-more :P
Thanks
Andy.
David Gerbec wrote:
>
Hi!
Kaplan, Andrew H. pravi:
>> If i understand correctly, u ran the plugin su'ed to the nagios user and
>> the command completed successfully?
>
> That is correct.
>
>> If that's the case, then please check if the xinetd daemon is running
>> and what the setting for nagios-nrpe are for xinetd.
Just in case this e-mail did not get through previously. If it had, my apologies
for the repost.
From: Kaplan, Andrew H.
Sent: Fri 12/29/2006 9:45 AM
To: 'David Gerbec'
Cc: Andy Shellam (Mailing Lists); Nagios Users mailinglist
Subject: RE: [Nagios-users] Service
The settings that I have in nrpe.cfg file appear to be correct, but just in
case, I have included it in this e-mail.
If there are no other ideas, I'll have no choice but to fall back to version 1.x
of the client and server applications.
From: David Gerbec [ma
My apologies, I'm suffering from a 60-minute lag on SourceForge's
mailing list for some reason - I'd got 2 replies from David before this
so it looked like you hadn't copied the list in.
Sorry!
Now onto this e-mail...
> As far as the client is concerned, nrpe is not being run via xinetd, it is
also check out fruity: http://fruity.sourceforge.net/
this is another groundwork open source product.
Mike Conigliaro
ProActive Technologies
[EMAIL PROTECTED]
203.239.0440 ext:317
www.getproactivenow.com
John Giaccotto wrote:
> Hi,
>
>
>
> I am investigating alternatives to a current Nagios
Hello,
I have a lot of custom alarms that need to generate a lot of status
information. The way I deal with this is I generate an HTML file that
I place on the nagios server and the one line that I return as the
status is a link to this file.
It would be nice if this were generalized such that i
The initial error message that I was getting, both onscreen and from the
nagios.log file, was Service Check Timed out. As an experiment I reconfigured
the nrpe client and check_nrpe plugin to not use SSL by including the -n option
in both cases. The error message that I am now getting is NRPE: Unab
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of Elliot Finley
> Sent: Friday, December 29, 2006 10:01 AM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] Multi-line Status Information Idea
>
> Hello,
>
> I have a lo
In message <[EMAIL PROTECTED]>,
Elliot Finley writes:
>I have a lot of custom alarms that need to generate a lot of status
>information. The way I deal with this is I generate an HTML file that
>I place on the nagios server and the one line that I return as the
>status is a link to this file.
>
>
I am trying to compile NRPE 2.6 on a system running Fedora Core 5, but I am
running into issues.
Whenever I try to complete the make all command as either root, sudo user, or a
regular user, I get
and Error 1 message. The lines shown below are a sample of the output I am
seeing:
dso_dlfcn.c:
This seems as if it could be an error in the makefile, a missing library
on your system, or an incorrect path in your /etc/ld.so.conf file.
Try passing "LDFLAGS=-ldl" to the configure script - eg.
LDFLAGS="-ldl" ./configure --prefix=/usr/local/nagios
Or, find the "dl" library (find / -name libd
22 matches
Mail list logo
