Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 647898 - syslog-ng-3.13.2 does not start with systemd
Summary: syslog-ng-3.13.2 does not start with systemd
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Tomáš Mózes
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-16 19:44 UTC by François Valenduc
Modified: 2018-02-17 14:41 UTC (History)
1 user (show)

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 François Valenduc 2018-02-16 19:44:17 UTC
Everything is in the subject line. I use systemd and since that it has been upgraded to 3.13.2, it does not start with systemd. systemd start syslog-ng gives the following error message: Failed to start syslog-ng.service: Unit syslog-ng.service not found.
Comment 1 Tomáš Mózes 2018-02-16 19:53:01 UTC

*** This bug has been marked as a duplicate of bug 640136 ***
Comment 2 Tomáš Mózes 2018-02-16 19:54:42 UTC
A warning should be printed after emerging syslog-ng with systemd:

"The service file for systemd has changed to support multiple instances. To start the default instance issue:
# systemctl start syslog-ng@default"

Do you have that message in your emerge log?
Comment 3 François Valenduc 2018-02-16 19:57:01 UTC
This message should be shown at the end of emerge ? If so, this is not the case. And systemctl start syslog-ng@default doesn't work either.
It would also be goog to upgrade the wiki page (https://wiki.gentoo.org/wiki/Syslog-ng).
Comment 4 François Valenduc 2018-02-16 19:58:18 UTC
Sorry, I overlooked it. the message is indeed shown. But it doesn't work:

 syslog-ng@default.service - System Logger Daemon "default" instance
   Loaded: loaded (/lib/systemd/system/syslog-ng@.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2018-02-16 20:57:26 CET; 3s ago
     Docs: man:syslog-ng(8)
  Process: 28364 ExecStart=/usr/sbin/syslog-ng -F $OTHER_OPTIONS --cfgfile $CONFIG_FILE --control $CONTROL_FILE --persist-file $PERSIST_FILE --pidfile $PID_FILE (code=exited, status=2)
 Main PID: 28364 (code=exited, status=2)
   Status: "Starting up... (Fri Feb 16 20:57:25 2018"

fév 16 20:57:26 pc-francois systemd[1]: syslog-ng@default.service: Service hold-off time over, scheduling restart.
fév 16 20:57:26 pc-francois systemd[1]: syslog-ng@default.service: Scheduled restart job, restart counter is at 5.
fév 16 20:57:26 pc-francois systemd[1]: Stopped System Logger Daemon "default" instance.
fév 16 20:57:26 pc-francois systemd[1]: syslog-ng@default.service: Start request repeated too quickly.
fév 16 20:57:26 pc-francois systemd[1]: syslog-ng@default.service: Failed with result 'exit-code'.
fév 16 20:57:26 pc-francois systemd[1]: Failed to start System Logger Daemon "default" instance.
zsh: exit 3     systemctl status syslog-ng@default
Comment 5 Tomáš Mózes 2018-02-16 21:30:38 UTC
Is syslog-ng still running? Try to check the process list.

If so, try to kill it and start it again.
Comment 6 François Valenduc 2018-02-17 14:41:10 UTC
It was a configuration problem. After running etc-update, it works as expected. But since syslog-ng was not the last package compiled, I din't had a chance to see the message about the change of the service file. A news would not have been bad.