Description of problem: Crashed with unbound together, see bug #1667387. Version-Release number of selected component: dnssec-trigger-0.15-7.fc29 Additional info: reporter: libreport-2.9.7 cmdline: /usr/bin/python3 -sE /usr/libexec/dnssec-trigger-script --update crash_function: check_call exception_type: subprocess.CalledProcessError executable: /usr/libexec/dnssec-trigger-script interpreter: python3-3.7.2-1.fc29.x86_64 kernel: 4.19.14-300.fc29.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: subprocess.py:347:check_call:subprocess.CalledProcessError: Command '['unbound-control', 'flush_zone', '.']' returned non-zero exit status 1. Traceback (most recent call last): File "/usr/libexec/dnssec-trigger-script", line 748, in <module> main() File "/usr/libexec/dnssec-trigger-script", line 735, in main Application(sys.argv).run() File "/usr/libexec/dnssec-trigger-script", line 470, in run self.method() File "/usr/libexec/dnssec-trigger-script", line 632, in run_update self.run_update_global_forwarders() File "/usr/libexec/dnssec-trigger-script", line 655, in run_update_global_forwarders UnboundZoneConfig._control([config.flush_command, "."]) File "/usr/libexec/dnssec-trigger-script", line 306, in _control subprocess.check_call(["unbound-control"] + args, stdout=DEVNULL, stderr=DEVNULL) File "/usr/lib64/python3.7/subprocess.py", line 347, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['unbound-control', 'flush_zone', '.']' returned non-zero exit status 1. Local variables in innermost frame: popenargs: (['unbound-control', 'flush_zone', '.'],) kwargs: {'stdout': <_io.BufferedWriter name='/dev/null'>, 'stderr': <_io.BufferedWriter name='/dev/null'>} retcode: 1 cmd: ['unbound-control', 'flush_zone', '.']
Created attachment 1521463 [details] File: backtrace
Created attachment 1521464 [details] File: cgroup
Created attachment 1521465 [details] File: cpuinfo
Created attachment 1521466 [details] File: environ
Created attachment 1521467 [details] File: mountinfo
Created attachment 1521468 [details] File: namespaces
Created attachment 1521469 [details] File: open_fds
Similar problem has been detected: Suspend and restore. Changed network environments reporter: libreport-2.10.0 cmdline: /usr/bin/python3 -sE /usr/libexec/dnssec-trigger-script --async --update crash_function: check_call exception_type: subprocess.CalledProcessError executable: /usr/libexec/dnssec-trigger-script interpreter: python3-3.7.2-4.fc29.x86_64 kernel: 4.20.13-200.fc29.x86_64 package: dnssec-trigger-0.15-7.fc29 reason: subprocess.py:347:check_call:subprocess.CalledProcessError: Command '['unbound-control', 'flush_zone', '.']' returned non-zero exit status 1. runlevel: N 5 type: Python3 uid: 0
*** Bug 1731518 has been marked as a duplicate of this bug. ***
*** Bug 1547476 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.