[syslog-ng] Unable to make syslog-ng listen to port 514

Czanik, Péter peter.czanik at balabit.com
Sat Nov 3 10:09:03 UTC 2018 

Hi,
That's it: I don't see the s_net source actually used in any of the log
statements.

For testing you could use for example:

log {source(s_net); destination(d_messages); };

And your test messages should show up in /var/log/messages.

Bye,

Peter Czanik (CzP) <peter.czanik at balabit.com>
Balabit (a OneIdentity company) / syslog-ng upstream
https://syslog-ng.com/community/
https://twitter.com/PCzanik


On Sat, Nov 3, 2018 at 11:04 AM Fosiul Alam <fosiul at gmail.com> wrote:

> Thanks,
> please have a look at the log fiel
> I am using the default
>
> Can you please let me know if this looks ok ?
>
> I am not using any selinux
>
>
> @version: 3.13
> @include "scl.conf"
>
> # Syslog-ng configuration file, compatible with default Debian syslogd
> # installation.
>
> # First, set some global options.
> options { chain_hostnames(off); flush_lines(0); use_dns(no); use_fqdn(no);
>           owner("root"); group("adm"); perm(0640); stats_freq(0);
>           bad_hostname("^gconfd$");
> };
>
> ########################
> # Sources
> ########################
> # This is the default behavior of sysklogd package
> # Logs may come from unix stream, but not from another machine.
> #
> source s_src {
>        system();
>        internal();
> };
>
> # If you wish to get logs from remote machine you should uncomment
> # this and comment the above source line.
> #
> source s_net { syslog(ip(192.168.0.13) port(514)  transport("tcp")); };
>
>
> ########################
> # Destinations
> ########################
> # First some standard logfile
> #
> destination d_auth { file("/var/log/auth.log"); };
> destination d_cron { file("/var/log/cron.log"); };
> destination d_daemon { file("/var/log/daemon.log"); };
> destination d_kern { file("/var/log/kern.log"); };
> destination d_lpr { file("/var/log/lpr.log"); };
> destination d_mail { file("/var/log/mail.log"); };
> destination d_syslog { file("/var/log/syslog"); };
> destination d_user { file("/var/log/user.log"); };
> destination d_uucp { file("/var/log/uucp.log"); };
>
> # This files are the log come from the mail subsystem.
> #
> destination d_mailinfo { file("/var/log/mail.info"); };
> destination d_mailwarn { file("/var/log/mail.warn"); };
> destination d_mailerr { file("/var/log/mail.err"); };
>
> # Logging for INN news system
> #
> destination d_newscrit { file("/var/log/news/news.crit"); };
> destination d_newserr { file("/var/log/news/news.err"); };
> destination d_newsnotice { file("/var/log/news/news.notice"); };
>
> # Some 'catch-all' logfiles.
> #
> destination d_debug { file("/var/log/debug"); };
> destination d_error { file("/var/log/error"); };
> destination d_messages { file("/var/log/messages"); };
>
> # The root's console.
> #
> destination d_console { usertty("root"); };
>
> # Virtual console.
> #
> destination d_console_all { file(`tty10`); };
>
> # The named pipe /dev/xconsole is for the nsole' utility.  To use it,
> # you must invoke nsole' with the -file' option:
> #
> #    $ xconsole -file /dev/xconsole [...]
> #
> destination d_xconsole { pipe("/dev/xconsole"); };
>
> # Send the messages to an other host
> #
> #destination d_net { tcp("127.0.0.1" port(1000) log_fifo_size(1000)); };
>
> # Debian only
> destination d_ppp { file("/var/log/ppp.log"); };
>
> ########################
> # Filters
> ########################
> # Here's come the filter options. With this rules, we can set which
> # message go where.
>
> filter f_dbg { level(debug); };
> filter f_info { level(info); };
> filter f_notice { level(notice); };
> filter f_warn { level(warn); };
> filter f_err { level(err); };
> filter f_crit { level(crit .. emerg); };
>
> filter f_debug { level(debug) and not facility(auth, authpriv, news,
> mail); };
> filter f_error { level(err .. emerg) ; };
> filter f_messages { level(info,notice,warn) and
>                     not facility(auth,authpriv,cron,daemon,mail,news); };
>
> filter f_auth { facility(auth, authpriv) and not filter(f_debug); };
> filter f_cron { facility(cron) and not filter(f_debug); };
> filter f_daemon { facility(daemon) and not filter(f_debug); };
> filter f_kern { facility(kern) and not filter(f_debug); };
> filter f_lpr { facility(lpr) and not filter(f_debug); };
> filter f_local { facility(local0, local1, local3, local4, local5,
>                         local6, local7) and not filter(f_debug); };
> filter f_mail { facility(mail) and not filter(f_debug); };
> filter f_news { facility(news) and not filter(f_debug); };
> filter f_syslog3 { not facility(auth, authpriv, mail) and not
> filter(f_debug); };
> filter f_user { facility(user) and not filter(f_debug); };
> filter f_uucp { facility(uucp) and not filter(f_debug); };
>
> filter f_cnews { level(notice, err, crit) and facility(news); };
> filter f_cother { level(debug, info, notice, warn) or facility(daemon,
> mail); };
>
> filter f_ppp { facility(local2) and not filter(f_debug); };
> filter f_console { level(warn .. emerg); };
>
> ########################
> # Log paths
> ########################
> log { source(s_src); filter(f_auth); destination(d_auth); };
> log { source(s_src); filter(f_cron); destination(d_cron); };
> log { source(s_src); filter(f_daemon); destination(d_daemon); };
> log { source(s_src); filter(f_kern); destination(d_kern); };
> log { source(s_src); filter(f_lpr); destination(d_lpr); };
> log { source(s_src); filter(f_syslog3); destination(d_syslog); };
> log { source(s_src); filter(f_user); destination(d_user); };
> log { source(s_src); filter(f_uucp); destination(d_uucp); };
>
> log { source(s_src); filter(f_mail); destination(d_mail); };
> #log { source(s_src); filter(f_mail); filter(f_info);
> destination(d_mailinfo); };
> #log { source(s_src); filter(f_mail); filter(f_warn);
> destination(d_mailwarn); };
> #log { source(s_src); filter(f_mail); filter(f_err);
> destination(d_mailerr); };
>
> log { source(s_src); filter(f_news); filter(f_crit);
> destination(d_newscrit); };
> log { source(s_src); filter(f_news); filter(f_err);
> destination(d_newserr); };
> log { source(s_src); filter(f_news); filter(f_notice);
> destination(d_newsnotice); };
> #log { source(s_src); filter(f_cnews); destination(d_console_all); };
> #log { source(s_src); filter(f_cother); destination(d_console_all); };
>
> #log { source(s_src); filter(f_ppp); destination(d_ppp); };
>
> log { source(s_src); filter(f_debug); destination(d_debug); };
> log { source(s_src); filter(f_error); destination(d_error); };
> log { source(s_src); filter(f_messages); destination(d_messages); };
>
> log { source(s_src); filter(f_console); destination(d_console_all);
>                                     destination(d_xconsole); };
> log { source(s_src); filter(f_crit); destination(d_console); };
>
> # All messages send to a remote site
> #
> #log { source(s_src); destination(d_net); };
> #log { source(s_src);  source(s_net); destination(d_auth); };
> ###
> # Include all config files in /etc/syslog-ng/conf.d/
> ###
> @include "/etc/syslog-ng/conf.d/*.conf"
>
>
> On Sat, Nov 3, 2018 at 9:19 AM Czanik, Péter <peter.czanik at balabit.com>
> wrote:
>
>> Hi,
>>
>> The source declaration seems to be all right. If it still does not work,
>> just a few more ideas what to check:
>>
>> - make sure, that this source is actually used in a log path (other way
>> it is not used)
>> - if you use SELinux, set it to permissive mode temporarily (setenforce 0)
>> - make sure that your firewall does not block it
>> - the syslog() source is for RFC5424 logs, make sure that you send your
>> logs using this protocol version
>>
>> Have a nice weekend!
>>
>> Bye,
>>
>> Peter Czanik (CzP) <peter.czanik at balabit.com>
>> Balabit (a OneIdentity company) / syslog-ng upstream
>> https://syslog-ng.com/community/
>> https://twitter.com/PCzanik
>>
>>
>> On Sat, Nov 3, 2018 at 10:01 AM Fosiul Alam <fosiul at gmail.com> wrote:
>>
>>> Hi
>>> Thanks,
>>> i have changed this to
>>> source s_net { syslog(ip(192.168.1.13) port(514)  transport("tcp")); };
>>>
>>> still it does not listen to 514 or 601
>>>
>>> do i need to do anthing in the config file to make it activate ?
>>>
>>>
>>>
>>> On Fri, Nov 2, 2018 at 9:18 PM Péter, Kókai <peter.kokai at oneidentity.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> The syslog source by default listening on 601 port, you could change
>>>> that with port(514) if you want to.
>>>>
>>>> See the admin guide:
>>>> https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.16/administration-guide/23#TOPIC-956472
>>>>
>>>>
>>>> --
>>>> Kokan
>>>>
>>>> On Fri, 2 Nov 2018, 7:29 pm Fosiul Alam, <fosiul at gmail.com> wrote:
>>>>
>>>>> Hello
>>>>> i have installed syslog-ng in our ubuntu server with version : 3.13
>>>>>
>>>>> its running fine, I am using the default syslog-ng file and i have
>>>>> change this line as per documentation
>>>>>
>>>>> source s_net { syslog(ip(192.168.1.19) transport("tcp")); };
>>>>>
>>>>> but its not listing on port 514
>>>>>
>>>>> What Do i have to do make it listen ?
>>>>>
>>>>> Thanks for the help
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ● syslog-ng.service - System Logger Daemon
>>>>>    Loaded: loaded (/lib/systemd/system/syslog-ng.service; enabled;
>>>>> vendor preset: enabled)
>>>>>    Active: active (running) since Fri 2018-11-02 18:22:46 UTC; 4min 5s
>>>>> ago
>>>>>      Docs: man:syslog-ng(8)
>>>>>  Main PID: 16470 (syslog-ng)
>>>>>     Tasks: 1 (limit: 2361)
>>>>>    CGroup: /system.slice/syslog-ng.service
>>>>>            └─16470 /usr/sbin/syslog-ng -F
>>>>>
>>>>> Nov 02 18:22:46 syslog systemd[1]: Starting System Logger Daemon...
>>>>> Nov 02 18:22:46 syslog systemd[1]: Started System Logger Daemon.
>>>>>
>>>>>
>>>>> --
>>>>> Regards
>>>>> Fosiul Alam
>>>>>
>>>>>
>>>>> ______________________________________________________________________________
>>>>> 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
>>>>
>>>>
>>>
>>> --
>>> Regards
>>> Fosiul Alam
>>>
>>>
>>> ______________________________________________________________________________
>>> 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
>>
>>
>
> --
> Regards
> Fosiul Alam
>
>
> ______________________________________________________________________________
> 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/20181103/1731f12a/attachment-0001.html>

More information about the syslog-ng mailing list