Does not seem to install to CentOS 4.3.
INFO - *********************************************************************** INFO - Operating system name: CentOS Linux INFO - Operating system version: 4.3 INFO - *********************************************************************** rpmdb: PANIC: Invalid argument rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->open: DB_RUNRECOVERY: Fatal error, run databas e recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery error: cannot open Name index using db3 - (-30978) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->open: DB_RUNRECOVERY: Fatal error, run databas e recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery error: cannot open Group index using db3 - (-30978) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->open: DB_RUNRECOVERY: Fatal error, run databas e recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery error: cannot open Providename index using db3 - (-30978) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->open: DB_RUNRECOVERY: Fatal error, run databas e recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery error: cannot open Provideversion index using db3 - (-30978) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->open: DB_RUNRECOVERY: Fatal error, run databas e recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery error: cannot open Installtid index using db3 - (-30978) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->open: DB_RUNRECOVERY: Fatal error, run databas e recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery error: cannot open Pubkeys index using db3 - (-30978) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbenv->close: DB_RUNRECOVERY: Fatal error, run dat abase recovery INFO - Installing virtualmin-release package for CentOS Linux 4.3... INFO - Disabling SELinux during installation... /usr/sbin/setenforce: SELinux is disabled % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 10510 100 10510 0 0 105k 0 --:--:-- --:--:-- --:--:-- 410k rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbenv->open: DB_RUNRECOVERY: Fatal error, run data base recovery error: cannot open Packages index using db3 - (-30978) error: cannot open Packages database in /var/lib/rpm warning: virtualmin-release-latest.noarch.rpm: V3 DSA signature: NOKEY, key ID a 0bdbcf9 rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbenv->open: DB_RUNRECOVERY: Fatal error, run data base recovery error: cannot open Packages database in /var/lib/rpm rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbenv->open: DB_RUNRECOVERY: Fatal error, run data base recovery error: cannot open Packages database in /var/lib/rpm INFO - Succeeded. INFO - Installing dependencies using command: /usr/bin/up2date --nox httpd-devel postfix bind spamassassin procmail perl perl-DBD-Pg perl-DBD-MySQL quota iptabl es openssl python mailman subversion ruby rdoc ri mysql mysql-server postgresql postgresql-server rh-postgresql rh-postgresql-server logrotate webalizer php php -domxl php-gd php-imap php-mysql php-odbc php-pear php-pgsql php-snmp php-xmlrpc mod_perl mod_python cyrus-sasl dovecot spamassassin mod_dav_svn cyrus-sasl-gssa pi mod_fastcgi mod_ssl rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbenv->open: DB_RUNRECOVERY: Fatal error, run data base recovery error: cannot open Packages index using db3 - (-30978) error: cannot open Packages database in /var/lib/rpm An error has occurred: exceptions.TypeError See /var/log/up2date for more information INFO - Package Type = rpm
INFO - Installing Virtualmin and all related packages now using the command: INFO - yum -y virtualmin-base Setting up Install Process Setting up repositories Reading repository metadata in from local files Parsing package install arguments No Match for argument: virtualmin-base Nothing to do INFO - Installation of virtualmin-base completed. INFO - Updating all packages to the latest versions now using the command: INFO - yum -y update Setting up Update Process Setting up repositories Reading repository metadata in from local files No Packages marked for Update/Obsoletion INFO - Update completed successfully.
Hey Mike,
This isn't a Virtualmin problem. Your RPM database is corrupted, and it seems to also have something weird going on with the RPM version, too (it's giving db3 and db4 errors--rpm on CentOS 4 should only ever be using db4). Thie corruption can be triggered by a system crash or disk error during RPM use (and it's impossible to trigger it doing anything that the Virtualmin installer does, without a system crash or disk error occurring simultaneously). I don't know what would cause your RPM to be giving both db3 and db4 errors...I suspect a buggy RPM build, or perhaps a partially failed upgrade from CentOS3?
You'll need to rebuild your RPM database:
rpm --rebuilddb
I would also recommend you check out your system pretty thoroughly before relying on it for production work. This looks like it could be an indicator of some kind of pretty serious problem. Either misbehaving hardware or a buggy kernel. At minimum, run a badblocks on all of your disk partitions, and if possible run memtest86 or memtest86+ on it. And run "yum update kernel" or "yum update kernel-smp" to be sure you're running the latest kernel.
--
Check out the forum guidelines!