Bug 1693476 - terminate called after throwing an instance of 'libdnf::File::NotOpenedException'
Summary: terminate called after throwing an instance of 'libdnf::File::NotOpenedExcept...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Rohel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1732615
TreeView+ depends on / blocked
 
Reported: 2019-03-27 23:11 UTC by Chris Murphy
Modified: 2019-10-14 07:45 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-14 07:45:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Chris Murphy 2019-03-27 23:11:45 UTC
Description of problem:

libdnf::File::NotOpenedException


Version-Release number of selected component (if applicable):
dnf-4.2.1-1.fc29.noarch

How reproducible:
1 for 2

Steps to Reproduce:
1.
# dnf update
Fedora Modular 29 - ppc64le                                                                                                   469 kB/s | 1.5 MB     00:03    
Fedora Modular 29 - ppc64le - Updates                                                                                         1.2 MB/s | 2.0 MB     00:01    
Fedora 29 - ppc64le - Updates                                                                                                 1.5 MB/s |  21 MB     00:13    
Fedora 29 - ppc64le                                                                                                           2.2 MB/s |  55 MB     00:24    
ll
Last metadata expiration check: 0:00:06 ago on Wed 27 Mar 2019 04:54:54 PM MDT.
terminate called after throwing an instance of 'libdnf::File::NotOpenedException'
  what():  File '/var/cache/dnf/updates-modular-f0377c92a3a60f3f/repodata/a52d6db9f8584a90bf9848b46839a6a664cf2108ad4ba2b82cb6e76fdda00426-modules.yaml.gz' is not opened.
Aborted

Actual result

Crash


Expected results:

No crash

Additional info:

This is on qemu-ppc/kvm on x86_64.


