Re: yum -> rpmdb: Locker still has locks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Paul Dickson wrote:
On Fri, 10 Nov 2006 12:53:37 -0700, Paul Dickson wrote:

Yesterday I did a daily devel update via yum (yum-3.0.1).  I appears to
have completed normally except for two messages following the "Complete!"
message:

Complete!
rpmdb: Locker still has locks
error: db4 error(22) from db->close: Invalid argument

glibc-common


Today I'm getting set of:

rpmdb: Lock table is out of available locks
error: cannot open Providename index using db3 - Cannot allocate memory (12)

where Providename changes to other indices (eg Conflictname, Dirnames, etc)


The yum update update is still proceeding inspite of these error messages.


I rebooted, ran "rpm --rebuilddb", and I'm applying today's updates.
From the current run of yum:

[...]
Installing for dependencies:
 glibc                   i686       2.5.90-6         development       5.1 M
 glibc-common            i386       2.5.90-6         development        16 M
 openoffice.org-core     i386       1:2.1.0-2.4      development        89 M
 qt                      i386       1:3.3.7-1.fc7    development       3.6 M

Transaction Summary
=============================================================================
Install 4 Package(s) Update 33 Package(s) Remove 0 Package(s)
Total download size: 165 M
Is this ok [y/N]: y
Downloading Packages:
(1/5): openoffice.org-gra 100% |=========================| 205 kB 00:00 (2/5): openoffice.org-cor 100% |=========================| 89 MB 02:05 (3/5): scribus-1.3.3.5-1. 100% |=========================| 7.6 MB 00:09 (4/5): agg-2.4-3.i386.rpm 100% |=========================| 141 kB 00:00 (5/5): x264-0.0.0-0.2.200 100% |=========================| 415 kB 00:01 Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : yum ####################### [ 1/70] Installing: glibc-common [ 2/70]warning: /etc/default/nss created as /etc/default/nss.rpmnew Installing: glibc-common ####################### [ 2/70] Installing: glibc [ 3/70]warning: /etc/ld.so.conf created as /etc/ld.so.conf.rpmnew
  Installing: glibc                                                [ 3/70]warning: /etc/localtime created as /etc/localtime.rpmnew
  Installing: glibc                                                [ 3/70]warning: /etc/nsswitch.conf created as /etc/nsswitch.conf.rpmnew
  Installing: glibc                                                [ 3/70]warning: /etc/rpc saved as /etc/rpc.rpmorig
  Installing: glibc                        ###################     [ 3/70]warning: /usr/lib/gconv/gconv-modules created as /usr/lib/gconv/gconv-modules.rpmnew
Installing: glibc ####################### [ 3/70] [...]

You probably have about 67 multiple package entries in your rpm database due to the exit. Maybe it will be the other way, you will get three multi-version entries.



Funny how my system can boot and run normally WITHOUT glibc installed. :-)

	-Paul


glibc-common is the rpm causing the rpmdb: Locker still has locks
... error. glibc seemed to install fine for me or remained back at its previous version because of the resulting yum error. I have the below versions currently installed.

 rpm -q glibc
glibc-2.5.90-6
[root@cornette-dell-hdb ~]# rpm -q glibc-common
glibc-common-2.5.90-6

 rpm -qV glibc
Unsatisfied dependencies for glibc-2.5.90-6.i686: glibc-common = 2.5.90-6
[root@cornette-dell-hdb ~]# rpm -qV glibc-common
Unsatisfied dependencies for glibc-common-2.5.90-6.i386: /usr/sbin/build-locale-archive, /usr/sbin/tzdata-update

Jim

--
I have a theory that it's impossible to prove anything, but I can't prove it.

--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]