Hello,

Also please when testing do not use a full blown configuration, that is just in a way of everybody. Create the most simple configuration file you can make, and test with that configuration file.

Like:

#test.conf

@version: 3.13

@include "scl.conf"

source s_net { syslog(ip(192.168.1.19) transport("tcp") port(514)); };

destination d_file { file("/tmp/syslog-ng.txt"); };

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

Start it with syslog-ng -Fdev -f test.conf

* Check the output for clues and/or paste here so we could also check it.

* How did you checked that it is not listening on that port ?

(syslog-ng usually either listens on that port or fails to start, so I am curious)

Kokan

On Sat, Nov 3, 2018 at 10:17 PM PÁSZTOR György <pasztor@linux.gyakg.u-szeged.hu> wrote:

Hi,

"Fosiul Alam" <fosiul@gmail.com> írta 2018-11-03 10:35-kor:
> Nov 03 10:34:25 syslog systemd[1]: syslog-ng.service: Main process exited,
> code=exited, status=2/INVALIDARGUMENT
> Nov 03 10:34:25 syslog systemd[1]: syslog-ng.service: Failed with result
> 'exit-code'.
> Nov 03 10:34:25 syslog systemd[1]: Failed to start System Logger Daemon.
> Nov 03 10:34:26 syslog systemd[1]: syslog-ng.service: Service hold-off time
> over, scheduling restart.
> Nov 03 10:34:26 syslog systemd[1]: syslog-ng.service: Scheduled restart
> job, restart counter is at 5.
> Nov 03 10:34:26 syslog systemd[1]: Stopped System Logger Daemon.
> Nov 03 10:34:26 syslog systemd[1]: syslog-ng.service: Start request
> repeated too quickly.
> Nov 03 10:34:26 syslog systemd[1]: syslog-ng.service: Failed with result
> 'exit-code'.
> Nov 03 10:34:26 syslog systemd[1]: Failed to start System Logger Daemon.

Ok, but what is the error message?
As it seems, shitemd joarnal doesn't contain any useful message.

Try to start manually in your terminal in foreground mode (-F).
If it still doesn't show any useful message, you can try to use some
verbose (-v) or debug switch (-d).
Using -e can be also useful.
And next time, for just testing the config file, you can try to use the -s
option for syntax-check only. That way you could be sure, if your config
file syntactically okay and if it is, then you can restart your service.

Regards,
Gyu
______________________________________________________________________________
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