Re: rpm fatal error on osx el capitan

[Anders F Björklund]

Jacques Knipper wrote:

> Indeed I'm talking about v5.4.15.
> I didn't try with the --rpmdbdebug yet but I will, thanks.
> The problem happen with every rpm.
> I am able to rebuild our rpms with the rpmbuild, but I cannot install them, 
> an I think it's because of an issue with Berkeley DB.

FWIW, the issue was reproducible on Mavericks too. You need to install 
something to see it, though...

So the default test case a) looks a bit broken and b) doesn't actually test 
installing and erasing ?

%_topdir#{testpath}/var/lib/rpm

I think it is something with the (lack of) configuration, that is getting the 
rpmdb in a sad state.

--anders__
RPM Package Managerhttp://rpm5.org
User Communication List rpm-users@rpm5.org

Re: rpm fatal error on osx el capitan

[Jeffrey Johnson]

> On Sep 24, 2015, at 9:40 AM, Jacques Knipper  
> wrote:
> 
> 
> When we tried to install any rpm with "sudo rpm -ivh ...", the command crash 
> with an error "error: db3cput:db3.c:1461: dbcursor->put(-30973): BDB0087 
> DB_RUNRECOVERY: Fatal error, run database recovery”.
This is the on;y trpotyrd retort msg.

Unfortunately, the problem in need of solving happened on the previous rpm
invocation, not this invocation.

Note that rpm-5.4.15 already automates the fixup necessary for “… run database 
recovery.”
so there is something else systematically (i.e. like configuration) that 
prevented the
automatic mixup from succeeding.

hth

73 de Jeff

Re: rpm fatal error on osx el capitan

[Jeffrey Johnson]

>> 
>> When we tried to install any rpm with "sudo rpm -ivh ...", the command crash 
>> with an error "error: db3cput:db3.c:1461: dbcursor->put(-30973): BDB0087 
>> DB_RUNRECOVERY: Fatal error, run database recovery”.
> This is the on;y trpotyrd retort msg.

This is the only reported error msg.

> 
> Unfortunately, the problem in need of solving happened on the previous rpm
> invocation, not this invocation.
> 
> Note that rpm-5.4.15 already automates the fixup necessary for “… run 
> database recovery.”
> so there is something else systematically (i.e. like configuration) that 
> prevented the
> automatic mixup from succeeding.
> 
> hth
> 
> 73 de Jeff

Re: rpm fatal error on osx el capitan

[Jeffrey Johnson]

> On Sep 30, 2015, at 4:32 PM, Anders F Björklund  wrote:
> 
> Jacques Knipper wrote:
> 
>> Indeed I'm talking about v5.4.15.
>> I didn't try with the --rpmdbdebug yet but I will, thanks.
>> The problem happen with every rpm.
>> I am able to rebuild our rpms with the rpmbuild, but I cannot install them, 
>> an I think it's because of an issue with Berkeley DB.
> 
> FWIW, the issue was reproducible on Mavericks too. You need to install 
> something to see it, though...
> 
> So the default test case a) looks a bit broken and b) doesn't actually test 
> installing and erasing ?
> 
> %_topdir  #{testpath}/var/lib/rpm
> 
> I think it is something with the (lack of) configuration, that is getting the 
> rpmdb in a sad state.
> 

Hmmm … I’d likely concur lack of configuration (and that rpmdb is overly 
complex).

Meanwhile:

Is this a segfault or an assertion failure using rpm?

I haven’t seen the exact error message ….

If the problem is a segfault, then there may be an assertion missing someplace.

And if some assertion exit is common (which is likely the case imho)
to an out-of-box misconfigured experience, perhaps an exit by invoking an
opaque script to display a per-platform tuned message might assist.

Of course the opaque script generation through AutoFu may just introduce
Yet Mode Configuration failures, sigh.

Is the problem a segfault or an assertion failure?

