<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.24"> <TITLE>RE : [Nagios-users] Re: [Nagios-devel] webinterface don't works with large number of hosts in Nagios 2.0 current cvs version</TITLE> </HEAD> <BODY> The test for strlen(input)>MAX_XODTEMPLATE_INPUT_BUFFER has been removed on 05/25/2005 from xodtemplate_add_object_property() in the CVS version. Maybe you could try the current CVS. > -----Original Message----- > From: nagios-users-admin@lists.sourceforge.net > [<A HREF="mailto:nagios-users-admin@lists.sourceforge.net">mailto:nagios-users-admin@lists.sourceforge.net</A>] On Behalf > Of Marcus Hildenbrand > Sent: Wednesday, July 13, 2005 1:19 PM > To: nagios-devel@lists.sourceforge.net; > nagios-users@lists.sourceforge.net > Subject: [Nagios-users] Re: [Nagios-devel] webinterface don't > works with large number of hosts in Nagios 2.0 current cvs version > > > Hi, > > the cause of this seems to be a too long list of services in > a servicegroup. My config includes something like this: > > - servicegroup definition: > define servicegroup{ > servicegroup_name filesystems > alias filesystems > members host1,filesystems > } > > - service template which includes also the above servicegroup > name define service{ > use generic-service > > name check_filesystems > service_description filesystems > normal_check_interval 15 > max_check_attempts 3 > servicegroups filesystems > register 0 > } > > - and for nearly every host something like this > define service{ > use check_filesystems > host_name hostxx > check_command check_nrpe!check_filesystems > normal_check_interval 15 > contact_groups GROUPX > } > > This means that the servicegroup includes nearly 4k services. > After doubling MAX_XODTEMPLATE_INPUT_BUFFER in > xdata/xodtemplate.h from 65535 to 131070 the webinterface works again. > > Maybe the size of this variable should be adjusted to > something higher. > > Regards > Marcus Hildenbrand > > > > Hi, > > > > in a test environment I try to monitor nearly 4.000 hosts. > Nagios core > > seems to run (checks and notifications are beeing executed) but the > > webinterface always says: > > > > Whoops! > > > > Error: Could not read host and service status information! .... > > .... > > > > The webinterface seems to think Nagios is not running. > > > > After reducing the number of hosts to 3925 the webinterface works > > again. > > So there seems to be a limitation somewhere in the cgi code. > > > > Any idea how to fix this? > > > > Thanks and Best Regards > > Marcus Hildenbrand > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > > from IBM. Find simple to follow Roadmaps, straightforward articles, > > informative Webcasts and more! Get everything you need to get up to > > speed, fast. <A HREF="http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click" TARGET="_blank">http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click</A> > > _______________________________________________ > > Nagios-devel mailing list > > Nagios-devel@lists.sourceforge.net > > <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-devel" TARGET="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-devel</A> > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' > webinar happening July 14 at 8am PDT/11am EDT. We invite you > to explore the latest in dual core and dual graphics > technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit > <A HREF="http://www.hp.com/go/dualwebinar" TARGET="_blank">http://www.hp.com/go/dualwebinar</A> > _______________________________________________ > Nagios-users mailing list > Nagios-users@lists.sourceforge.net > <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users" TARGET="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> > ::: Please include Nagios version, plugin version (-v) and OS > when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > </BODY> </HTML>