--_004_40FF3EB574329C459B49338F779CE44E014DC83D48bosmail2k7adv_
Content-Type: multipart/alternative;
boundary="_000_40FF3EB574329C459B49338F779CE44E014DC83D48bosmail2k7adv_"
--_000_40FF3EB574329C459B49338F779CE44E014DC83D48bosmail2k7adv_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi,
We were having a problem with one of the clients sending results to our Nag=
ios server via NSCA because something between the client and the server (pr=
obably an annoying firewall) was interfering with the TCP connection and re=
setting it. We were unable to diagnose this from following what was happen=
ing on the client, because as far as the client was concerned, all of the d=
ata was written to the socket successfully. We were unable to diagnose thi=
s from following what was happening on the server, because all it was loggi=
ng was "Ending connection..." without any indication of why.
To debug this particular problem as well as to make it easier to debug such=
problems in the future, I modified the NSCA source code to do better loggi=
ng of errors like this. It's a straightforward but useful change. Is ther=
e any chance of getting it folded back into the master source tree, and if =
so, to whom should I send it?
Thanks,
[cid:[email protected]] Jonathan Kamens
Operations Manager
Tamale RMS
Advent Software, Inc.
201 South Street, Floor 3
Boston, MA 02111
617.261.0264 ext. 133 office
617.417.8989 mobile
617.812.0330 fax
--_000_40FF3EB574329C459B49338F779CE44E014DC83D48bosmail2k7adv_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
v\:* {behavior:url(
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]