Since a long long time systemd has been shipping an rsyslog config snippet /etc/rsyslog.d/listen.conf, to ensure that rsyslog would get its data from the journal, so that it can benefit from log messages from stderr/stdout of daemons, from native journal messages and everything else. To my knowledge rsyslog is nowadays capable of reading this information directly from the journal, hence the snippet is obsolete? Either way, it should probably not be included in systemd anymore, but if it needs to stay it should move to rsyslog, so that only systems which have rsyslog installed get the file. With the next rawhide upload I will drop that file from the systemd package. If this file is still needed, please update rsyslog until then to include the file (or just the config line in it). Current state: # cat /etc/rsyslog.d/listen.conf $SystemLogSocketName /run/systemd/journal/syslog # rpm -qf /etc/rsyslog.d/listen.conf systemd-208-19.fc20.x86_6 Thanks!
Thanks for the heads up. (In reply to Lennart Poettering from comment #0) > To my knowledge rsyslog is nowadays capable of reading this information > directly from the journal, hence the snippet is obsolete? Yeah, it does so by default so listen.conf is not actively used. Getting rid of the file would actually simplify couple of things (e.g. syntax changes). > Either way, it should probably not be included in systemd anymore, but if it > needs to stay it should move to rsyslog, so that only systems which have > rsyslog installed get the file. > > With the next rawhide upload I will drop that file from the systemd package. > If this file is still needed, please update rsyslog until then to include > the file (or just the config line in it). The nice thing about having a conf file provided by systemd is that if the location of the socket changes, configuration will be updated and things won't break. But I guess it's not worth the hassle. After the update hits rawhide, I'll adjust rsyslog's configuration to provide some guidance for people wanting to use the socket anyway.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
liblognorm-1.1.1-1.fc22,rsyslog-8.8.0-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/liblognorm-1.1.1-1.fc22,rsyslog-8.8.0-2.fc22
Package liblognorm-1.1.1-1.fc22, rsyslog-8.8.0-2.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing liblognorm-1.1.1-1.fc22 rsyslog-8.8.0-2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4405/liblognorm-1.1.1-1.fc22,rsyslog-8.8.0-2.fc22 then log in and leave karma (feedback).
liblognorm-1.1.1-1.fc22, rsyslog-8.8.0-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.