Support for Nagios products and services
https://support.nagios.com/forum/
Well, if I click on the CCM Log link, it initially comes up blank and if I leave the search box blank and hit search, a few items come up, but I know its 1% of the stuff I've done in the CCM.slansing wrote:What errors is it causing? Do you have an example? This is something I've/we've brought up, fleshing out the CCM log a bit to include more input on what a CCM user does while they are logged in.
480...so that explains why so low. So, not I'm ok with this, still wouldnt mind fixing the errors in the http error log though.scottwilkerson wrote:What is set if you go to?
Admin -> Performance Settings -> Databases Tab -> NagiosQL Database section -> Max Logbook Age
Only items less than this many minutes are retained...
You can change this to whatever amount you want...BanditBBS wrote: 480...so that explains why so low. So, not I'm ok with this
Patches already committed for next release...BanditBBS wrote:still wouldnt mind fixing the errors in the http error log though.
Sorry, I'm not exactly sure which items you are referring to... Could you elaborateBanditBBS wrote:480...so that explains why so low. So, not I'm ok with this, still wouldnt mind fixing the errors in the http error log though.scottwilkerson wrote:What is set if you go to?
Admin -> Performance Settings -> Databases Tab -> NagiosQL Database section -> Max Logbook Age
Only items less than this many minutes are retained...
Also, just one more related question......why isn't there a delay or some sort of check built into the apply config and startup scripts to make sure the one doesn't start before the other?
sreinhardt wrote:That would be a symptom of the ndo\nagios sql race condition that abrist was talking about. Are your configs stored locally to the nagios server on a ramdisk or hard disk? Generally this seems to be due to nagios marking everything inactive while it imports the configs then marking them active again in the DB once everything has been loaded into memory and such. If NDO connects prior to the completed import and re-activation, it wreaks all sorts of havoc. Generally we see this with higher latency systems between nagios and mysql, or if the nagios configs are on a san\nas that are acting poorly. Somehow I'm guessing this isn't normally the case for you, since it hasn't been mentioned before. This is usually noticed on an apply config or nagios service restart.it happened Sunday morning at the exact same time an Apply Configuration was processed. It also appeared to want to happen this morning, but I forced the processes to start and everything is fine.
Resolutions for some customers up to this point have been:
reduce latency to the mysql server from the nagios server.
Move the nagios configs to your ramdisk as well, ideally rsync them back to the actual hdd so that they are kept and do not require applying before they would be imported in the case of a server reboot.
Move the nagios configs local to the system if on a san\nas, not likely your issue.
Other things that might impact it:
high load or disk io on the nagios server when applying config
backups or other high traffic\disk activity on either mysql or nagios when apply config happens
other abnormal network traffic while this may have happened
I just wanted to get this info to you and see if it might make sense in your case, it certainly sounds like this is what is happening, as it really only seems to effect large installs with particular optimizations in place.
Code: Select all
for i in 1 2 3 4 5 6 7 8 9 10 ; doCode: Select all
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 ; docleaning up some loose ends... It's going to be a long week.....BanditBBS wrote:p.s. Why are we working at 9:30? Well, 8:30 your time....