systemd-logger[947]: Failed to connect log socket to /dev/log: No such file or directory init[1]: systemd-logger.service: main process exited, code=exited, status=3 init[1]: Unit systemd-logger.service entered maintenance state. I wonder if it's a systemd issue or a system misconfiguration. I'm running latest F14 packages. $ rpm -qa | grep systemd systemd-sysvinit-8-3.fc14.i686 systemd-units-8-3.fc14.i686 systemd-8-3.fc14.i686
Could you get me a longer dmesg excerpt around this?
Created attachment 443251 [details] dmesg output
Hmm, could you redo this and boot with systemd.log_level=debug systemd.log_target=kmsg? Which syslog implementation are you using? Default rsyslog?
It's syslog-ng-3.1.1-1.fc14.i686. Let me check what happens when I reboot with those arguments...
Created attachment 443278 [details] debug dmesg output
Ah, syslog-ng, hmm. Note that systemd currently cannot really log to syslog-ng anyway, since syslog-ng finds it funny to use a SOCK_STREAM instead of a SOCK_DGRAM socket, which I think is kinda borked. That said, could you please paste the LSB header of the syslog-ng init script? Most likely it isn't including "Provides: $syslog" in the LSB header which has the effect that systemd doesn't synchronize on it properly.
Actually, $syslog is provided: (you can fetch whole init script from Fedora dist git if needed) ### BEGIN INIT INFO # Provides: $syslog # Required-Start: $local_fs # Required-Stop: $local_fs # Short-Description: Next-generation syslog server # Description: syslog-ng, as the name shows, is a syslogd replacement, but # with new functionality for the new generation. The original syslogd # allows messages only to be sorted based on priority/facility pairs; # syslog-ng adds the possibility to filter based on message contents # using regular expressions. The new configuration scheme is intuitive # and powerful. Forwarding logs over TCP and remembering all forwarding # hops makes it ideal for firewalled environments. ### END INIT INFO
I believe this has been addressed upstream: http://cgit.freedesktop.org/systemd/commit/?id=c31e14954b158351b11f886332229a61fff2e5d1
This is now fixed upstream in git. Upload follows shortly.
systemd-10-1.fc14,initscripts-9.20-1.fc14,sysvinit-2.87-5.dsf.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/systemd-10-1.fc14,initscripts-9.20-1.fc14,sysvinit-2.87-5.dsf.fc14
systemd-10-1.fc14, initscripts-9.20-1.fc14, sysvinit-2.87-5.dsf.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update systemd initscripts sysvinit'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/systemd-10-1.fc14,initscripts-9.20-1.fc14,sysvinit-2.87-5.dsf.fc14
I've updated to latest packages from testing and systemd works as expected. Thanks for the fix.
initscripts-9.20-1.fc14, sysvinit-2.87-5.dsf.fc14, systemd-10-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.