I Have configured serveral cgi file in /etc/nagios/
hosts.cfg
contactgroup.cfg
timeperiod.cfg
hostgroup.cfg
now when I uncomment these files from nagios.cfg. nagios server service not
starting. after comment these files its works fine. how many files I have to
make and uncomment for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/11/07 01:11 PM, Jeff Shumard - DefenseWeb Technologies wrote:
> We have our monitoring configured and everything is working great
> checking all our windows servers through a single windows server running
> nrpe_nt. The problem we are having is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/10/07 01:10 PM, Alloo, Vincent wrote:
> Hello,
>
>
>
> I have an issue with NSCA on Solaris 10 x86 machine (SunOS svxnagios02
> 5.10 Generic_120012-14 i86pc i386 i86pc):
>
>
>
> On a Linux RH4 machine, no issue:
>
> % printf "toto\t0\tco
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/11/07 12:55 PM, Andreas Ericsson wrote:
>
> That's not strictly true. Each check run by Nagios needs three fork()'s
> and two exec()'s. For your case, you can achieve exactly the same thing,
> but with 6 fork()'s and 4 exec()'s less by using
>
Thomas Guyot-Sionnest wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/11/07 11:48 AM, Andreas Ericsson wrote:
>> Thomas Guyot-Sionnest wrote:
>>> This gives the same result for up hosts, but takes 20 times longer on
>>> unreachable hosts:
>>>
>>> $ time ./check_icmp -H 1.1.1.1 -
Ok, I will send you all the information.
Do you know the hardware of the servers (I would like to compare it with
hardware of my servers)?
Currently I have:
1. ~15000 host checks (ping, every 15 min). Since 3.0 Nagios release all the
host chacks parallelized.
2. ~27000 service checks (15000 pin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/11/07 11:48 AM, Andreas Ericsson wrote:
> Thomas Guyot-Sionnest wrote:
>>
>> This gives the same result for up hosts, but takes 20 times longer on
>> unreachable hosts:
>>
>> $ time ./check_icmp -H 1.1.1.1 -w 300.00,80% -c 500.00,100% -p 1 -t 1
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/07 05:27 AM, Jacques FAN wrote:
> Thanks Thomas,
>
> If I understanding your answer, so I must install nagios plugin as I did
> for Windows computer?
There's no Nagios-plugins for Windows (maybe you were talking about
NRPE-NT, NSClient or NC
On Sunday 04 November 2007 17:40:59 Alexander Bespalov wrote:
> Thank you!
>
> I will try it.
OK. Could you send the results please?
> Should I change the 'max_check_result_reaper_time' paremeter?
I don't known. I play a lot with with nagios 2.x version, not for the 3.x.
This parameter is intr
Thomas Guyot-Sionnest wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/11/07 05:03 AM, Andreas Ericsson wrote:
>> Thomas Guyot-Sionnest wrote:
>>> Something that can help as well is having the host check return as fast
>>> as possible.
>> If that's what you're after ...
>
> It h
Thank you!
I will try it.
Should I change the 'max_check_result_reaper_time' paremeter?
How can I calculate the values for my installation (it is insufficient
information in the documentation)?
What is the largest Nagios installation do you know?
--
Alexander Bespalov
Golden Telecom, Moscow, R
On Thursday 01 November 2007 08:20:31 Alexander Bespalov wrote:
> Hi,
Hi,
> We are trying to use Nagios to monitor (just ping) very large network
> (15000 hosts).
[...]
> I think the the main problem is in the check_result_reaper_frequency=10 and
> max_check_result_reaper_time=60 parameters in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/07 05:03 AM, Andreas Ericsson wrote:
> Thomas Guyot-Sionnest wrote:
>>
>> Something that can help as well is having the host check return as fast
>> as possible.
>
> If that's what you're after ...
It helped a lot reducing the check latency
13 matches
Mail list logo