I've had a look at https://github.com/NagiosEnterprises/na ... issues/172 and it is marked as solved there, but the problem is still present in 4.2.4 - does anyone know if the correction from github will be included in the next nagios core release or any workaround on getting rid of the messages until then?
best regards
Mirco