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

PÁSZTOR György pasztor at linux.gyakg.u-szeged.hu
Sat Nov 3 21:17:38 UTC 2018


Hi,

"Fosiul Alam" <fosiul at 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


More information about the syslog-ng mailing list