Just a note that I have the same problem you describe.  Nagios 2.10 runs
perfectly, Nagios 3.0 or 3.0.1 run with 100% cpu on both both Intel and PPC
hardware in either OSX 10.4 or 10.5.

Any help with this would be appreciated.

Rob Yeo
University of Utah
College of Fine Arts

On 5/13/08 7:21 AM, "Rudolf van der Leeden" <[EMAIL PROTECTED]>
wrote:

> Hi,
> 
> I just built and installed Nagios 3.0.1 on Mac OSX 10.5 / Intel.
> 
> In order to verify the installation I just put together a set of tiny
> configfiles with just 1 node and 1 service.
> Nagios works fine so far with one exeception:  The nagios process
> with 2 threads is busy all the time
> (around 100% CPU).
> In nagios.cfg:   sleep_time=10 (break for 10s if idle).
> 
> Any ideas or explanations? Am I doing something wrong?
> 
> Best regards,
> Rudolf van der Leeden
> Logic United GmbH, Germany
> 
> PS. I've seen the same behaviour on OSX 10.4 with Nagios 3.0
>          Nagios 2.9 is OK and runs as expected.
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Nagios-users mailing list
> [email protected]
> 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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
[email protected]
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

Reply via email to