Hide Forgot
Description of problem: After booting system see in /var/log/messages: Jun 12 11:07:15 P5K-EWIFI kernel: [ 12.961021] systemd[1]: Unit systemd-logger.service entered failed state. $ systemctl status systemd-logger.service systemd-logger.service - Stdio Syslog Bridge Loaded: loaded (/lib/systemd/system/systemd-logger.service) Active: failed since Sun, 12 Jun 2011 11:06:44 -0400; 15min ago Process: 616 ExecStart=/lib/systemd/systemd-logger (code=exited, status=218/CAPABILITIES) CGroup: name=systemd:/system/systemd-logger.service Version-Release number of selected component (if applicable): $ rpm -q systemd systemd-28-3.fc16.x86_64 How reproducible: every boot Steps to Reproduce: 1. boot system 2. 3. Actual results: as above and then problems shutting down. Expected results: no error Additional info: When shutting down see: Jun 12 11:07:15 P5K-EWIFI kernel: [ 12.787535] systemd[1]: systemd-logger.service: main process exited, code=exited, status=218 Jun 12 11:07:15 P5K-EWIFI kernel: [ 12.808025] systemd[1]: Unit systemd-logger.service entered failed state. repeated maybe 100 times before shutdown or reboot.
What's your kernel version?
2.6.39-1.fc16.x86_64 Can't use 3.0 kernel's yet due to https://bugzilla.redhat.com/show_bug.cgi?id=710646 mdadm needs a patch.
This error will happen whenever the kernel adds a new capability, we build systemd against it, and then someone attempts to run it on an older kernel. We should make systemd tolerate missing capabilities. As a workaround comment out the CapabilityBoundingSet= lines from all systemd unit files.
Ok, working now that I can use 3.0 kernels. Should this stay open for older kernels? Should there be a requires on 3.0 kernels?
Yes, this bug should stay open. No, there should not be a Requires on kernel-3.0. It will be fixed properly. I saw Tollef Fog Heen yesterday on #systemd already proposing a patch for it.
Fixed upstream by: http://cgit.freedesktop.org/systemd/commit/?id=ae556c210942cb6986c6d77b58505b5daa66bbe2 (I'm going to abuse the POST Bugzilla state to indicate "Fixed in git". Some other Fedora packages do it this way and it seems cleaner than putting this information into the bug title.).
systemd-26-6.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/systemd-26-6.fc15
Package systemd-26-7.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-26-7.fc15' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/systemd-26-7.fc15 then log in and leave karma (feedback).
Package systemd-26-8.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-26-8.fc15' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/systemd-26-8.fc15 then log in and leave karma (feedback).
systemd-26-8.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.