I want to find out if I can simply change the check_command for imap, pop, and
smtp to verify 587, 995, and 993 respectively
on the nagios server, in commands.cfg, I thought perhaps I could just change
this:
# 'check_pop' command definition
define command{
command_namecheck_pop
In top, does it show the same load values? The status of your memory
shouldn't cause the nagios plugin to report high cpu. What does the
uptime command say? Try running the check_load script by hand on that
host and verify it returns the same results.
Dan
From: Marc Powell [mailto:li...
On Mon, Dec 6, 2010 at 1:50 PM, Kaplan, Andrew H. wrote:
> Hi there --
>
> We are running Nagios 3.1.2 server, and the client that is the subject of
> this e-mail is running version 2.6 of the nrpe client.
>
> The check_load plugin, version 1.4, is indicating the past three readings
> are the fol
> -Original Message-
> From: Andreas Ericsson [mailto:a...@op5.se]
> Sent: Monday, December 06, 2010 6:06 AM
> To: Nagios Users List
> Cc: Frost, Mark {PBC}
> Subject: Re: [Nagios-users] high latency
>
> On 12/03/2010 08:14 PM, Frost, Mark {PBC} wrote:
> >
> > I too struggle with them a
You might want to check:
netstat -nap |grep 5667
That will show you what's actually listening on that port, if anything.
That's usually oen big reason xinetd couldn't start up. Like maybe you
have an RC script starting up NSCA outside of xinetd.
Dan
From: Rikard Dahlberg [mailto:r
Hi there --
We are running Nagios 3.1.2 server, and the client that is the subject of this
e-mail is running version 2.6 of the nrpe client.
The check_load plugin, version 1.4, is indicating the past three readings are
the following:
load average: 71.00, 71.00, 70.95 CRITICAL
The critical thresh
Hello
I was wondering if there was a straight-forward way to alert based on an
average of past data plus a current perfdata entry. I understand I'm not
explaining it very well that way, so here is the real-world example I am
working with -
I am polling a set of machines via SNMP for CPU load e
Hi Rikard,
I assume you have checked the path and rights to all files.
What seems to be wrong is your 'server_args' parameter.
server_args = -c /etc/nsca.cfg .inetd
The option 'inetd' must be added via '--' and not '.'.
server_args = -c /etc/nsca.cfg --inetd
I think that should do the
Hey daniel!
Wow, this really showed my error i think. I cant connect either on
localhost:5667 nor from the server via telnet 5667...
Could i ask you if you could walk me through how to troubleshoot this? That
would really make my day :)
yes, i use xinetd
this is the config file :
# descriptio
Hi Rikard,
is your nsca daemon running (on your nagios host?). You can check the
process list via 'ps aux | grep nsca'. Furthermore you should try to
connect to port 5667 (from localhost and/or your windows server):
telnet localhost 5667. If you get connected you should verify your
network setup (
Rikard
From first glance you may have several factors that may contribute to
the issue you are having :
1) you may not have the nsca deamon running on the nagios server , to
receive the sent data from the submitting server - to solve that look at
the documentation of nsca and see about sett
Hello
I'm just starting with nagios and im trying to learn everything at once.
At this moment im trying to get a remote windows 2008 server to be monitored,
its on a different network so i've decided to use NSCA to monitor it via
passive checks.
However I get an error message at the remote serv
On 12/03/2010 08:14 PM, Frost, Mark {PBC} wrote:
>
> Can the use of dependencies also be the cause of increased latencies?
>
If they're very deep, it's possible. Otherwise it really shouldn't matter
all that much. It will ofcourse add *some* load, but it shouldn't be enough
to cause latency.
>
On 12/03/2010 07:59 PM, Daniel Wittenberg wrote:
> It appears that nagios spawns lots and lots of new procs for all the
> various tasks it does, check results and such. I was curious, wouldn't
> a model more like Apache work better? Something like, a queue for work,
> and have worker processes gr
14 matches
Mail list logo
