RPM Community Forums

Mailing List Message of <rpm-users>

Fwd: rpmdb: c_put: attempt to modify a read-only tree

From: Jeff Johnson <n3npq@mac.com>
Date: Tue 11 May 2010 - 01:22:06 CEST
Message-id: <3F783E89-CF24-42DB-905D-CD696CBEFBF5@mac.com>
I replied privately but perhaps useful.

Begin forwarded message:
>> 
>> ----- Forwarded message from Marc MERLIN <marc_rpm@merlins.org> -----
>> 
>> From: Marc MERLIN <marc_rpm@merlins.org>
>> To: rpm-users@rpm5.org
>> Subject: rpmdb: c_put: attempt to modify a read-only tree
>> 
>> After upgrading rpm on a system from 4.0.2 to 4.4.1, I'm seeing this:
>> 
>> muny20:/lib# rpm -e --test sed
>> rpmdb: c_put: attempt to modify a read-only tree
>> error: db4 error(13) from dbcursor->c_put: Permission denied
>> rpmdb: c_put: attempt to modify a read-only tree
>> error: db4 error(13) from dbcursor->c_put: Permission denied
>> rpmdb: c_put: attempt to modify a read-only tree
>> error: db4 error(13) from dbcursor->c_put: Permission denied
>> error: Failed dependencies:
>>       sed is needed by (installed) console-tools-19990829-34.i386
>>       sed is needed by (installed) pam-0.74-22.i386
>>       /bin/sed is needed by (installed) initscripts-5.84-1.i386
>> 
> 
> Hmmm ... I personally have never seen this error msg that I recall ...
> 
> what platform and vendor distro?
> 
> what version of rpm is in use for upgrade, 4.0.2 or 4.4.1?
> 
> what version of Berkeley DB? These are really old RPM versions and I've forgotten details.
> 
> (aside)
> Hmmm, I'd skip rpm-4.4.1 (was it SuSE who used? I fergit ...) not
> my best effort ... and 4.4.2 should be easy to upgrade to.
> 
> 
>> It doesn't quite seem to stop rpm from working, but it's worrisome and I can't
>> quite find what it means.
>> 
> 
> There's gonna be data loss (because db->c_put was involved).
> 
> But --rebuilddb afterwards will fix all the indices (except for Packages,
> do rpm -qa | sort before and after looking for packages that go *POOF*).
> 
> Note also that rpm checks _EVERY_ return code from Berkeley DB, so
> you don't have to get too paranoid about mysterious internal crud.
> You should get an error msg as above for all anomolies.
> 
> I'd also look carefully for something really odd, like rpm reading some
> fishy configuration (strace -e open should catch), or chattr(1) on a database file,
> or an rpmdb on some non ext2/ext3 file system.
> 
> hth
> 
> 73 de Jeff
Received on Tue May 11 01:22:31 2010
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.