Can you have multiple non-standard TCP ports as sources
Good Afternoon, I am trying to setup a syslog-ng aggregation server and I can currently get it to listen on standard 601/514 ports. source remote { udp(ip(0.0.0.0)); tcp(ip(0.0.0.0) port(601) max-connections(200)); }; and source remote_2 { tcp(ip(0.0.0.0) port(514) max-connections(200)); }; [root@ms30snllx opt]# netstat -pan |grep syslog tcp 0 0 0.0.0.0:601 0.0.0.0:* LISTEN 22113/syslog-ng tcp 0 0 0.0.0.0:514 0.0.0.0:* LISTEN 22113/syslog-ng udp 3328 0 0.0.0.0:514 0.0.0.0:* 22113/syslog-ng But when I add a new source and have it listen on 1514 for example: source remote_3 { tcp(ip(0.0.0.0) port(1514) max-connections(200)); }; I don't get a listener on 1514 as well when looking via netstat . Is there something I am missing? Thanks in advance,
Hi, On 07/30/2014 08:34 PM, Smith, Jerry Don II wrote:
But when I add a new source and have it listen on 1514 for example:
source remote_3 { tcp(ip(0.0.0.0) port(1514) max-connections(200)); };
I don't get a listener on 1514 as well when looking via netstat .
Is there something I am missing?
Is it already included in a log path? If the tcp source is declared, but not in a log path, it will not listen. Bye, -- Peter Czanik (CzP) <peter.czanik@balabit.com> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ https://twitter.com/PCzanik
________________________________ From: syslog-ng-bounces@lists.balabit.hu <syslog-ng-bounces@lists.balabit.hu> on behalf of Peter Czanik <czanik@balabit.hu> Sent: Wednesday, July 30, 2014 12:41 PM To: syslog-ng@lists.balabit.hu Subject: [EXTERNAL] Re: [syslog-ng] Can you have multiple non-standard TCP ports as sources Hi, On 07/30/2014 08:34 PM, Smith, Jerry Don II wrote: But when I add a new source and have it listen on 1514 for example: source remote_3 { tcp(ip(0.0.0.0) port(1514) max-connections(200)); }; I don't get a listener on 1514 as well when looking via netstat . Is there something I am missing? Is it already included in a log path? If the tcp source is declared, but not in a log path, it will not listen. Bye, That was it, I didn't have a log setup for it. After adding that, it works like a charm. Thanks
participants (2)
-
Peter Czanik
-
Smith, Jerry Don II