search

nrmjba / nagioschecker

Automatically exported from code.google.com/p/nagioschecker
0 stars 0 forks source link

Problems with many hosts or services #30

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install Nagioschecker
2.
3.

What is the expected output? What do you see instead?
I´m expecting to see if there is a problem or not. Instead I never get any
result. The weel keeps on spinning forever.

What version of the product are you using (Nagios Checker and Nagios)? On
what operating system?
Nagios Checker version 0.9.5

Please provide any additional information below.
We are monitoring 1000 services on 239 hosts and we are only having this
problem if we are logging in as a user who can view all of the
hosts/services. If we are using a user that only is allowed to see some of
the hosts/services it´s working perfectly. I guess there is a problem for
nagios checker to handle a lot of objects.

Original issue reported on code.google.com by anders.t...@gmail.com on 7 Aug 2007 at 10:52

GoogleCodeExporter commented 9 years ago 
This is probably due to some timeout issues.  Bring up "about:config" in the 
browser, look up "extensions.nagioschecker.timeout" and make this value higher. 

Make sure that the value is lower than your refresh interval though.

If possible it would be great if NagiosChecker can provide a means to change 
this in 
its own menus.

Original comment by bernard...@gmail.com on 9 Aug 2007 at 7:04

GoogleCodeExporter commented 9 years ago 
Same issue with 374 hosts and 909 services (growing)...

Tried to put an higher value for "extensions.nagioschecker.timeout", but the 
wheel
still spinning and spinning again...

Time to configure new users in Nagios to test if it works better with a smaller
number of hosts to monitor.

Original comment by cham...@gmail.com on 30 Aug 2007 at 2:57

GoogleCodeExporter commented 9 years ago 
I am monitoring a lot more hosts and services and upping the 
extensions.nagioschecker.timeout solved the problem for me.  Questions:

- Did you restart firefox after you changed the settings?
- What did you change the timeout to, I changed it to 60.

Original comment by bernard...@gmail.com on 1 Sep 2007 at 12:15

GoogleCodeExporter commented 9 years ago 
I tried different values, and '60' was one of my choices. I did not restart 
Firefox
every time, but surely did it between time out changes. Upgrading to version 
0.10.2
(on Firefox 2.0.0.6) did not change anything...

Original comment by cham...@gmail.com on 3 Sep 2007 at 1:45

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hello,

I was suspecting that it was working with version 0.9.4... and it works ! I 
keep this
version before further notice.

Is it helpful ?

Original comment by cham...@gmail.com on 7 Sep 2007 at 1:42

GoogleCodeExporter commented 9 years ago 
Everything works well with version 0.11.

Thanks.

Original comment by cham...@gmail.com on 20 Nov 2007 at 10:36

GoogleCodeExporter commented 9 years ago 
Thank you for your response.

Original comment by petr.si...@gmail.com on 20 Nov 2007 at 9:49