connection refused by host

[yu-ting_liu at agilent.com]

Thanks! 

After checking the configuration I found they are only a normal active service check instead of passive check. (It only uses passive as the command name.)

After I submit an immediate service check request it's recovered.

Regards!
Yu Ting

-----Original Message-----
From: Marc Powell [mailto:marc at ena.com]
Sent: Tuesday, April 13, 2004 9:26 PM
To: LIU,YU-TING (A-Singapore,ex1); peter.gutmann at db.com
Cc: nagios-users at lists.sourceforge.net;
nagios-users-admin at lists.sourceforge.net
Subject: RE: [Nagios-users] connection refused by host


yu-ting_liu at agilent.com <mailto:yu-ting_liu at agilent.com> wrote:
> Thanks! I need to assign the monitor server's IP address to
> allow_hosts in nrpe.cfg on client. 
> 
> Now the passive check LOGS/TRAPS are still pending with complain
> "service check is not scheduled for execution". 
> 
> So where is the configuration so I can start the passive check? I
> have check the netsaint.cfg, nsca.cfg, send_nsca.cfg...... 

A passive check means that nagios does nothing (hence passive as opposed
to active). It simply waits for the results to be submitted by some
external application. This is most often used with Distributed
Monitoring and the documentation for that and SNMP Trap integration
should clear up the different roles and processes for you. Since we
don't know what your LOGS/TRAPS services are (i.e. service and command
definitions and how you're implementing them), it's hard to be more
specific than that.

--
Marc


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_id66&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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