On Jun 6, 2007, at 12:20 PM, Ralf S. Engelschall wrote:
...
1:openpkg
###########################################
[100%]
rpmdb: unknown type: 0
Off the top of my head, unknown type means that something other
than DB_HASH or DB_BTREE (and DB_RECNO etc) was specified
and/or detected while opening.
The type should be displayed when the database is opened
if -vv is passed to rpm.
...
From my point of view I would say the RPM DB got trashed. I don't know
why. And AFAIK you already tried "openpkg rpm --db-rebuild" which
usually goes through a complete dump & restore procedure. As it still
doesn't work, the only possibility seems to be to re-install the
whole instance from scratch. But I've to say that in the last 7 years
I've never seen such a hard crash of the RPM DB, although I myself
have seen a few times where one has to rebuild it with "openpkg rpm
--db-rebuild" in order to resurrect it. I've never seen that a from
scratch re-installation is required. But I've no clue why the RPM
DB is
such trashed here. BTW, have you once run "file /openpkg/RPM/DB/*"?
I'm not quite sure because this is openpkg and AIX, and there
may be differences from what I know.
But the usual corruption diagnosis next step is
cd /var/lib/rpm
/usr/lib/rpm/rpmdb_verify Packages
rpm --rebuilddb -vv
and then test corruption repair with
rpm -qa
You should see something similar to this:
/openpkg/RPM/DB/Basenames: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Conflictname: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Depends: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Dirnames: Berkeley DB (Btree, version 9,
little-endian)
/openpkg/RPM/DB/Filemd5s: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Group: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Installtid: Berkeley DB (Btree, version 9,
little-endian)
/openpkg/RPM/DB/Name: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Packages: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Providename: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Provideversion: Berkeley DB (Btree, version 9,
little-endian)
/openpkg/RPM/DB/Pubkeys: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Requirename: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Requireversion: Berkeley DB (Btree, version 9,
little-endian)
/openpkg/RPM/DB/Sha1header: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Sigmd5: Berkeley DB (Hash, version 8,
little-endian)
/openpkg/RPM/DB/Tags: PalmOS application "openssh
base system applica"
Hmmm, what is this file? Not the magic mis-identify, I understand
what that is.
But I don't recall a Tags index however.
/openpkg/RPM/DB/Triggername: Berkeley DB (Hash, version 8,
little-endian)
Exept for the "little-endian" and perhaps the incorrect "PalmOS [...]"
your output should look similar. If this is not the case, the DB files
got already garbled. If they look ok, please check "openpkg rpm -Vf
/openpkg/lib/openpkg/macros" to make sure the DB related RPM macros
are
not trashed. If this all is ok, well, then a full re-install seems
to be
the only thing one can do here. Although this is really the first time
ever that I see an OpenPKG instance which had to be reinstalled from
scratch...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
OpenPKG http://openpkg.org
User Communication List openpkg-users@openpkg.org
______________________________________________________________________
OpenPKG http://openpkg.org
User Communication List openpkg-users@openpkg.org
