No lock_file field in Configuration - Centreon - ndo2db.cfg
which brought us incovenience for writing a ndo2db init script ...
in ndo2db.cfg, there's a lock_file=/path/to/ndo2db.lock directive, and hope this can be added into centreon mgmt iface.
#5 Updated by Andrew Greenwood about 2 years ago
Why does centreon need to meddle with the ndoutils database anyway.. and touch that configuration at all?
The user is expected to build/install nagios before centreon as it stands anyway and your not providing your version of the module as far as I can see in the distro.
I got nagios and ndoutils setup and ready only to find centreon want's to use it's own 'centstatus' version (which doesn't even populate the nagios_dbversion table with the correct version so updating the schema of this database must be tied to Centreon releases.
It would be nice to see a cleaner decoupling of the Nagios project stuff from centreon.
Why can't the ACL table live in the centreon database and centreon simply have credentials to access the ndoutils database leaving it in the Nagios realm.
It's annoying even with Nagios configuration items that come out in new releases that are not supported in centreon for some time afterwords. (like checking for software updates) afterwords. This lock file issue drove me crazy today until I figured out what was happening it breaks the start/stop script for the ndoutil daemon.
One simple solution to address this is to allow user defined key/value pairs to be added to the various configuration files so the user can maintain newer options themselves until they get rolled into core.
#6 Updated by Kenny Kevin almost 2 years ago
I hate to do "me too", but it would be nice if at the very least this config setting (lock_file ) was pulled forward to v2.x.
I just spent the last three hours getting to the bottom of why the ndo2db process wasn't being killed.
And it also means I have to fix this every time we push a config update to nagios. It's not huge, but it is a faff.