Bug 757628
| Summary: | scheduled shutdown doesn't work | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sergey Arsenyev <arseniev> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | johannbg, lpoetter, metherid, mschmidt, notting, plautrba, systemd-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-37-11.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-25 04:54:29 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sergey Arsenyev
2011-11-28 06:11:16 UTC
I can reproduce this in Rawhide and also in F16 with the Rawhide kernel. Not in plain F16.
The first attempt always fails, but the following attempts succeed.
In /var/log/messages I'm getting this error from the first attempt:
systemd-shutdownd[1195]: Got request from unprivileged user. Ignoring.
A debug print showed that systemd-shutdownd received:
(struct ucred){.pid=0, .uid=-1, .gid=-1}
It's likely related to this kernel change:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=16e5726269611b71c930054ffe9b858c1cea88eb
af_unix: dont send SCM_CREDENTIALS by default
systemd-shutdownd is socket-activated on demand. systemd does not set SO_PASSCRED on the listening socket. The option is set on the socket by systemd-shutdownd after activation, so that's why only first attempt fails.
We should add an option to set SO_PASSCRED on sockets and use it in systemd-shutdownd.socket.
I've notified netdev: http://marc.info/?l=linux-netdev&m=132248669629981&w=2 Fixed upstream: http://cgit.freedesktop.org/systemd/commit/?id=75d3fc60f88e08bf953063819a8a04b881d6db23 systemd-37-6.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/systemd-37-6.fc16 Package systemd-37-6.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-6.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-6.fc16 then log in and leave karma (feedback). Thanks it's work Package systemd-37-7.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-7.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-7.fc16 then log in and leave karma (feedback). Package systemd-37-8.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-8.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-8.fc16 then log in and leave karma (feedback). Package systemd-37-10.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-10.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-10.fc16 then log in and leave karma (feedback). systemd-37-11.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |