Bug 1547476 - [abrt] dnssec-trigger: check_call(): subprocess.py:291:check_call:subprocess.CalledProcessError: Command '['unbound-control', 'flush_zone', '.']' returned non-zero exit status 1.
Summary: [abrt] dnssec-trigger: check_call(): subprocess.py:291:check_call:subprocess....
Keywords:
Status: CLOSED DUPLICATE of bug 1667388
Alias: None
Product: Fedora
Classification: Fedora
Component: dnssec-trigger
Version: 29
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:a7f47c177720888e355566968b3...
: 1577518 1630544 1653221 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-21 12:12 UTC by Bodo
Modified: 2019-08-27 14:07 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-27 14:07:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.29 KB, text/plain)
2018-02-21 12:13 UTC, Bodo
no flags Details
File: cgroup (441 bytes, text/plain)
2018-02-21 12:13 UTC, Bodo
no flags Details
File: cpuinfo (1.46 KB, text/plain)
2018-02-21 12:13 UTC, Bodo
no flags Details
File: environ (1.63 KB, text/plain)
2018-02-21 12:13 UTC, Bodo
no flags Details
File: mountinfo (4.75 KB, text/plain)
2018-02-21 12:13 UTC, Bodo
no flags Details
File: namespaces (129 bytes, text/plain)
2018-02-21 12:13 UTC, Bodo
no flags Details
File: open_fds (550 bytes, text/plain)
2018-02-21 12:13 UTC, Bodo
no flags Details

Description Bodo 2018-02-21 12:12:56 UTC
Version-Release number of selected component:
dnssec-trigger-0.13-5.fc27

Additional info:
reporter:       libreport-2.9.3
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
kernel:         4.15.3-300.fc27.x86_64
runlevel:       N 5
type:           Python3
uid:            0

Truncated backtrace:
subprocess.py:291: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 769, in <module>
    main()
  File "/usr/libexec/dnssec-trigger-script", line 756, in main
    Application(sys.argv).run()
  File "/usr/libexec/dnssec-trigger-script", line 491, in run
    self.method()
  File "/usr/libexec/dnssec-trigger-script", line 653, in run_update
    self.run_update_global_forwarders()
  File "/usr/libexec/dnssec-trigger-script", line 676, in run_update_global_forwarders
    UnboundZoneConfig._control([config.flush_command, "."])
  File "/usr/libexec/dnssec-trigger-script", line 327, in _control
    subprocess.check_call(["unbound-control"] + args, 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', 'flush_zone', '.']' returned non-zero exit status 1.

Local variables in innermost frame:
cmd: ['unbound-control', 'flush_zone', '.']
retcode: 1
kwargs: {'stdout': <_io.BufferedWriter name='/dev/null'>, 'stderr': <_io.BufferedWriter name='/dev/null'>}
popenargs: (['unbound-control', 'flush_zone', '.'],)

Comment 1 Bodo 2018-02-21 12:13:03 UTC
Created attachment 1398684 [details]
File: backtrace

Comment 2 Bodo 2018-02-21 12:13:05 UTC
Created attachment 1398685 [details]
File: cgroup

Comment 3 Bodo 2018-02-21 12:13:06 UTC
Created attachment 1398686 [details]
File: cpuinfo

Comment 4 Bodo 2018-02-21 12:13:07 UTC
Created attachment 1398687 [details]
File: environ

Comment 5 Bodo 2018-02-21 12:13:09 UTC
Created attachment 1398688 [details]
File: mountinfo

Comment 6 Bodo 2018-02-21 12:13:11 UTC
Created attachment 1398689 [details]
File: namespaces

Comment 7 Bodo 2018-02-21 12:13:12 UTC
Created attachment 1398690 [details]
File: open_fds

Comment 8 Christian Stadelmann 2018-06-13 05:46:43 UTC
Still present on Fedora 28, see bug #1547476.

Comment 9 Ben Cotton 2018-11-27 15:10:55 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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.

Comment 10 Christian Stadelmann 2018-11-28 19:42:54 UTC
Still present in Fedora 29.

Comment 11 Tomáš Hozza 2018-12-06 09:12:58 UTC
*** Bug 1630544 has been marked as a duplicate of this bug. ***

Comment 12 Tomáš Hozza 2018-12-06 09:13:02 UTC
*** Bug 1577518 has been marked as a duplicate of this bug. ***

Comment 13 Tomáš Hozza 2018-12-06 09:13:22 UTC
*** Bug 1653221 has been marked as a duplicate of this bug. ***

Comment 14 Paul Wouters 2019-08-27 14:07:43 UTC

*** This bug has been marked as a duplicate of bug 1667388 ***


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