27 Jun
2007
27 Jun
'07
11:52 p.m.
I started seeing this kind of behaviour on my syslog-ng clients when I updated my syslog-ng server to 2.0.4 and tracked it down to the newely added support of TCPWrappers. There was no clue on the client machines since the rejection occured on the syslog-ng server.
Just adding my $0.02 so that nothing was overlooked.
Evan.
Evan - What did you have to do to get it going again? -- tim --