[ATrpms-users] problems using smart, rpm

[Mark Wormgoor]

Axel Thimm wrote:
> Hi,
> 
> On Sun, Oct 29, 2006 at 11:36:21AM +0100, Mark Wormgoor wrote:
>> Marcel Janssen wrote:
>>> On Sunday 29 October 2006 09:45, Axel Thimm wrote:
>>>> Try rm -f /var/lib/rpm/__*, that's all what a reboot does.
>>> OK.
>>>
>>>> I'm using smart of FC6 just fine, though.
>>> I'll keep an eye on what is happening. Last night also some cron jobs didn't 
>>> start correctly. This seems totally unrelated to the smart issues though.
>>> After I rebooted things seem fine again.
>> I also suffered from a lot of smart/rpm problems on my FC5 box this week and 
>> I still haven't figured out what caused it. It seems like smart kept 
>> corrupting my rpm database (happened over night at least twice and a couple 
>> more times when I was trying to fix it). I've rebuilt my rpm db at least 10 
>> times and removed all smart data (except for config) at least twice.
>>
>> It seems better now, but I don't know what caused it.
> 
> There were no updates in FC5 that would affect smart and/or rpm, at
> least I didn't spot any. But given that there are now two reports on
> this, something seems broken somewhere.
> 
> Mark, could you check whether anything suspicious was upgraded on the
> FC5 box before the corruption?  Something that smart/rpm depends on
> like beecrypt/sqlite/python etc.?
> 
> A bit far fetched, but perhaps kernel 2.6.18 is causing rpm(lib)
> headaches.

Very possible. The only updates that I see that can have any impact are
kernel (2.6.18) and libsepol. And for that last one, I don't have
selinux enabled, but the selinux libs are linked in just about everywhere.

> Even farther fetched: Perhaps during your nightly smart updates yum
> kicked in, too? One can use yum/apt/smart/rpm randomly at will, but
> not simultaneously. And if a smart download goes into the night the
> 4:00 AM cron scripts from yum might cooperate on the same rpmdb which
> can cause issues.

Nope, I only have smart enabled. I don't even have apt or yum installed.

Kind regards,

Mark