[SLE] yast: "Another process is accessing..."
Hi, all! i'm new to this list, and i apologize if this is not the place for this type of question (if it is, please kindly ignore me or point me to the proper place). i'm using OpenSuse 10.1 and have the following problem: Some days ago i tried to add an ftp site as an Installation Source using yast. Each time i tried (3 or 4 times) yast hung (i waited for 5+ minutes each time) and i had to kill it. At some point it got in a bad state, and now each time i try to use yast's Software Management or Installation Source features i get the following error message: "Another process is accessing the package database. Package management will not work!" There are no running yast processes except for the one i'm getting the error in. i can find no stale lock files for older instances. Other than the inability to add/remove software (or package repositories) via yast my box is working just fine. i am able to un/install RPMs directly from the command line. Can someone please tell me what file(s) i need to nuke to get rid of this error? i've tried re-installing the yast core RPMs, but that hasn't helped. i don't mind hosing my current yast configuration in order to get around this problem. Note: i am an advanced user, so don't be afraid to suggest an ugly hack, nor do you need to feel compelled to dumb down an answer for me. :) Many thanks in advance for any tips... -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On 7/13/06, stephan beal <stephan@s11n.net> wrote:
Hi, all!
i'm new to this list, and i apologize if this is not the place for this type of question (if it is, please kindly ignore me or point me to the proper place).
i'm using OpenSuse 10.1 and have the following problem:
Some days ago i tried to add an ftp site as an Installation Source using yast. Each time i tried (3 or 4 times) yast hung (i waited for 5+ minutes each time) and i had to kill it. At some point it got in a bad state, and now each time i try to use yast's Software Management or Installation Source features i get the following error message:
"Another process is accessing the package database. Package management will not work!"
There are no running yast processes except for the one i'm getting the error in. i can find no stale lock files for older instances.
Other than the inability to add/remove software (or package repositories) via yast my box is working just fine. i am able to un/install RPMs directly from the command line.
Can someone please tell me what file(s) i need to nuke to get rid of this error? i've tried re-installing the yast core RPMs, but that hasn't helped. i don't mind hosing my current yast configuration in order to get around this problem.
Note: i am an advanced user, so don't be afraid to suggest an ugly hack, nor do you need to feel compelled to dumb down an answer for me. :)
Many thanks in advance for any tips...
-- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
Stephan, I asked the same question a week or two ago. Got no answer. I had the luxury of trying a reboot. It cleared the problem for me, so the locking is either in RAM or the lock file is cleared by the init scripts. If rebooting is not an option, you could look at the IPC stuff and see if it is a memory resident lock. (ipcs will give you status) ie. maybe they are using a shared memory segment or a semaphore to control the lock. I just looked on my pretty vanilla server and I have 4 shared memory segments and 3 semaphores. I don't really know what they are being used for. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 13 July 2006 18:25, Greg Freemyer wrote:
I had the luxury of trying a reboot. It cleared the problem for me, so the locking is either in RAM or the lock file is cleared by the init scripts.
The lock file is actually /var/run/zypp.pid, if you're sure nothing is working on it at the moment you should be able to delete it and start working -- Ut supra post festum sunt obscura -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 13 July 2006 18:45, Anders Johansson wrote:
On Thursday 13 July 2006 18:25, Greg Freemyer wrote:
I had the luxury of trying a reboot. It cleared the problem for me, so the locking is either in RAM or the lock file is cleared by the init scripts.
The lock file is actually /var/run/zypp.pid, if you're sure nothing is working on it at the moment you should be able to delete it and start working
@Greg: yes, i have the luxury of being able to reboot, but... @Anders: zypp.pid was it. Thanks very much to both of you! :) -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On Thursday 13 July 2006 12:15, stephan beal wrote:
"Another process is accessing the package database. Package management will not work!"
I just had a long session with Yast2 and was trying to update the installation sources list..... After messing around with that for awhile, I tried to install a package from the DVD. It attempted to load but at the very end I got that same message. Tried again and got the same message.... So I quit entirely out of YAST2, checked to see if any parts of Yast were still running, and they weren't. Went back into Yast and this time the package loaded ok. Yast has some really, really serious problems - yet. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (4)
-
Anders Johansson -
Bruce Marshall -
Greg Freemyer -
stephan beal