Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: syslog-ng fails to start on reboot Version-Release number of selected component (if applicable): 3.22.1 How reproducible: 100% Steps to Reproduce: 1. reboot 2. 3. Actual results: # systemctl status syslog-ng.service ● syslog-ng.service - System Logger Daemon Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2020-03-02 23:19:21 CET; 5min ago Docs: man:syslog-ng(8) Process: 1047 ExecStart=/usr/sbin/syslog-ng -F $SYSLOGNG_OPTS -p /var/run/syslogd.pid (code=exited, status=2) Main PID: 1047 (code=exited, status=2) Status: "Starting up... (Mon Mar 2 23:19:20 2020" CPU: 43ms mar 02 23:19:20 ninja systemd[1]: Stopped System Logger Daemon. mar 02 23:19:20 ninja systemd[1]: Starting System Logger Daemon... mar 02 23:19:20 ninja systemd[1]: syslog-ng.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mar 02 23:19:20 ninja systemd[1]: syslog-ng.service: Failed with result 'exit-code'. mar 02 23:19:20 ninja systemd[1]: Failed to start System Logger Daemon. mar 02 23:19:21 ninja systemd[1]: syslog-ng.service: Scheduled restart job, restart counter is at 6. mar 02 23:19:21 ninja systemd[1]: Stopped System Logger Daemon. mar 02 23:19:21 ninja systemd[1]: syslog-ng.service: Start request repeated too quickly. mar 02 23:19:21 ninja systemd[1]: syslog-ng.service: Failed with result 'exit-code'. mar 02 23:19:21 ninja systemd[1]: Failed to start System Logger Daemon. Expected results: That it should start. Additional info: Manually running "systemctl start syslog-ng" works - but then it doesn't start up with the same arguments: ● syslog-ng.service - System Logger Daemon Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-03-02 23:25:41 CET; 9min ago Docs: man:syslog-ng(8) Main PID: 3427 (syslog-ng) Tasks: 7 (limit: 19064) Memory: 22.3M CPU: 989ms CGroup: /system.slice/syslog-ng.service ├─3427 /usr/sbin/syslog-ng -F -p /var/run/syslogd.pid ├─3428 /usr/bin/perl -w /usr/local/sbin/syslog_auth ├─3429 /usr/bin/perl -w /usr/local/sbin/syslog_mail ├─3430 /usr/bin/perl -w /usr/local/sbin/syslog_audit ├─3431 /usr/bin/perl -w /usr/local/sbin/syslog_callerid └─3432 /usr/bin/perl -w /usr/local/sbin/syslog_external
Adding the last two lines in [Unit] for network.target lines solved the problem for me. [root@syslog ~]# head -n5 /usr/lib/systemd/system/syslog-ng.service [Unit] Description=System Logger Daemon Documentation=man:syslog-ng(8) Wants=network.target network-online.target After=network.target network-online.target
I suspect that it was some other component that was to blame because the last couple of reboots the syslog-ng service has started just fine even through I'm still using the same syslog-ng version (3.22.1) and the service file has not been updated in a long time: -rw-r--r-- 1 root root 385 13 aug 2019 /usr/lib/systemd/system/syslog-ng.service This is the full content (I don't know how to check if this is the default config file or if it's been altered): [Unit] Description=System Logger Daemon Documentation=man:syslog-ng(8) [Service] Type=notify ExecStart=/usr/sbin/syslog-ng -F $SYSLOGNG_OPTS -p /var/run/syslogd.pid ExecReload=/bin/kill -HUP $MAINPID EnvironmentFile=-/etc/default/syslog-ng EnvironmentFile=-/etc/sysconfig/syslog-ng StandardOutput=journal StandardError=journal Restart=on-failure [Install] WantedBy=multi-user.target
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.