Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 608352 - syslog-ng fails to start for source src { systemd-journal(); internal() } in /etc/syslog-ng/syslog-ng.conf SOLVED
Summary: syslog-ng fails to start for source src { systemd-journal(); internal() } in ...
Status: RESOLVED FIXED
Alias: None
Product: Websites
Classification: Unclassified
Component: Wiki (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Wiki Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-05 19:12 UTC by zerous
Modified: 2017-02-05 19:20 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description zerous 2017-02-05 19:12:33 UTC
The syslog-ng wiki recommends changing the line 
source src { system(); internal(); }; 
in the default syslog-ng configuration file to
source src { systemd-journal(); internal(); }; 
for systemd users. But syslog-ng fails to start after making this change.

O/P of journalctl -xe after failed attempt :

Feb 05 21:34:16 abaccus systemd[1]: Starting System Logger Daemon...
-- Subject: Unit syslog-ng.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit syslog-ng.service has begun starting up.
Feb 05 21:34:16 abaccus syslog-ng[4991]: Error parsing source, source plugin system-journal not found in /etc/syslog-ng/syslog-ng.conf at line 25, column 14:
Feb 05 21:34:16 abaccus syslog-ng[4991]: source src { system-journal(); internal(); };
Feb 05 21:34:16 abaccus syslog-ng[4991]: ^^^^^^^^^^^^^^
Feb 05 21:34:16 abaccus syslog-ng[4991]: syslog-ng documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
Feb 05 21:34:16 abaccus syslog-ng[4991]: mailing list: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Feb 05 21:34:16 abaccus systemd[1]: syslog-ng.service: Main process exited, code=exited, status=1/FAILURE
Feb 05 21:34:16 abaccus systemd[1]: Failed to start System Logger Daemon.
-- Subject: Unit syslog-ng.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit syslog-ng.service has failed.
-- 
-- The result is failed.
Feb 05 21:34:16 abaccus systemd[1]: syslog-ng.service: Unit entered failed state.
Feb 05 21:34:16 abaccus systemd[1]: syslog-ng.service: Failed with result 'exit-code'.
Feb 05 21:34:16 abaccus systemd[1]: syslog-ng.service: Service hold-off time over, scheduling restart.
Feb 05 21:34:16 abaccus systemd[1]: Stopped System Logger Daemon.
-- Subject: Unit syslog-ng.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit syslog-ng.service has finished shutting down.
Feb 05 21:34:16 abaccus systemd[1]: syslog-ng.service: Start request repeated too quickly.
Feb 05 21:34:16 abaccus systemd[1]: Failed to start System Logger Daemon.
-- Subject: Unit syslog-ng.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit syslog-ng.service has failed.
-- 
-- The result is failed.
Feb 05 21:34:16 abaccus systemd[1]: syslog-ng.service: Unit entered failed state.
Feb 05 21:34:16 abaccus systemd[1]: syslog-ng.service: Failed with result 'start-limit'.

I had to change it back to the default value which is source src { system(); internal(); } for syslog-ng to restart. I would like to know if there are any repercussions when not using the recommended settings ?
Comment 1 zerous 2017-02-05 19:16:13 UTC
This was just a typo error from my side. Sorry for logging it.

I used system-journal() instead of systemd-journal().