Nagios Support Forum

I just wanted to post an update. We have been running since Thursday using the new check_results strategy and have not seen any invalid alarms. It seems that the issue was related to that command pipe corruption that I found.

I think it would be prudent to clear out the contents of the buf variable in command_input_handler after each process_external_command1 run. It's certainly not ideal to have corruption pop up at all, but I don't see any reason to keep bogus commands around in that variable to (possibly) be executed later.

I think it would be prudent to clear out the contents of the buf variable in command_input_handler after each process_external_command1 run. It's certainly not ideal to have corruption pop up at all, but I don't see any reason to keep bogus commands around in that variable to (possibly) be executed later.

Thank you for the update. I'm sure it will be helpful for those who use the external command pipe to know. Can I close this thread?

Sure, my problem is fixed since we're not using the command pipe anymore. I still think it would be good to patch nagios to fix this command pipe behavior.

I have submitted a bug report on github for Nagios Core. We'll close this thread for now.
https://github.com/NagiosEnterprises/na ... /issues/35