Version-Release number of selected component: dnssec-trigger-0.15-5.fc28 Additional info: reporter: libreport-2.9.5 cmdline: /usr/bin/python3 -sE /usr/libexec/dnssec-trigger-script --setup crash_function: check_call exception_type: subprocess.CalledProcessError executable: /usr/libexec/dnssec-trigger-script interpreter: python3-3.6.5-1.fc28.x86_64 kernel: 4.17.3-200.fc28.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: subprocess.py:291:check_call:subprocess.CalledProcessError: Command '['unbound-control', 'set_option', 'cache-max-negative-ttl:', '5']' 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 554, in run_setup self._unbound_set_negative_cache_ttl(UNBOUND_MAX_NEG_CACHE_TTL) File "/usr/libexec/dnssec-trigger-script", line 639, in _unbound_set_negative_cache_ttl subprocess.check_call(CMD, stdout=DEVNULL, stderr=DEVNULL) File "/usr/lib64/python3.6/subprocess.py", line 291, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['unbound-control', 'set_option', 'cache-max-negative-ttl:', '5']' returned non-zero exit status 1. Local variables in innermost frame: cmd: ['unbound-control', 'set_option', 'cache-max-negative-ttl:', '5'] retcode: 1 kwargs: {'stdout': <_io.BufferedWriter name='/dev/null'>, 'stderr': <_io.BufferedWriter name='/dev/null'>} popenargs: (['unbound-control', 'set_option', 'cache-max-negative-ttl:', '5'],) Potential duplicate: bug 1489170
Created attachment 1457753 [details] File: backtrace
Created attachment 1457754 [details] File: cgroup
Created attachment 1457755 [details] File: cpuinfo
Created attachment 1457756 [details] File: environ
Created attachment 1457757 [details] File: mountinfo
Created attachment 1457758 [details] File: namespaces
Created attachment 1457759 [details] File: open_fds
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.