Capacity Planing report error

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
User avatar
BanditBBS
Posts: 2474
Joined: Tue May 31, 2011 12:57 pm
Location: Scio, OH
Contact:

Capacity Planing report error

Post by BanditBBS »

When I use graph explorer, I can see all the drives being monitored on our linux machines. However, if I go to the capacity planning reports and select any of the drive, the report is blank and the error "RRD contained NaNs or corrupted data."

Any idea what is wrong?
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
User avatar
nscott
Posts: 1040
Joined: Wed May 11, 2011 8:54 am

Re: Capacity Planing report error

Post by nscott »

Hmm, I remember there being some issue with the drives names changing when converted to service names. What are the names of the drives? Like literal names to Nagios as a service name? Like 'C:\'? There may be an issue with the way the service names are getting translated.
Nicholas Scott
Former Nagios employee
User avatar
BanditBBS
Posts: 2474
Joined: Tue May 31, 2011 12:57 pm
Location: Scio, OH
Contact:

Re: Capacity Planing report error

Post by BanditBBS »

Its the one with a "/" in the dame. I went and changed the one that was "/ Disk Usage" to "Root Disk usage" and waited 30 minutes and it started working. The rest all still dont work, like "/usr Disk Usage"
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
mguthrie
Posts: 4380
Joined: Mon Jun 14, 2010 10:21 am

Re: Capacity Planing report error

Post by mguthrie »

Bug confirmed and assigned. Thanks for the heads up:
http://tracker.nagios.com/view.php?id=306
User avatar
BanditBBS
Posts: 2474
Joined: Tue May 31, 2011 12:57 pm
Location: Scio, OH
Contact:

Re: Capacity Planing report error

Post by BanditBBS »

I see the bug is listed as "Fixed in xicomponents revision 888. "

Where can I download the latest components? If I do an upgrade check it shows everything as most recent and my searches on the exchange come up empty for related terms.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Capacity Planing report error

Post by scottwilkerson »

There was another bug that was found related to this and it is still being worked on.

Components that are part of the Enterprise feature set will be only distributed with version releases of XI.


I would guess this should be resolved @ or around the release of 2012R1.2
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
User avatar
BanditBBS
Posts: 2474
Joined: Tue May 31, 2011 12:57 pm
Location: Scio, OH
Contact:

Re: Capacity Planing report error

Post by BanditBBS »

scottwilkerson wrote:There was another bug that was found related to this and it is still being worked on.

Components that are part of the Enterprise feature set will be only distributed with version releases of XI.


I would guess this should be resolved @ or around the release of 2012R1.2
I thought components wouldn't auto upgrade? I had an issue with the Bulk Modifications and received a new file for that and thought i was
In the meantime go ahead and keep using that component. Individual components are still upgraded manually after the 2011-2012 update, so from here it won't get overwritten unless you manually reinstall the component yourself.
So if what you say is the case, will the installation of newer versions overwrite the modified Bulk Modification component I am running? Or are they just released with newer versions and I will manually tell XI to update them?
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
mguthrie
Posts: 4380
Joined: Mon Jun 14, 2010 10:21 am

Re: Capacity Planing report error

Post by mguthrie »

I think the route that we're going to go is to have the Enterprise-only components update automatically when you update each version of XI. Non-enterprise components will still require a manual update to allow for users to do custom modifications. We've been discussing the most effective way to get component fixes and such out to users and we're thinking this will be the best way. We're open to feedback on this idea though ;)
User avatar
BanditBBS
Posts: 2474
Joined: Tue May 31, 2011 12:57 pm
Location: Scio, OH
Contact:

Re: Capacity Planing report error

Post by BanditBBS »

Here is my feedback:

I would prefer being able to download them separately. This way, if there is a long time between XI releases but a component has been updated/fixed, we would be able to update it without waiting on the next release. Also, this would allow enterprise users to have customized components as well. While this isn't really that big of a deal, now that is just one more thing I will have to check after upgrading to see if the new Bulk Modifications install works, and if not, ask for a fix again.

Just my 2 cents, won't kill me either way.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
mguthrie
Posts: 4380
Joined: Mon Jun 14, 2010 10:21 am

Re: Capacity Planing report error

Post by mguthrie »

Typically our release cycle for XI is on average 4 weeks, which is actually a lot less than most of our components. We can probably also post the latest version of the components as well for download for manual updates, but as we examine logistics for the enterprise-only components, we'll probably push the fresh copies into the XI tree with each update as well. We figured that users who are paying extra for those features shouldn't have to go through extra steps just to have bug fixes applied ;)

The standard components will be left alone, but the enterprise components all have partial encryption, so they're less friendly for custom mods.
Locked