Bug 1221939 - [abrt] dnssec-trigger: subprocess.py:1456:_execute_child:FileNotFoundError: [Errno 2] No such file or directory: '/etc/init.d/NetworkManager'
Summary: [abrt] dnssec-trigger: subprocess.py:1456:_execute_child:FileNotFoundError: [...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dnssec-trigger
Version: 21
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Hozza
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:fd65fc7d471bc8727905bd48dbf...
: 1241291 (view as bug list)
Depends On:
Blocks: Default_Local_DNS_Resolver
TreeView+ depends on / blocked
 
Reported: 2015-05-15 10:00 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2015-07-15 13:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-15 13:27:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.84 KB, text/plain)
2015-05-15 10:00 UTC, Dominik 'Rathann' Mierzejewski
no flags Details
File: environ (134 bytes, text/plain)
2015-05-15 10:00 UTC, Dominik 'Rathann' Mierzejewski
no flags Details

Description Dominik 'Rathann' Mierzejewski 2015-05-15 10:00:31 UTC
Description of problem:
I connected to an open wifi with a captive portal.

Version-Release number of selected component:
dnssec-trigger-0.12-20.fc21

Additional info:
reporter:       libreport-2.3.0
cmdline:        /usr/bin/python3 /usr/libexec/dnssec-trigger-script --restore
executable:     /usr/libexec/dnssec-trigger-script
kernel:         3.19.5-200.fc21.x86_64
runlevel:       N 5
type:           Python3
uid:            0

Truncated backtrace:
subprocess.py:1456:_execute_child:FileNotFoundError: [Errno 2] No such file or directory: '/etc/init.d/NetworkManager'

Traceback (most recent call last):
  File "/usr/libexec/dnssec-trigger-script", line 704, in <module>
    Application(sys.argv).run()
  File "/usr/libexec/dnssec-trigger-script", line 459, in run
    self.method()
  File "/usr/libexec/dnssec-trigger-script", line 554, in run_restore
    subprocess.check_call(["/etc/init.d/NetworkManager", "restart"])
  File "/usr/lib64/python3.4/subprocess.py", line 556, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/usr/lib64/python3.4/subprocess.py", line 537, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib64/python3.4/subprocess.py", line 858, in __init__
    restore_signals, start_new_session)
  File "/usr/lib64/python3.4/subprocess.py", line 1456, in _execute_child
    raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] No such file or directory: '/etc/init.d/NetworkManager'

Local variables in innermost frame:
orig_executable: '/etc/init.d/NetworkManager'
pass_fds: ()
hex_errno: bytearray(b'2')
startupinfo: None
close_fds: True
errno_num: 2
env: None
cwd: None
errwrite: -1
c2pwrite: -1
start_new_session: False
restore_signals: True
devnull_fd: None
errpipe_write: 11
executable_list: (b'/etc/init.d/NetworkManager',)
fds_to_keep: {11}
child_exec_never_called: False
p2cwrite: -1
executable: b'/etc/init.d/NetworkManager'
child_exception_type: <class 'OSError'>
part: b''
errpipe_read: 10
exception_name: bytearray(b'OSError')
args: ['/etc/init.d/NetworkManager', 'restart']
env_list: None
creationflags: 0
p2cread: -1
preexec_fn: None
errpipe_data: bytearray(b'OSError:2:')
self: <subprocess.Popen object at 0x7f4109b6b358>
errread: -1
low_fds_to_close: []
c2pread: -1
err_msg: "No such file or directory: '/etc/init.d/NetworkManager'"
shell: False

Comment 1 Dominik 'Rathann' Mierzejewski 2015-05-15 10:00:56 UTC
Created attachment 1025725 [details]
File: backtrace

Comment 2 Dominik 'Rathann' Mierzejewski 2015-05-15 10:00:59 UTC
Created attachment 1025726 [details]
File: environ

Comment 3 Tomáš Hozza 2015-07-10 09:59:50 UTC
*** Bug 1241291 has been marked as a duplicate of this bug. ***

Comment 4 Tomáš Hozza 2015-07-13 15:29:09 UTC
So the issue seems to be that SELinux denies the access to /sys/fs/cgroup/systemd. Please see Bug #1242430

Comment 5 Tomáš Hozza 2015-07-15 13:27:26 UTC
This Should not happen any more on Fedora, since we changed the script to send the NM signal if the NM is new enough. NM is new enough in F22+ so the check that failed will not get executed.


Note You need to log in before you can comment on or make changes to this bug.