Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #187] servicegroup limit #87

Closed
icinga-migration opened this issue Nov 18, 2009 · 5 comments
Closed

[dev.icinga.com #187] servicegroup limit #87

icinga-migration opened this issue Nov 18, 2009 · 5 comments

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/187

Created by sz0wxc on 2009-11-18 20:27:04 +00:00

Assignee: (none)
Status: Rejected (closed on 2010-01-31 20:05:53 +00:00)
Target Version: (none)
Last Update: 2010-02-03 08:27:56 +00:00 (in Redmine)


It seems icinga will only allow me to have x amount of services defined in a service group. Once I reach x the plugin returns a Code 127.
Below is my config. in order to make things work all I have to do is comment out the service group definition and things start working.

I want to say that x was 3265 have to double check.

On that flip side I cannot get nagios to do more than 1200 services in a service group and on Nagios a hostgoup of 7661 causes the code 127 while dropping the group down 500 clears the 127.

Are there limit to number of services and host in a group? If so what is the magic number and why?

define command{
command_name sysUpTime-test
command_line /usr/local/icinga/libexec/check_snmp -C $_HOSTCOMMUNITY_STRING$ -P 1 -H $HOSTADDRESS$ -o .1.3.6.1.2.1.1.3.0

}
define service{
use WAP-svc-T ; template
hostgroup_name HW.Foundry.IP-250
# servicegroups system.sysUpTime.IP250
service_description system.sysUpTime
normal_check_interval 60 ; when in normal state, check every n minutes
check_command sysUpTime-test
notes .iso.org.dod.internet.mgmt.mib-2.system.sysUpTime
}
~

@icinga-migration
Copy link
Author

Updated by Meier on 2009-12-24 15:22:23 +00:00

I had a look on the code and the only obvious thing that could go wrong here is some malloc failure. Is this a 32bit system? How big is the process?

@icinga-migration
Copy link
Author

Updated by Meier on 2010-01-04 22:57:47 +00:00

  • Due Date set to 2010
  • Category set to Other
  • Status changed from New to Feedback
  • Priority changed from Normal to Low

Ok I did a couple of tests with a servicegroup of 4000 services. I can not see any Problems. Also the desrciption is somewhat unclear first you say problems occur if you have more then 3265 services in a group later you say you cannot put more then 1200 services in a service group. And to confuse some more you talk about hostgroups. So please give more precise details what the problem is and how to reproduce it.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2010-01-31 20:05:53 +00:00

  • Status changed from Feedback to Rejected

i don't really get the problem. plugins, nagios, icinga, configs - what exactly is wrong?

@icinga-migration
Copy link
Author

Updated by Meier on 2010-01-31 20:33:25 +00:00

I was about to close that one to. The report is not clear on what actually is wrong, tests are ok and no further feedback.

@icinga-migration
Copy link
Author

Updated by hbaecker on 2010-02-03 08:27:56 +00:00

Just a note:

Host||Servicegroups are just configuration items without big function at all, except inheritance or the view side like CGIs or other Webstuff.

In no-way that configurationgroups are doing anything with executing checks.

The mention error like 127 xxx (possibly "Plugin may be missing") results after a "reload" and inpropper permissions on ressource.cfg which may not be readably by icinga user.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant