This is a multi-part message in MIME format.
--------------020703010701010006010500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 11.01.2012 20:16, Andrew Widdersheim wrote:
> I wanted to use Mike Lindsey's new features in nsca-2.9 but found that
> clients on 2.7.2 were not able to communicate after updating the
> server. I found this on the Nagios bug tracker:
>
> http://tracker.nagios.org/view.php?id=78
>
> From what I'm reading it's not possible to have a client and server
> compiled with different MAX_PLUGINOUTPUT_LENGTH. Has this been fixed
> at all and I'm just not finding it?
i would guess the changed length of char arrays will affect the
calculated crc for the packet.
the clients calculate a crc based on MAX_PLUGINOUTPUT_LENGTH=512 and add
that to the sent packet. the server receives a packet, reads the crc32
and calculates one itsself for having MAX_PLUGINOUTPUT_LENGTH=4096 (to
be looked at in include/common.h - data_packet_struct)
search the logs for "Dropping packet with invalid CRC32 - possibly due
to client using wrong password or crypto algorithm?" - anything?
it might also affect en/decryption methods, so watch for such error
messages as well.
>
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
>
>
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
--
DI (FH) Michael Friedrich
Vienna University Computer Center
Universitaetsstrasse 7 A-1010 Vienna, Austria
email: [email protected]
phone: +43 1 4277 14359
mobile: +43 664 60277 14359
fax: +43 1 4277 14338
web: http://www.univie.ac.at/zid
http://www.aco.net
Lead Icinga Core Developer
http://www.icinga.org
--------------020703010701010006010500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
On 11.01.2012 20:16, Andrew Widdersheim wrote:
I wanted to use Mike Lindsey's new features in nsca-2.9 but
found that clients on 2.7.2 were not able to communicate after
updating the server. I found this on the Nagios bug tracker:
http://tracker.nagios.org/view.php?id=78
From what I'm reading it's not possible to have a client and
server compiled with different MAX_PLUGINOUTPUT_LENGTH. Has
this been fixed at all and I'm just not finding it?
i would guess the changed length of char arrays will affect the
calculated crc for the packet.
the clients calculate a crc based on MAX_PLUGINOUTPUT_LENGTH=512
and add that to the sent packet. the server receives a packet,
reads the crc32 and calculates one itsself for having
MAX_PLUGINOUTPUT_LENGTH=4096 (to be looked at in include/common.h
- data_packet_struct)
search the logs for "Dropping packet with invalid CRC32 - possibly
due to client using wrong password or crypto algorithm?" -
anything?
it might also affect en/decryption methods, so watch for such
error messages as well.
<pr
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]