Bug 1229216
Summary: | [abrt] dnssec-trigger: subprocess.py:542:check_call:CalledProcessError: Command '['systemctl', '--ignore-dependencies', 'try-restart', 'NetworkManager.service']' returned non-zero exit status 4 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Laurent Rineau <laurent.rineau__fedora> | ||||||
Component: | dnssec-trigger | Assignee: | Tomáš Hozza <thozza> | ||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 20 | CC: | laurent.rineau__fedora, pj.pandit, psimerda, pspacek, pwouters, thozza | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Unspecified | ||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/04c59fe6d8230a838ceac673b0418f565e74da1d | ||||||||
Whiteboard: | abrt_hash:eb253a188c9a64122fd6766b8abd3d2db5ddea4d | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2015-06-30 00:29:55 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: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1182488 | ||||||||
Attachments: |
|
Description
Laurent Rineau
2015-06-08 09:38:59 UTC
Created attachment 1036272 [details]
File: backtrace
Created attachment 1036273 [details]
File: environ
Hi. Is NetworkManager installed on your system? If you run the command manually, does it fail? # systemctl --ignore-dependencies try-restart NetworkManager.service Thanks! I have NetworkManager. renoir ~ $ rpm -q NetworkManager NetworkManager-0.9.9.0-46.git20131003.fc20.x86_64 If I run: renoir ~ $ sudo systemctl --ignore-dependencies try-restart NetworkManager.service then I have AVC: renoir ~ $ sudo ausearch -m AVC -ts recent ---- time->Mon Jun 8 14:34:09 2015 type=PROCTITLE msg=audit(1433766849.549:84411): proctitle=756E626F756E642D636F6E74726F6C00737461747573 type=SYSCALL msg=audit(1433766849.549:84411): arch=c000003e syscall=59 success=yes exit=0 a0=25ee560 a1=2489080 a2=22d54a0 a3=0 items=0 ppid=18212 pid=18228 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="unbound-control" exe="/usr/sbin/unbound-control" subj=system_u:system_r:named_t:s0 key=(null) type=AVC msg=audit(1433766849.549:84411): avc: denied { write } for pid=18228 comm="unbound-control" path="/run/dnssec-trigger/lock" dev="tmpfs" ino=28197 scontext=system_u:system_r:named_t:s0 tcontext=system_u:object_r:dnssec_trigger_var_run_t:s0 tclass=file permissive=0 ---- time->Mon Jun 8 14:34:09 2015 type=PROCTITLE msg=audit(1433766849.785:84412): proctitle=756E626F756E642D636F6E74726F6C006C6973745F666F727761726473 type=SYSCALL msg=audit(1433766849.785:84412): arch=c000003e syscall=59 success=yes exit=0 a0=2614ba0 a1=2489080 a2=22d54a0 a3=0 items=0 ppid=18212 pid=18233 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="unbound-control" exe="/usr/sbin/unbound-control" subj=system_u:system_r:named_t:s0 key=(null) type=AVC msg=audit(1433766849.785:84412): avc: denied { write } for pid=18233 comm="unbound-control" path="/run/dnssec-trigger/lock" dev="tmpfs" ino=28197 scontext=system_u:system_r:named_t:s0 tcontext=system_u:object_r:dnssec_trigger_var_run_t:s0 tclass=file permissive=0 the SELinux issue is bug #1147705. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |