Re: _rpm.error: rpmdb open failed

On 07/05/2013 09:27 PM, Russell Jones wrote:
>
> On 7/5/2013 2:13 PM, Ljubomir Ljubojevic wrote:
>> On 07/05/2013 07:46 PM, Russell Jones wrote:
>>> Here you go:
>>>
>>> /usr/bin/python /usr/bin/yum -y -c /tmp/genimage.30802.yum.conf
>>> --installroot=/install/netboot/centos5.4/x86_64/rootimg/ --disablerepo=*
>>> --enablerepo=centos5.4-x86_64-0 install bc mysql SysVinit control-center
>> <snip>
>>> jpackage-utils jwhois libutempter sos util-linux openssl097a
>>> kdebase.x86_64
>>>
>>>
>>> Contents of /tmp/genimage.30802.yum.conf:
>>> [centos5.4-x86_64-0]
>>> name=centos5.4-x86_64-0
>>> baseurl=file:///install/centos5.4/x86_64
>>> gpgpcheck=0
>>>
>>>
>>>
>>>
>>> On 7/5/2013 11:29 AM, Chris Kittlitz wrote:
>>>> What command are you executing?
>>>>
>>>>
>>>> On Fri, Jul 5, 2013 at 10:15 AM, Russell Jones <[email protected]
>>>> <mailto:[email protected]>> wrote:
>>>>
>>>>     Hi all,
>>>>
>>>>     Can anyone assist me with understanding what the below error
>>>>     means? This occurs when doing a "yum install" into a rootdir with
>>>>     CentOS 5 packages on a CentOS 6.4 server. This only occurs
>>>>     specifically with CentOS 6.4, if I do the exact same command on
>>>>     CentOS 6.3 it works fine. Thank you in advance for the help!
>>>>
>>
>> Why in hell are you installing 5.x packages on 6.4 system??????
>>
>
>
> Hi Ljubomir,
>
> This is installing into a separate install root (via --installroot), not
> the base system itself. This is then later used to create diskless PXE
> boot images for booting client systems.
>
Ahh, yes, sorry, missed that.

> This works fine on CentOS 6.3, but as you can see generates that error
> on CentOS 6.4. Trying to get the node used to create these images up to
> CentOS 6.4 if I can.

Now when I think of it, I had a same problem with creating LiveCD(?) 5.x 
on CentOS 6.x. The problem is I think that rpm app (or a python?) for 
6.4 is creating newer rpm database that 5.x can not read. can not 
remember what needs to be done, I never got that far, I created some 
issues for my self on a server.

maybe there is an option to force rpm to use older format?

I hope this will direct you to the proper solution.


-- 
Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe

StarOS, Mikrotik and CentOS/RHEL/Linux consultant