Version-Release number of selected component: dnssec-trigger-0.12-13.fc20 Additional info: reporter: libreport-2.2.3 cmdline: /usr/bin/python /usr/libexec/dnssec-trigger-script --update dso_list: python-libs-2.7.5-13.fc20.x86_64 executable: /usr/libexec/dnssec-trigger-script kernel: 3.15.9-200.fc20.x86_64 runlevel: N 5 type: Python uid: 0 Truncated backtrace: subprocess.py:542:check_call:CalledProcessError: Command '['unbound-control', 'flush_zone', '.']' returned non-zero exit status 1 Traceback (most recent call last): File "/usr/libexec/dnssec-trigger-script", line 463, in <module> Application(sys.argv).run() File "/usr/libexec/dnssec-trigger-script", line 362, in run self.method() File "/usr/libexec/dnssec-trigger-script", line 410, in run_update self.run_update_global_forwarders() File "/usr/libexec/dnssec-trigger-script", line 422, in run_update_global_forwarders subprocess.check_call(["unbound-control", "flush_zone", "."]) File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command '['unbound-control', 'flush_zone', '.']' returned non-zero exit status 1 Local variables in innermost frame: cmd: ['unbound-control', 'flush_zone', '.'] retcode: 1 popenargs: (['unbound-control', 'flush_zone', '.'],) kwargs: {}
Created attachment 927082 [details] File: backtrace
Created attachment 927083 [details] File: environ
The command in the script should normally be always successful. I would need to see the output of the following commands run by root: unbound-control status unbound-control flush_zone . /usr/libexec/dnssec-trigger-script --debug --update
Another user experienced a similar problem: yum install dnssec-trigger systemctl enable unbound unbound-keygen systemctl start unbound dnssec-triggerd reporter: libreport-2.2.3 cmdline: /usr/bin/python /usr/libexec/dnssec-trigger-script --update dso_list: python-libs-2.7.5-14.fc20.i686 executable: /usr/libexec/dnssec-trigger-script kernel: 3.16.4-200.fc20.i686+PAE package: dnssec-trigger-0.12-13.fc20 reason: subprocess.py:542:check_call:CalledProcessError: Command '['unbound-control', 'flush_zone', '.']' returned non-zero exit status 1 runlevel: N 5 type: Python uid: 0
Still need additional info for this exceptional state.
(In reply to Pavel Šimerda (pavlix) from comment #5) > Still need additional info for this exceptional state. Sorry, cannot provide any additional info.
Please reopen if you have new information.
Suspects for being duplicate to this one: https://bugzilla.redhat.com/show_bug.cgi?id=1147705 https://bugzilla.redhat.com/show_bug.cgi?id=1183159 The good thing is that both are either fixed or going to be fixed very soon.