[SOLVED] Syslog-ng error after update

rebootl · 2012-10-21 16:21:06

Hi,

after today's update my syslog-ng is failing to start with the error:

:: Starting Syslog-NG                                                             [BUSY] Error binding socket; addr='AF_UNIX(/run/systemd/journal/syslog)', error='No such file or directory (2)'
Error initializing source driver; source='src', id='src#0'
Error initializing message pipeline;
                                                                                  [FAIL]

At the moment, I'm still using initscripts to boot... However it seems to look for a systemd file ? Is this (quote from frontpage):

However, individual packages may now start relying on the system being booted with systemd.

the problem ? Doesn't really makes sense to me since systemd has it's own log system ?

Edit: During update it says:

(28/32) Aktualisiere systemd                       [##########################] 100%
==> journald now writes to /var/log/journal by default. This can be
    controlled with the Storage setting in /etc/systemd/journald.conf

But this shouldn't affect syslog-ng I think...

Edit2: Ok i see

24 hours depend on systemd dreisner

in the changelog for syslog-ng. But this makes still no sense to me...

Last edited by rebootl (2012-10-21 16:53:53)

m1ck3y · 2012-10-21 16:31:37

I have the same problem

rebootl · 2012-10-21 16:52:04

Ok, I found this topic: https://bbs.archlinux.org/viewtopic.php?id=151132

Sorry, I didn't find it, when I was searching before...

Edit: Problem solved. But I'll put a comment in the other thread...

Last edited by rebootl (2012-10-21 16:52:56)

Arch Linux

#1 2012-10-21 16:21:06

[SOLVED] Syslog-ng error after update

#2 2012-10-21 16:31:37

Re: [SOLVED] Syslog-ng error after update

#3 2012-10-21 16:52:04

Re: [SOLVED] Syslog-ng error after update

Board footer