Page 2 of 2

Re: Stuck in Applying Changes

Posted: Thu May 18, 2017 11:08 am
by SavaSC
I'll be honest, you just went way over my head. :-D That's OK, it's great info and I'm sure someone will need it.

I did go through and start doing some by hand. I got about 1\4 of the way through the list and am now sitting at 87% used. So, that's a HUGE jump.

Thank you very much for your help.

Re: Stuck in Applying Changes

Posted: Thu May 18, 2017 11:28 am
by dwhitfield
SavaSC wrote: So, that's a HUGE jump.
Indeed!

I'm really surprised du -a /usr/local | sort -n -r | head -n 10 didn't have you look in the perfdata. Maybe it did and it just wasn't something you wanted to delete before.

I guess if it were me I'd stop (unless just just want less data for the migration) and just know where to go back to if things started to fill up. I guess if you had any logs of the size of that mount point those could be useful to see how quickly you got to a problem state.

You might also want to adjust your warning and critical on the localhost disk check to alert you sooner, if you have one of those checks.

Re: Stuck in Applying Changes

Posted: Thu May 18, 2017 12:01 pm
by SavaSC
dwhitfield wrote: guess if it were me I'd stop (unless just just want less data for the migration) and just know where to go back to if things started to fill up. I guess if you had any logs of the size of that mount point those could be useful to see how quickly you got to a problem state.

You might also want to adjust your warning and critical on the localhost disk check to alert you sooner, if you have one of those checks.
I did stop. It seems like it should be more than enough space.

Well, therein lies the rub. We didn't have any mount points monitored. Yes, I'm going to change that! :-D

This space issue had a big chain reaction in Nagios. Notifications stopped and no changes could be applied. It even caused some DB issues where removed / inactive hosts were still showing as down on the reports (although missing from CCM). I had to do a vacuum of the DB to get rid of those issue.

I would like to make a formal feature request to add the ability to clean up that /usr/local/nagios/share/perfdata to where it only has currently active host data. Where do I do that?

Thanks!

Re: Stuck in Applying Changes

Posted: Thu May 18, 2017 12:16 pm
by dwhitfield
It seems this request already exists. The request ID is 7750. No version # has been given yet, but it hasn't been rejected. 5.5 would be the earliest you'd see it. Really, anything I say about the 5.5 release at this point is mere speculation. I would say check back in December if it's not out yet.

If it's an XI request, you are in the right place. If it's Core or the Plugins, those go to github. https://github.com/nagios-plugins/nagio ... issues/new specifically for the plugins. Sometimes it's hard to know if it's really an XI or Core feature request. That's something we can sort out on the forums on a case-by-case basis.

Re: Stuck in Applying Changes

Posted: Thu May 18, 2017 1:53 pm
by SavaSC
Awesome! Thank you very much for all of your assistance. I *think* I've got it working properly (for now!).

Re: Stuck in Applying Changes

Posted: Thu May 18, 2017 2:03 pm
by dwhitfield
Glad to hear it is resolved. I am going to lock the thread. Please feel free to post again if you have you another issue. Thank you for using the Nagios forums!