Bug 986794
Summary: | [abrt] yum-3.4.3-100.fc19: sqlitecachec.py:46:getPrimary:TypeError: Can not create removals trigger: disk I/O error | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ahmed Noor Kader Mustajir Md Eusoff <sir.ade> | ||||||||
Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> | ||||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 19 | CC: | admiller, ffesti, firas.alkafri, packaging-team-maint, sir.ade, tim.lauridsen, zpavlas | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:4bca479f01c44664db9369efc6653dbb6ecdb91e | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-07-25 08:47:05 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Ahmed Noor Kader Mustajir Md Eusoff
2013-07-22 06:22:03 UTC
Created attachment 776742 [details]
File: backtrace
Created attachment 776743 [details]
File: core_backtrace
Created attachment 776744 [details]
File: environ
The most likely cause of this is full disk. There was enough space to create an empty sqlite database and tables, but we ran out of space when creating triggers. Please could you check that /var/cache is indeed close to full? there are enough space,more than 20 gb free space Sorry I'm asking but have you checked the right partition? (/var is usually mounted on a different partition than /home or /).. This is clearly triggered in yum-metadata-parser code, when DB schema is being created, nothing Yum specific. If the free space is really not a problem, maybe the existing database cache is broken (a sqlite3 bug, maybe..) Please backup /var/cache/yum/x86_64/19/adobe-linux-x86_64/gen/primary.xml.sqlite (if it's small, maybe zip it and attach to the BZ so I can check), then unlink it and try running Yum again. I using the same partition /var and /, and i just clean all info you requested using yum clean all so I can't give you the file Okay, thanks. If this happens again, please upload the file and reopen. |