Hello Peter,

thanks for your comment. First of all, let me admit that I was rather frustrated with syslog-ng when I wrote that post because I had spent days debugging both syslog-ng and systemd to find the issue I described.

Especially since the systemd code is fairly simple: http://paste.pocoo.org/show/261471/ (lines 135 to 182)

I kept getting either “connection refused” or “file does not exist”. This simply doesn’t happen with rsyslog which just works (which I will gladly admit has been true for syslog-ng for many years, too).

If you have any ideas what the issue could be, I’ll gladly take advice.

As for logging to databases with syslog-ng – I was aware of http://www.balabit.com/sites/default/files/documents/syslog-ng-v3.0-guide-admin-en.html/index.html-single.html#configuring_destinations_sql
and an adaption of Example 3.22 to MySQL succeeded to connect to the database, created the tables but the logging failed. (Unfortunately, I don’t have the details anymore as it’s been quite a while since I tried it.)

Anyway, I didn’t mean to offend and I’d like to apologise if I did.

Best regards, Wulf