NDO2DB 2.0.0
Copyright (c) 2009 Nagios Core Development Team and Community Contributors
Copyright (c) 2005-2008 Ethan Galstad
Last Modified: 02-28-2014
License: GPL v2
Nagios Core 4.0.8
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 08-12-2014
License: GPL
In addition, have you noticed any issues with your XI server aside from these messages? Notifications not being sent, check statuses not being updated, etc?
Hmmm. We've seen similar behavior but usually in those cases the kernel message queue fills up. Yours looks to be processing just fine.
What sort of hardware do you have? It's possible that if you are in a VM, you are hitting an issue where having too many cores/CPUs actually is detrimental, because the hypervisor has to wait longer to decide which VMs can get a slice of compute time:
This is in a VM evironment, but so far I think the resources is set correctly to what's needed. I started with 4vCPUs and it seems to be used quite a bit. We are still populating the instance, so I've added 2 additional cores since then. This is part of a bigger environment and resourcing and cpus seems to be fine. We have hosts with a total of 16cores (2socket x 8 core) per host, so I do not think this would be a contention issue at this point.
CFT6Server wrote:Looking at top and ndo2db is pretty much pinned at over 90%. What are these and should I be concerned?
The great news is nothing is broken it seems, but yes - to me this is cause for concern. Was the string of errors you blatted out isolated or is it spraying that ndo2db error nonstop?
Also - is your mysql offloaded? I kind of hope not... so that we can tell you DO IT and hopefully it will solve all your problems. I'm afraid you're going to tell me it already is though.