[root@localhost ~]# coredumpctl info 1036
           PID: 1036 (dnf)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Wed 2019-03-27 16:59:58 MDT (11min ago)
  Command Line: /usr/bin/python3 /usr/bin/dnf update
    Executable: /usr/bin/python3.7
 Control Group: /user.slice/user-0.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-0.slice
       Session: 3
     Owner UID: 0 (root)
       Boot ID: ed23cb5ab50646e586f49f5cdb3da0cb
    Machine ID: df49c1c0f25a404893f046cee21a3562
      Hostname: localhost.localdomain
       Storage: /var/lib/systemd/coredump/core.dnf.0.ed23cb5ab50646e586f49f5cdb3da0cb.1036.1553727598000000.lz4
       Message: Process 1036 (dnf) of user 0 dumped core.
                
                Stack trace of thread 1036:
                #0  0x00007fff84db500c raise (libc.so.6)
                #1  0x00007fff84d94520 abort (libc.so.6)
                #2  0x00007fff82e74bb8 _ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6)
                #3  0x00007fff82e6f834 n/a (libstdc++.so.6)
                #4  0x00007fff82e6f8f0 _ZSt9terminatev (libstdc++.so.6)
                #5  0x00007fff82e6fdcc __cxa_throw (libstdc++.so.6)
                #6  0x00007fff83c66a60 _ZN6libdnf14CompressedFile10getContentB5cxx11Ev (libdnf.so.2)
                #7  0x00007fff83c422f8 n/a (libdnf.so.2)
                #8  0x00007fff83c4d4ac _ZN6libdnf22ModulePackageContainer3addEP8_DnfSack (libdnf.so.2)
                #9  0x00007fff83bac220 _Z26dnf_sack_filter_modules_v2B5cxx11P8_DnfSackPN6libdnf22ModulePackageContainerEPPKcS5_S5_bb (libdnf.so.2)
                #10 0x00007fff7fcc1d58 n/a (_hawkey.so)
                #11 0x00007fff85296688 _PyMethodDef_RawFastCallKeywords (libpython3.7m.so.1.0)
                #12 0x00007fff8539b060 _PyMethodDescr_FastCallKeywords (libpython3.7m.so.1.0)
                #13 0x00007fff851fc720 _PyEval_EvalFrameDefault (libpython3.7m.so.1.0)
                #14 0x00007fff852331c4 PyEval_EvalFrameEx (libpython3.7m.so.1.0)
                #15 0x00007fff85303928 _PyEval_EvalCodeWithName (libpython3.7m.so.1.0)
                #16 0x00007fff85303c0c _PyFunction_FastCallKeywords (libpython3.7m.so.1.0)
                #17 0x00007fff851fc22c _PyEval_EvalFrameDefault (libpython3.7m.so.1.0)
                #18 0x00007fff852331c4 PyEval_EvalFrameEx (libpython3.7m.so.1.0)
                #19 0x00007fff85303928 _PyEval_EvalCodeWithName (libpython3.7m.so.1.0)
                #20 0x00007fff85303c0c _PyFunction_FastCallKeywords (libpython3.7m.so.1.0)
                #21 0x00007fff851f9204 _PyEval_EvalFrameDefault (libpython3.7m.so.1.0)
                #22 0x00007fff852331c4 PyEval_EvalFrameEx (libpython3.7m.so.1.0)
                #23 0x00007fff851f1424 n/a (libpython3.7m.so.1.0)
                #24 0x00007fff851fc22c _PyEval_EvalFrameDefault (libpython3.7m.so.1.0)
                #25 0x00007fff852331c4 PyEval_EvalFrameEx (libpython3.7m.so.1.0)
                #26 0x00007fff851f1424 n/a (libpython3.7m.so.1.0)
                #27 0x00007fff851fc22c _PyEval_EvalFrameDefault (libpython3.7m.so.1.0)
                #28 0x00007fff852331c4 PyEval_EvalFrameEx (libpython3.7m.so.1.0)
                #29 0x00007fff851f1424 n/a (libpython3.7m.so.1.0)
                #30 0x00007fff851f9220 _PyEval_EvalFrameDefault (libpython3.7m.so.1.0)
                #31 0x00007fff852331c4 PyEval_EvalFrameEx (libpython3.7m.so.1.0)
                #32 0x00007fff851f1424 n/a (libpython3.7m.so.1.0)
                #33 0x00007fff851f9220 _PyEval_EvalFrameDefault (libpython3.7m.so.1.0)
                #34 0x00007fff852331c4 PyEval_EvalFrameEx (libpython3.7m.so.1.0)
                #35 0x00007fff85303928 _PyEval_EvalCodeWithName (libpython3.7m.so.1.0)
                #36 0x00007fff85303c0c _PyFunction_FastCallKeywords (libpython3.7m.so.1.0)
                #37 0x00007fff851f9220 _PyEval_EvalFrameDefault (libpython3.7m.so.1.0)
                #38 0x00007fff852331c4 PyEval_EvalFrameEx (libpython3.7m.so.1.0)
                #39 0x00007fff85303928 _PyEval_EvalCodeWithName (libpython3.7m.so.1.0)
                #40 0x00007fff85303c0c _PyFunction_FastCallKeywords (libpython3.7m.so.1.0)
                #41 0x00007fff851f9204 _PyEval_EvalFrameDefault (libpython3.7m.so.1.0)
                #42 0x00007fff852331c4 PyEval_EvalFrameEx (libpython3.7m.so.1.0)
                #43 0x00007fff85303928 _PyEval_EvalCodeWithName (libpython3.7m.so.1.0)
                #44 0x00007fff85303ab4 PyEval_EvalCodeEx (libpython3.7m.so.1.0)
                #45 0x00007fff85303b2c PyEval_EvalCode (libpython3.7m.so.1.0)
                #46 0x00007fff853f2b90 n/a (libpython3.7m.so.1.0)
                #47 0x00007fff853f3c10 PyRun_FileExFlags (libpython3.7m.so.1.0)
                #48 0x00007fff8541f648 PyRun_SimpleFileExFlags (libpython3.7m.so.1.0)
                #49 0x00007fff8541fc04 PyRun_AnyFileExFlags (libpython3.7m.so.1.0)
                #50 0x00007fff85424fe8 n/a (libpython3.7m.so.1.0)
                #51 0x00007fff854254ec _Py_UnixMain (libpython3.7m.so.1.0)
                #52 0x00000001345c0858 main (python3.7)
                #53 0x00007fff84d94b78 generic_start_main.isra.0 (libc.so.6)
                #54 0x00007fff84d94d84 __libc_start_main (libc.so.6)
[root@localhost ~]#

Comment 1 Chris Murphy 2019-03-27 23:33:19 UTC
abrt wasn't installed at the time of the crash, and doesn't want to run:
Mar 27 17:29:11 localhost.localdomain systemd[1]: ABRT Automated Bug Reporting Tool is not active.
Mar 27 17:29:11 localhost.localdomain systemd[1]: Dependency failed for Install ABRT coredump hook.
Mar 27 17:29:11 localhost.localdomain systemd[1]: abrt-ccpp.service: Job abrt-ccpp.service/start failed with result 'dependency'.
[root@localhost ~]# 

So here's the coredumpfile, URL should be valid for a little while
https://drive.google.com/open?id=1LONvpu-dtYvzA3FKL-fJTNxhbtPGO8nh

Comment 2 Jaroslav Rohel 2019-10-14 07:45:56 UTC
There can be more reason why the file is not opened. I think that the file was missing. Eg other DNF process or dnfautomatic cleans/refresh the cache. That is known issue.

I'm not able solve the bug now.
I made PR https://github.com/rpm-software-management/libdnf/pull/810 to get more information why the file was not opened.

If you are able to reproduce the problem with new version of libdnf (with the PR above) then reopn the bug. And send new message (dnf log file).


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