On Monday 24 July 2006 09:34, stephan beal wrote:

That problem was the reason i subscribed to this list ;).

IIRC the lock file you need to remove is /var/run/zypp.pid.

Hi Stephan, 10.0 predates the new updater system delivered with 10.1, but you've got the right idea. :-) Lucky, First verify that you really have killed all yast processes... run 'top' in a shell (or in the alternate console.) When you're certain there's nothing holding the rpm database open, look for an orphaned 'lock' file under /var/lib/rpm and delete it. If the lock-up occurred with the last set released (I think) yesterday for 10.0, there was one update for the kernel plus two or three more. Try running YOU and deselecting everything /but/ the kernel update, allow that update to be applied, reboot (necessary for kernel updates) and then run YOU again to apply the remaining patches. In my experience, you need to apply kernel patches independently of any other patches, reboot and proceed with the rest to avoid problems like the one you experienced. hth & regards, Carl -- 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 Monday 24 July 2006 10:15 am, Lucky Leavell wrote:

On Mon, 24 Jul 2006, Carl Hartung wrote:

...

On Monday 24 July 2006 09:34, stephan beal wrote:

...

That problem was the reason i subscribed to this list ;).

IIRC the lock file you need to remove is /var/run/zypp.pid.

Hi Stephan,

10.0 predates the new updater system delivered with 10.1, but you've got the right idea. :-)

Lucky,

First verify that you really have killed all yast processes... run 'top' in a shell (or in the alternate console.)

When you're certain there's nothing holding the rpm database open, look for an orphaned 'lock' file under /var/lib/rpm and delete it.

I checked and no yast processes are running. I also was unable to locate zypp.pid or and lock files in /var/lib/rpm recognizable as such but it still fails with the same error on the first patch. In this case it is the PHP5 security patch. If I skip this patch, it will get the same error on the next patch. (This system hasn't updated in quite a while and there are quite a few patches.)

I am unable to deselect any patches marked with ">" but can "Skip" the kernel patch when I get the kernel update warning dialog box.

I am using the character screen (not KDE). Look at /var/run/yast.pid. Make sure YaST is not running, and delete this file if it exists. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

-- 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 Monday 24 July 2006 10:36 am, Carl Hartung wrote:

I'd have thought if YOU launches and doesn't 'hiccup' until rpm attempts to access it's database (does it call it "Packages index"?), it'd be an rpm lock that's orphaned. Is this wrong? When YOU 'hangs' (or is killed exclusive of rpm) does it leave a yast.pid instead? I agree. Lucky just posted a more detailed explanation.

-- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -- 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 Monday 24 July 2006 10:53, Lucky Leavell wrote:

I would try rebooting but this is a mail server and will have to wait until evening...

Anything interesting from 'dmesg' (or review /var/log/messages)? Carl -- 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 Mon, 24 Jul 2006, Jerry Feldman wrote:

However, can you download a patch manually and install it with the command line rpm command.

I just tried to install php4-session with rpm -U --force /media/dvdrecorder/suse/i586/php4-session-4.4.0-6.i586.rpm and receive the same lock message on the /var/lib/rpm/Packages file. Is these some way to remove and rebuild the Packages file or the entire rpm database? Thank you, Lucky -- 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 Mon, 24 Jul 2006, Carl Hartung wrote:

On Monday 24 July 2006 12:20, Lucky Leavell wrote:

...

Is these some way to remove and rebuild the Packages file or the entire rpm database?

As root, 'rpm --rebuilddb' ('man rpm' for more options) but, before doing that, did you happen to see anything interesting or more informative from running 'dmesg' or inspecting /var/log/messages? IMHO, it'd be nice to track down and rid the system of any orphaned lock files and/or verify there aren't any <gasp> filesystem problems.

dmesg produces too much volume to be read; /var/log/messages has no entries for "rpm" or "yast". Again, I haven't found ANY lock files in /var/run or /var/lib/rpm. Is there anyplace else I should look? (Of course, I could do a fiind for "*.lock" ...) Thank you, Lucky -- 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 Mon, 24 Jul 2006, Carl Hartung wrote:

On Monday 24 July 2006 13:20, Lucky Leavell wrote:

...

dmesg produces too much volume to be read; /var/log/messages has no entries for "rpm" or "yast". Again, I haven't found ANY lock files in /var/run or /var/lib/rpm. Is there anyplace else I should look? (Of course, I could do a fiind for "*.lock" ...)

It's a good sign if you're not seeing any hd access related errors, :-) I wish I knew for certain where rpm puts the lock file (maybe someone else will chime in?)

If you get tired of waiting and/or looking for it, you could always try the rpm database rebuild. That's probably what my approach would be.

Good luck!

I did the rebuild and that apparently cleared the lock file. Now I am trying to resolve all the other problems. -- 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