[syslog-ng] Weird issue with remote syslog-ng setup

[David Florek]

Hi Peter,

Thanks for getting back to me. I'll double check SELinux. The server is Debian based, but the client is CentOS.

Sincerely,

> On Mar 29, 2016, at 2:52 AM, Czanik, Péter <peter.czanik at balabit.com> wrote:
> 
> Hi,
> 
> Do you have SELinux enabled? For a test you could run "setenforce 0" and restart syslog-ng. If it works, then you should take a look at /var/log/audit/audit.log and extend SELinux configs to allow network connection. AFAIR, on RHEL only port 514 is allowed by default.
> 
> Bye,
> 
> Peter Czanik (CzP) <peter.czanik at balabit.com>
> Balabit / syslog-ng upstream
> http://czanik.blogs.balabit.com/
> https://twitter.com/PCzanik
> 
>> On Tue, Mar 29, 2016 at 1:45 AM, Dave Florek <dave.a.florek at gmail.com> wrote:
>> Hi,
>> 
>> I'm running into a weird issue where I have syslog-ng running on a client and server. Both are correctly configured to push log files from the client to the server and they're both Linux boxes. A netstat command on the client shows an established connection from the client to the server, however on the server, a netstat command does not show a connection from the server to the client or client to server. I checked firewall settings in iptables, however nothing seems to be working. Any ideas on how I can troubleshoot this?
>> 
>> Sincerely,
>> 
>> ______________________________________________________________________________
>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
> 
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20160329/5079544c/attachment.htm