Le 08/02/2013 12:57, Gergely Nagy a écrit :
Guillaume Rousse <guillomovitch@gmail.com> writes:
Hello list.
I'm unable to run syslog-ng, whatever the version (I tried 3.3.6 and 3.4.1), on a recent system using systemd (mageia cauldron 64 bits, systemd 195). As soon as I'm launching syslog-ng, systemd and systemd-journal cpu usages reach 80/95%, and systemd fill dmesg log with this kind of message: [ 5962.484250] systemd[1]: syslog-ng.service start request repeated too quickly, refusing to start
As it was found in the bug report too, the problem was due to the missing /var/syslog-ng directory. A similar problem was also recently reported in Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699942
The Debian report has the better fix, I believe. But indeed, this is a packaging error, but one that should be documented, and one that can be worked around with a change to the syslog-ng unit file.
I'll probably update the syslog-ng unit file, and/or write some documentation regarding syslog-ng and systemd, aimed at packagers. There was a packaging error, indeed, but I'm not sure it was the only cause of the problem here, as I was able to reproduce the issue even with a correct state directory. I guess any start failure will trigger this issue, given systemd socket activation mechanism. -- BOFH excuse #370:
Virus due to computers having unsafe sex.