<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <style>  </style> </head> <body lang="EN-GB" link="blue" vlink="purple"> <div class="WordSection1"> Check out Bug 247 <a href="http://tracker.nagios.org/view.php?id=247">http://tracker.nagios.org/view.php?id=247</a> The attached patch should fix the issue. Cheers, Phil <div> -- Phil Randal Infrastructure Engineer Hoople Ltd | Thorn Office Centre | Hereford HR2 6JT Tel: 01432 260415 | Email: phil.randal@hoopleltd.co.uk </div> <div> <div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0cm 0cm 0cm"> From: James Fillman [mailto:jfillman@central1.com] Sent: 12 July 2012 18:57 To: 'nagios-users@lists.sourceforge.net' Subject: [Nagios-users] Help with OCP_daemon and distributed monitoring </div> </div> I’ve got a large distributed Nagios installation that uses the OCP_daemon to handle the forwarding of passive service checks to the master server. I’ve recently upgraded from version 3.0.3 to 3.4.1. After the upgrade, I’ve found a serious problem that I haven’t completely solved yet. When using the OCP_daemon, you configure Nagios to forward passive check results by having it write performance data to a named pipe. While on version 3.0.3, all passive check results where being where being written to the perf data named pipe regardless of whether there was performance data or not. Since the upgrade to 3.4.1, check data only gets written to the pipe if the plugin generates perf data. I need all check results, regardless of state to be written to the pipe and forwarded on to the master. Has anyone else encountered this issue and what was the solution. Here’s the relevant config: # Enable Performance data processing. process_performance_data=1 # Files to which Nagios will write data. In this setup # they will be named pipes. #host_perfdata_file=/path/to/host-perfdata.fifo service_perfdata_file=/var/log/nagios/rw/service-perfdata.fifo # This is exactly what will be sent to send_NSCA. Do not change it. host_perfdata_file_template=$HOSTNAME$\t$HOSTSTATEID$\t$HOSTOUTPUT$|$HOSTPERFDATA$ service_perfdata_file_template=$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATEID$\t$SERVICEOUTPUT$|Data: $SERVICEPERFDATA$ # The write mode should be w, although append should have no effect on a named pipe. host_perfdata_file_mode=p service_perfdata_file_mode=p # We don't want to process any command, so set this to 0 host_perfdata_file_processing_interval=0 service_perfdata_file_processing_interval=0 Thanks, --james </div> “Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it. </body> </html>