Your message dated Fri, 9 Dec 2016 16:09:18 +0100
with message-id <[email protected]>
and subject line No longer relevant
has caused the Debian Bug report #662642,
regarding nsca: Daemon fails to handle packets with more than five reports
(i.e. five lines) in it
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
662642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662642
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nsca
Version: 2.9.1-2
Severity: important
Dear Maintainer,
I am experiencing a bug since I have upgraded to version 2.9.1-2.
Immediately after upgrading the package, I started to see such lines in the log:
Mar 5 14:14:24 lapin nsca[30583]: Dropping packet with invalid CRC32 -
possibly due to client using wrong password or crypto algorithm?
Mar 5 14:14:25 lapin nsca[30584]: Dropping packet with invalid CRC32 -
possibly due to client using wrong password or crypto algorithm?
Also, Nagios soon started complaining about not receiving passive checks. Of
course, everything was working fine before the upgrade, and thus it is not a
password/encryption method mismatch.
After a little more investigation, I found that single-line reports still
worked fine (no error in the logs). For instance
echo test-test,bla,0,OK | /usr/sbin/send_nsca -H globi.homelinux.com -c
/etc/send_nsca.cfg -d ","
works fine. However, multi-line reports cause problems above 5 lines. For
instance
tail -n 5 /dev/shm/host | /usr/sbin/send_nsca -H globi.homelinux.com -c
/etc/send_nsca.cfg
still works, whereas
tail -n 6 /dev/shm/host | /usr/sbin/send_nsca -H globi.homelinux.com -c
/etc/send_nsca.cfg
fails (i.e. generates a line similar to the above in the log file).
I have tested with several encryption methods (0 to 3), and all exhibit the
same behavior.
Thus, I believe that it is a bug in this version of the package.
Regards,
Olivier
PS: config files not included because of password content. However, I edited
only the "password" and "decryption_method" values.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (700, 'testing'), (500, 'unstable')
Architecture: i386 (i586)
Kernel: Linux 3.2.0-1-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nsca depends on:
ii confget 1.03-1
ii debconf [debconf-2.0] 1.5.41
ii libc6 2.13-26
ii libmcrypt4 2.5.8-3.1
ii nsca-client 2.9.1-2
nsca recommends no packages.
Versions of packages nsca suggests:
ii nagios-plugins 1.4.15-5
ii nagios-plugins-basic 1.4.15-5
ii nagios3 3.2.3-3+b2
-- Configuration Files:
/etc/nsca.cfg changed [not included]
/etc/send_nsca.cfg changed [not included]
-- debconf information:
nsca/run-nsca-daemon:
--- End Message ---
--- Begin Message ---
nsca 2.9 has been in Debian for several stable releases already.
--- End Message ---
