Version-Release number of selected component: dnf-0.4.9-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/dnf -v makecache timer crash_function: solvable_copy_cb executable: /usr/bin/python2.7 kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 solvable_copy_cb at /lib64/libsolvext.so.0 #1 repodata_search at /lib64/libsolv.so.0 #2 repo_add_rpmdb at /lib64/libsolvext.so.0 #3 repo_add_rpmdb_reffp at /lib64/libsolvext.so.0 #4 hy_sack_load_system_repo at /lib64/libhawkey.so.0 #5 load_system_repo at /usr/lib64/python2.7/site-packages/hawkey/_hawkeymodule.so #6 PyEval_EvalFrameEx at /lib64/libpython2.7.so.1.0 #7 PyEval_EvalCodeEx at /lib64/libpython2.7.so.1.0 #8 PyEval_EvalFrameEx at /lib64/libpython2.7.so.1.0 #9 PyEval_EvalCodeEx at /lib64/libpython2.7.so.1.0
Created attachment 842806 [details] File: backtrace
Created attachment 842807 [details] File: cgroup
Created attachment 842808 [details] File: core_backtrace
Created attachment 842809 [details] File: dso_list
Created attachment 842810 [details] File: environ
Created attachment 842811 [details] File: exploitable
Created attachment 842812 [details] File: limits
Created attachment 842813 [details] File: maps
Created attachment 842814 [details] File: open_fds
Created attachment 842815 [details] File: proc_pid_status
Created attachment 842816 [details] File: var_log_messages
hmmm, there's no coredump really in here and I've been so far unable to map back the traceback's addresses to source files/lines. One thing that stands out: the crash occurs in solvable_copy_cb() which is what got affected by mls last patch in the latest build, a8e47f15b81002c721fe164885d809562c5d3e7a, the one that fixes issues with package checksums if updating rpmdb cache with repo_add_rpmdb_reffp(). Michael, is it possible the issue is in this?
here's a better backtrace: https://retrace.fedoraproject.org/faf/reports/310947/ That would indicate the crash in dirpool_parent() (still indirectly called from solvable_copy_cb)
reporter, we might need the full coredump file. can you please provide us one, by doing: $ ulimit -c unlimited $ /usr/bin/python /usr/bin/dnf -v makecache This will create (in case of crash) core.* file in the local directory, I'd like to ask you to upload it somewhere and paste the link here, if possible. Thank you.
related abrt issue why the backtrace is no good here: bug 1047980
I don't think it has anything to do with the latest change, as this is about the filelist, not a checksum. My guess is that the old solv file is corrupt, the directory index of one of the files seems to be out of the valid range.
Not sure what to do here, we shouldn't crash on any input .solv file, but it's too rare (possibly because of hw error etc.) to be worth actively chasing and fixing at the moment. Let's just keep it open for a record, perhaps more users will experience this. Also, reporter, if you still see this: can you upload /var/cache/dnf/x86_64/20/@System.solv to this? Thank you.
similar bug with somewhat a better traceback: bug 1051917.
uploaded the core http://akozumpl.fedorapeople.org/core.9039
scratch comment 19, wrong bug.
Discussing this with Michael we decided the best course of action for now is eliminate the possibility of keeping an unfinished solv file in the cache. To prevent that we will provide functionality that first stores the generated solv file into a temporary file and only when that is successfully finished rename it to the final name.
Fixed upstream by 9290a1c, will be part of the 0.4.10 release.
hawkey-0.4.10-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/hawkey-0.4.10-1.fc20
Package hawkey-0.4.10-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing hawkey-0.4.10-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-2700/hawkey-0.4.10-1.fc20 then log in and leave karma (feedback).
*** Bug 1066783 has been marked as a duplicate of this bug. ***
hawkey-0.4.11-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/hawkey-0.4.11-1.fc20
hawkey-0.4.10-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
hawkey-0.4.11-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1051812 has been marked as a duplicate of this bug. ***
(clearing needinfo)