Bug 607049
Summary: | Manual yum update fails: sqlite3 error and pidfile error | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rich Mattes <richmattes> |
Component: | yum | Assignee: | Seth Vidal <skvidal> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | ffesti, james.antill, maxamillion, pmatilai, tim.lauridsen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-23 11:26:12 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: |
Description
Rich Mattes
2010-06-23 03:21:02 UTC
What does the command: ls -l /var/run ...say? I'm suspicious that you might have some FS corruption, if so try rebooting and running fsck. To "fix" the history problem you can run: yum history new I think you're right. After I reported this, I went about doing some development, and cmake started throwing errors that it couldn't write to /tmp. After confirming that I couldn't create any new files in /tmp as any user (even after some generous chmodding) I rebooted and things seemed to start working again (the yum transaction completed, and /tmp was writeable again). Sorry for the noise. |