reassign 760426 syslog-ng-core thanks Am 05.09.2014 01:42, schrieb Vedran Furač: > On 05.09.2014 01:09, Michael Biebl wrote: >> Am 05.09.2014 00:59, schrieb Michael Biebl: >> >>> Apparently your syslog socket unit fails to start. Why is not clear yet. >>> As said, please provide a complete debug log for the boot. >> >> Please also attache the output of >> ls -la /etc/systemd/system/syslog.service > > Here it is. I'll check the full log later. > > # ls -la /etc/systemd/system/*syslog* > lrwxrwxrwx 1 root root 37 Lis 3 2012 > /etc/systemd/system/syslog.service.dpkg-new -> > /lib/systemd/system/syslog-ng.service
Ok, this somehow got messed up. This is not a bug in systemd, but rather an interaction issue between syslog-ng and rsyslog. Please purge the rsyslog and syslog-ng package and make sure any dangling /etc/systemd/system/syslog.service* symlinks are removed. Then re-install rsyslog. After that, rsyslog should work properly. You can double-check if the syslog.service symlink is pointing correctly at /lib/systemd/system/rsyslog.service. There is already as similar bug report for rsyslog [1] which basically deals with the same problem. I'm re-assigning this to syslog-ng-core. In the end we need to find a way how we can transfer the syslog.socket symlink between packages when moving from rsyslog to syslog-ng and vice versa. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741496 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