73 de Jeff
> --anders__
> RPM Package Managerhttp://rpm5.org
> User Communication List rpm-users@rpm5.org

__
RPM Package Managerhttp://rpm5.org
User Communication List rpm-users@rpm5.org

Re: rpm fatal error on osx el capitan

[Jacques Knipper]

After brew update, rpm upgrade, db reset and reboot, it's now working 
like a charm.


Thanks again :)







Jacques Knipper
Software Engineer
t. +49 7851 91 96 23 
f. +49 7851 73 57 6 




DALIM SOFTWARE GmbH
Strassburger Strasse 6
77694 Kehl, Germany
www.dalim.com 




Geschäftsführer: Dr. Carol Werlé (CEO)
Vorsitzender des Aufsichtsrats (Chairman): Jim D. Salmon
Ust-IdNr. (VAT-Nr.): DE 195 290 616
Sitz der Gesellschaft (Location): Kehl, Amtsgericht Freiburg, HRB 371620

Re: rpm fatal error on osx el capitan

[Jacques Knipper]

Indeed I'm talking about v5.4.15.
I didn't try with the --rpmdbdebug yet but I will, thanks.
The problem happen with every rpm.
I am able to rebuild our rpms with the rpmbuild, but I cannot install 
them, an I think it's because of an issue with Berkeley DB.


Thanks for your answer I will try again tomorrow and see If I can get 
further.








Jacques Knipper
Software Engineer
t. +49 7851 91 96 23 
f. +49 7851 73 57 6 




DALIM SOFTWARE GmbH
Strassburger Strasse 6
77694 Kehl, Germany
www.dalim.com 




Geschäftsführer: Dr. Carol Werlé (CEO)
Vorsitzender des Aufsichtsrats (Chairman): Jim D. Salmon
Ust-IdNr. (VAT-Nr.): DE 195 290 616
Sitz der Gesellschaft (Location): Kehl, Amtsgericht Freiburg, HRB 371620

Re: rpm fatal error on osx el capitan

[Anders F Björklund]

Jacques Knipper wrote:

> I already know that brew and rpm are not officially supported on latest 
> version of osx for now...

Whatever official support is, I don't think it is happening on *any* version of 
OS X. But that particular system version is not even released yet, for another 
week or so...

> I noticed when I installed rpm with brew that rpm is suffixed with 
> "_el_capitan_bottle", so I allow myself to ask you about an issue I'm facing, 
> maybe someone is working on it :)

Can't say I have any plans to work on it. But the homebrew build is pretty 
standard, so it should be more or less the same as just building it from 
release (5.4.15) ?

> When we tried to install any rpm with "sudo rpm -ivh ...", the command crash 
> with an error "error: db3cput:db3.c:1461: dbcursor->put(-30973): BDB0087 
> DB_RUNRECOVERY: Fatal error, run database recovery".
> 
> I tried to remove any db files and run rebuilddb but that's not better...

Sounds like you have a problem with Berkeley DB ? It seems that you (i.e. brew) 
is using version 6.1.26.

You can also run with additional -v flags, to get some more debugging 
information. And also --rpmdbdebug.

> We also tried to install both of rpm and berkeley-db in debug to step in, but 
> we do not find any relevant information that help us to get out of this bad 
> situation...

Seems like you didn't get far enough to really create a situation, if the first 
rpm installation crashed on you ?

> Have you any idea why we are able to install all the stuff but not using it?

Depends on what you are trying to use it for. Did you plan on doing anything 
else, after unpacking with brew ?



I think the only scenario being tested by the build bot, is being able to make 
an .rpm and possibly to inspect an empty db:

https://github.com/Homebrew/homebrew/blob/master/Library/Formula/rpm.rb#L108

A more extensive test, like installing and erasing packages is probably a good 
idea - *if* one is planning to use rpm for that...

Seems like my /var/lib/rpmbuild hack didn't even make it to the next commit 
(f386026)

--anders