|
From: Chris S. <chr...@da...> - 2003-08-05 12:37:09
|
Hi all quick questions; I have been using Nagios for a while now and it's doing a great job, the only issue, and it's really just a minor annoyance is that when I use check_ssh on my servers it causes a ton of the following to be thrown to my logs, which then show up the next day in logwatch Connection from A.B.C.D port 53213 Enabling compatibility mode for protocol 2.0 Connection from A.B.C.D port 53346 Enabling compatibility mode for protocol 2.0 Connection from A.B.C.D port 53479 Enabling compatibility mode for protocol 2.0 Connection from A.B.C.D port 53609 as I said not a problem, but a pain in the butt none the less, with each active check throwing this into the daily logwatch it's really polluting the data, and I worry will cause a situation where legitimate information will be missed by human eye's that are so used to just skipping the SSHD section of the logwatch due to the pages and pages of the above. Has anyone got a solution to this? or do all the Nagios RH users out there just live with the problem?? if anyone has a patch for the SSHD Logwatch code that can tell it to ignore an IP (Basically get it to ignore the Nagios IP and not report any of the connections from it) I would appreciate it, or any other useful shove in the right direction towards fixing this. -- Chris Stankaitis |