Bug#630389: sitesummary-client: sitesummary client drops config snipplet in /etc/nagios/ but should use /etc/nagios/nrpe.d/
[Andreas B. Mundt] > check_kernel_status fails with UNKNOWN. This is not due to a newer > kernel, the lenny stuff works for squeeze, and the script gives the > correct answer when called on the command line. Modifications in the > script do not change the warning at all. Just for the record. This was caused by dpkg truncating package names if the COLUMNS environment variable content was too small. It is fixed in version 0.0.75. Moving configuration to nrpe.d is probably a good idea anyway. :) -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2fllioum83y@diskless.uio.no
Bug#630389: sitesummary-client: sitesummary client drops config snipplet in /etc/nagios/ but should use /etc/nagios/nrpe.d/
Hi, On Mon, Jun 13, 2011 at 07:36:16PM +0200, Petter Reinholdtsen wrote: > [Andreas B. Mundt] > > check_kernel_status fails with UNKNOWN. This is not due to a newer > > kernel, the lenny stuff works for squeeze, and the script gives the > > correct answer when called on the command line. Modifications in > > the script do not change the warning at all. > > Right. Same I have seen for a while. The error show up for a while > after the first boot, and then disappears after some time without > anything being changed. I have not been able to figure out why it > fail, but it is not related to moving any configuration. > > > However, I don't know where the warning comes from in the first > > place. > > Me neither. I suspect some background job running after installation > is blocking something, and the check start working when this > background job is done. But I have never been able to find such > job. :) When testing again, I found that indeed restarting nagios3 fixed the wrong warning. Perhaps something does not yet work when nagios starts at boot-time. I'll revert the changes in svn. Cheers, Andi -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110613192857.GC4107@flashgordon
Bug#630389: sitesummary-client: sitesummary client drops config snipplet in /etc/nagios/ but should use /etc/nagios/nrpe.d/
[Andreas B. Mundt] > check_kernel_status fails with UNKNOWN. This is not due to a newer > kernel, the lenny stuff works for squeeze, and the script gives the > correct answer when called on the command line. Modifications in > the script do not change the warning at all. Right. Same I have seen for a while. The error show up for a while after the first boot, and then disappears after some time without anything being changed. I have not been able to figure out why it fail, but it is not related to moving any configuration. > However, I don't know where the warning comes from in the first > place. Me neither. I suspect some background job running after installation is blocking something, and the check start working when this background job is done. But I have never been able to find such job. :) Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110613173616.gr25...@login1.uio.no
Bug#630389: sitesummary-client: sitesummary client drops config snipplet in /etc/nagios/ but should use /etc/nagios/nrpe.d/
On Mon, Jun 13, 2011 at 07:14:29PM +0200, Petter Reinholdtsen wrote: > [Andreas B. Mundt] > > An error is reported by nagios although anything is OK. > > Which error? I know of one such error, and its reason is probably not > what you suggested. check_kernel_status fails with UNKNOWN. This is not due to a newer kernel, the lenny stuff works for squeeze, and the script gives the correct answer when called on the command line. Modifications in the script do not change the warning at all. After moving it to /etc/nagios3/ the warning vanished and anything works as expected. However, I don't know where the warning comes from in the first place. Regards, Andi -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110613172332.GB4107@flashgordon
Bug#630389: sitesummary-client: sitesummary client drops config snipplet in /etc/nagios/ but should use /etc/nagios/nrpe.d/
[Andreas B. Mundt] > An error is reported by nagios although anything is OK. Which error? I know of one such error, and its reason is probably not what you suggested. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110613171429.gq25...@login1.uio.no
Bug#630389: sitesummary-client: sitesummary client drops config snipplet in /etc/nagios/ but should use /etc/nagios/nrpe.d/
Package: sitesummary-client Severity: important User: debian-edu@lists.debian.org Usertags: debian-edu An error is reported by nagios although anything is OK. The reason seems to be the wrong-placed nagios-nrpe-commands.cfg, (see subject.) From the source of nagios-nrpe-2.12 (debian/patches/03_support_nrpe.d.dpatch, I don't have the final file handy right now): # you can place your config snipplets into nrpe.d/ include_dir=/etc/nagios/nrpe.d/ So I think this is where we should drop sitesummaries nagios-nrpe-commands.cfg. Fixed in SVN. Cheers, Andi -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110613170536.9724.61005.reportbug@flashgordon
