Am 07.06.19 um 16:14 schrieb Blaise T: > I'm having an issue with my syslog-ng service. I already checked to see > if syslog-ng. service was enabled, which it was. & I ran the syntax > command on syslog-ng & there was no errors. When I try to start the > service, I'm getting an error saying: > > etc/syslog-ng$ systemctl start syslog-ng > Job for syslog-ng.service failed because the control process exited with > error code. See "systemctl status syslog-ng.service" and "journalctl > -xe" for details. > > When I run the systemctl message, I get this: > > systemd[1]: syslog-ng.service failed. > systemd[1]: syslog-ng.service holdoff time over, scheduling restart. > systemd[1]: Stopped System Logger Daemon. > systemd[1]: start request repeated too quickly for syslog-ng.service > systemd[1]: Failed to start System Logger Daemon. > systemd[1]: Unit syslog-ng.service entered failed state. > systemd[1]: syslog-ng.service failed. > systemd[1]: start request repeated too quickly for syslog-ng.service > systemd[1]: Failed to start System Logger Daemon. > systemd[1]: syslog-ng.service failed. this is not a systemd problem beause the service exits and systemd is the messenger telling you - cause and effect either "systemctl status syslog-ng.service" has something useful or you need to report that to syslog-ng or your distribution _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel