Sorry about this, but... On Fri, 2006-06-23 at 13:01 -0300, Marcel Mitsuto Fucatu Sugano wrote: > Is there someone having problems with Nagios 2.4 forking processes that > simply does not terminate in a hibrid monitoring configuration of some > active checks and a lot of passive checks? > > It seems that when Nagios forks to execute an active check, the forked > process did not terminate itself. Therefore it begins to double > submitting check results to our central Nagios, and messing up with > services statuses becoming staled. > > Someone have any advice on how to detect forked Nagios processes that > will mess with central Nagios freshness service checking? > > Just grepping -v `head -n 1 nagiosl.lock` file isn't enough, as some > forked process might be actively checking something. But, if that > process keep itself running, it should be killed. Still don't know why > the forked process did not terminate itself, but i think it might have > something to do with syslog-ng, but can't tell for sure.
This is what i'm talking about: nagios 2223 1 2 13:01 ? 00:00:37 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 28074 1 0 13:21 ? 00:00:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 30447 1 0 13:22 ? 00:00:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 30592 1 0 13:22 ? 00:00:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 30865 2223 0 13:22 ? 00:00:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 30867 30865 0 13:22 ? 00:00:00 /bin/sh /opt/nagios-2.4/libexec/submit_check_result sensei4-b Cron Daemon OK proc=cron n_procs=1 threads=1 mem_size=240 mem_vsize=1736 mem_r nagios 30868 30867 0 13:22 ? 00:00:00 /bin/sh /opt/nagios-2.4/libexec/submit_check_result sensei4-b Cron Daemon OK proc=cron n_procs=1 threads=1 mem_size=240 mem_vsize=1736 mem_r nagios 30869 30867 0 13:22 ? 00:00:00 /bin/sh /opt/nagios-2.4/libexec/submit_check_result sensei4-b Cron Daemon OK proc=cron n_procs=1 threads=1 mem_size=240 mem_vsize=1736 mem_r [some other time] nagios 2223 1 3 13:01 ? 00:00:42 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 15338 1 0 13:25 ? 00:00:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 15661 2223 0 13:25 ? 00:00:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 15663 15661 0 13:25 ? 00:00:00 /bin/sh /opt/nagios-2.4/libexec/submit_check_result sensei18-b Disk Space OK (/ 14 90)(/boot 36 90)(/export 7 90)(/opt 46 90)(/usr 25 90)(/v nagios 15664 15663 0 13:25 ? 00:00:00 /bin/sh /opt/nagios-2.4/libexec/submit_check_result sensei18-b Disk Space OK (/ 14 90)(/boot 36 90)(/export 7 90)(/opt 46 90)(/usr 25 90)(/v nagios 15665 15663 0 13:25 ? 00:00:00 /bin/sh /opt/nagios-2.4/libexec/submit_check_result sensei18-b Disk Space OK (/ 14 90)(/boot 36 90)(/export 7 90)(/opt 46 90)(/usr 25 90)(/v [one minute after a restart] nagios 373 1 5 13:27 ? 00:00:01 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 2675 373 0 13:28 ? 00:00:00 /opt/nagios/bin/nagios -d /opt/nagios/etc/nagios.cfg nagios 2676 2675 0 13:28 ? 00:00:00 /bin/sh /opt/nagios-2.4/libexec/submit_check_result shogun96-c PING OK OK - 172.27.248.195: rta 1.849ms, lost 0% nagios 2679 2676 0 13:28 ? 00:00:00 /bin/sh /opt/nagios-2.4/libexec/submit_check_result shogun96-c PING OK OK - 172.27.248.195: rta 1.849ms, lost 0% As you can see, there is something very strange. The two first, are messages coming from syslog-ng, and the third is active checking. Stracing pids did not lead to anything conclusive, as each process is acting within their processing loop. Will try to recompile Nagios, from the latest cvs. TIA. AVISO: A informação contida neste e-mail, bem como em qualquer de seus anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) acima referido(s), podendo conter informações sigilosas e/ou legalmente protegidas. Caso você não seja o destinatário desta mensagem, informamos que qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de seus anexos é absolutamente proibida. Solicitamos que o remetente seja comunicado imediatamente, respondendo esta mensagem, e que o original desta mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão realizada a partir destes, sejam permanentemente apagados e/ou destruídos. Informações adicionais sobre nossa empresa podem ser obtidas no site http://sobre.uol.com.br/. NOTICE: The information contained in this e-mail and any attachments thereto is CONFIDENTIAL and is intended only for use by the recipient named herein and may contain legally privileged and/or secret information. If you are not the e-mail´s intended recipient, you are hereby notified that any dissemination, distribution or copy of this e-mail, and/or any attachments thereto, is strictly prohibited. Please immediately notify the sender replying to the above mentioned e-mail address, and permanently delete and/or destroy the original and any copy of this e-mail and/or its attachments, as well as any printout thereof. Additional information about our company may be obtained through the site http://www.uol.com.br/ir/. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
