Hello,
I tried to go through the mailing list archive and I found a lot of similar
issues but I still don't know what's wrong with my configuration. I would
expect that if I put the following custom Nagios option into the
main.mkconfiguration file
extra_host_conf['max_check_attempts'] = [
( "3", ALL_HOSTS, ALL_SERVICES ),
]
restarted the OMD site or just generate a new check_mk_objects.cfg file
with
cmk -R
cmk -U
and then outputted the Nagios configuration with
cmk -N
that it would contain "max_check_attempts 3" option under each host
definition. But it's not there and I really don't know what I have
overlooked. Do you have any idea how troubleshoot the issue? Is it somehow
possible to generate the intermediate check_mk configuration with all these
default/custom lists/tuples before getting the final Nagios configuration?
I can see in the file <SITE>/etc/wato.rules.mk check_mk default
configuration values and that the user specified values should be added to
the default extra_service_conf list but in my case, it is not:
extra_service_conf.setdefault('max_check_attempts', [])
extra_service_conf['max_check_attempts'] = [
( 2, [], ALL_HOSTS, ALL_SERVICES ),
] + extra_service_conf['max_check_attempts']
Anyway, I have OMD 1.2.2p3 deployed on RHEL6.5, x86_64. OMD is installed
from official check_mk repo hosted on labs.consol.de
Thank you,
Dave
_______________________________________________
omd-users mailing list
[email protected]
http://lists.mathias-kettner.de/mailman/listinfo/omd-users
