Servicegroup limit?

Andreas Ericsson ae at op5.se
Sun Jan 23 20:51:42 CET 2005


Jay Janssen wrote:
> Hi, I seem to have hit some kind of limit in my nagios config.  I am
> defining a generic service escalation model for all of my services
> divided into two servicegruops, services-priority-high and
> services-priority-low.  This seems to work well, until I reach some
> limit on the number of services I have in my services-priority-high
> group (~1300 services).  I have narrowed it down if I add one more
> service (which actually results in about 150 being added to the
> service group, because that service is on a ~150 hosts), I experience
> the following when I load my web interface:
> 
>> Whoops!
>> 
>> Error: Could not read object configuration data!
> 
> 
> When I back out that one service from the service group, the error
> goes away.  Throughout all of this my nagios daemon restarts happily
> without any errors (nor any errors from nagios -v) Does anyone have
> any thoughts/experiences with this?
> 

It seems like you're reaching the max line number. What happens then is 
that it will read the part that will fit in the buffer, find the keyword 
and its corresponding value and then continue to read the same line, but 
thinking it's the next line.

> 
> Jay Janssen
> 

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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





More information about the Users mailing list