[syslog-ng] Systemd troubles: incompatibility with journald ?

[Guillaume Rousse]

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

I tried to disable journald, but i didn't suceed. I also found 
indication of using the journald socket ( /run/systemd/journal/syslog) 
instead of /dev/log in syslog-ng configuration, but it doesn't change 
much. Also, the fedora package for syslog-ng doesn't contains anything 
special, either in default configuration, or in systemd service unit 
(excepted a patch to force pid file location). So, I'm a bit lost here...

There is a user bug report on this issue:
https://bugs.mageia.org/show_bug.cgi?id=8944

-- 
BOFH excuse #223:

The lines are all busy (busied out, that is -- why let them in to begin 
with?).