I'm trying to set up a collector and the nsca daemon on the central server is
rejecting my packets:
nsca[10902]: Dropping packet with invalid CRC32 - possibly due to client using
wrong password or crypto algorithm?
Obviously, I've triple-checked the password and algorithm settings, so that's
not the problem.
I'm suspecting that since the collector is running a 64 bit version of SLES
(10.2) and the central server is 32 bit SLES (10.2), that somehow the CRC is
being generated differently between the two.
Another bit of evidence pointing to the suspected mismatch is that the
collector in question can do send_nsca successfully to another 64 bit system.
Anyone else run into this or can think of a workaround to try?
Andy Ford
Network Security Compliance & Automation, Wells Fargo & Co.
Office: 314-955-6647
Cell (preferred): 314-600-7025
[email protected]
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
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
