Bug 374961
| Summary: | Cannot run software updater at always complains about another application accessing software information | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | NILMONI DEB <ndeb> | ||||
| Component: | pirut | Assignee: | Jeremy Katz <katzj> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 8 | CC: | james.antill, robatino | ||||
| 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: | 2007-11-10 21:06:46 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
NILMONI DEB
2007-11-10 18:33:27 UTC
Created attachment 254021 [details]
software updater complaining about rpm db access
I actually had to manually kill the process -> /usr/bin/python -tt /usr/libexec/yum-updatesd-helper --check .... to allow a new instance of the software updater to start. After it did start fine, it now hangs during "retrieving software information". This hang happens for the software add/removal tool (package manager) as well. Something is really wrong with these tools since command-line rpm works fine. I disabled yum-updatesd in system-config-services and the problem still continues. The same problem exists with command-line yum. (PID 2552 was yum-updatesd-helper which also belongs to the yum-updatesd package.) The component for this bug should be changed from pirut to yum-updatesd. Existing lock /var/run/yum.pid: another copy is running as pid 2552. Another app is currently holding the yum lock; waiting for it to exit... Another app is currently holding the yum lock; waiting for it to exit... Another app is currently holding the yum lock; waiting for it to exit... Another app is currently holding the yum lock; waiting for it to exit... Another app is currently holding the yum lock; waiting for it to exit... Another app is currently holding the yum lock; waiting for it to exit... Another app is currently holding the yum lock; waiting for it to exit... (over and over until yum-updatesd is kill'ed and yum-updatesd-helper is kill'ed with -9, since nothing else works). Also please change the priority to high or urgent. This even prevents using yum or pirut from being used for updates, unless instructions are given separately for killing the renegade processes first, so just releasing updated packages won't be enough. This appears to be a duplicate of bug #374801. After stopping the yum-updatesd thru system-config-services, neither the software update or install/removal tool would start initially. They would complain about another process accessing the software db. However, after waiting a long time (about an hour after stopping yum-updatesd) I could finally start the software install/removal tool but it got hung (just as described in comment 2). For all practical purposes, fedora 8 should never have been released as a stable distro given its pre-alpha state of affairs. (In reply to comment #5) > Also please change the priority to high or urgent. I don't think ordinary users (like me) can do that. I had already set the severity to urgent. > This even prevents using > yum or pirut from being used for updates, unless instructions are given > separately for killing the renegade processes first, so just releasing updated > packages won't be enough. The problem created by yum-updatesd running at startup has been around for a year now (see http://forums.fedoraforum.org/showthread.php?t=142170 ) but at least on fedora 7, I could install/remove/update without problems. Fedora 8 is a step backwards. After stopping the yum-updatesd thru system-config-services, neither the software update or install/removal tool would start initially. They would complain about another process accessing the software db. However, after waiting a long time (about an hour after stopping yum-updatesd) I could finally start the software install/removal tool but it got hung (just as described in comment 2). For all practical purposes, fedora 8 should never have been released as a stable distro given its pre-alpha state of affairs. (In reply to comment #5) > Also please change the priority to high or urgent. I don't think ordinary users (like me) can do that. I had already set the severity to urgent. > This even prevents using > yum or pirut from being used for updates, unless instructions are given > separately for killing the renegade processes first, so just releasing updated > packages won't be enough. The problem created by yum-updatesd running at startup has been around for a year now (see http://forums.fedoraforum.org/showthread.php?t=142170 ) but at least on fedora 7, I could install/remove/update without problems. Fedora 8 is a step backwards. Sorry for the double post, but the previous comments (6 and 7) collided and for some strange reason the bugzilla page started shaking abnormally (I am using kde/konqueror). I kept clicking and somehow managed to stop the shaking of the konqueror tab (no idea if this is a konqueror bug or a bugzilla problem). *** This bug has been marked as a duplicate of 374801 *** *** This bug has been marked as a duplicate of 374801 *** |