The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Server when on automatic update (cron), appear these problems, why?

Discussion in 'General Discussion' started by tekdns, Apr 21, 2003.

  1. tekdns

    tekdns Well-Known Member

    Joined:
    Jun 9, 2002
    Messages:
    100
    Likes Received:
    0
    Trophy Points:
    16
    Hi,

    Server when on automatic updates (cron), then appear these problem;

    "Downloading openssh-3.1p1-6.i386.rpm
    Retrieving http://updates.cpanel.net/pub/rpmup/redhat/7.3/x86/updates/openssh-3.1p1-6.i386.rpm
    Preparing... ##################################################
    openssh ##################################################
    rpmdb: PANIC: Invalid argument
    error: db4 error(-30981) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from dbcursor->c_close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record openssh into Name
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record ssh into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record moduli into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record scp into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record ssh-keygen into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record openssh into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record openssh-3.1p1 into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record CREDITS into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record ChangeLog into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record INSTALL into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record LICENCE into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record OVERVIEW into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record README into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record README.smartcard into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record RFC.nroff into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record TODO into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record WARNING.RNG into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record scp.1.gz into Basenames
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run database recovery
    error: error(-30981) storing record ssh-keygen.1.gz into Basenames
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Group index using db3 - (-30981)
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Requirename index using db3 - (-30981)
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Providename index using db3 - (-30981)
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Dirnames index using db3 - (-30981)
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Requireversion index using db3 - (-30981)
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Provideversion index using db3 - (-30981)
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Installtid index using db3 - (-30981)
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Sigmd5 index using db3 - (-30981)
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Sha1header index using db3 - (-30981)
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Filemd5s index using db3 - (-30981)
    error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Triggername index using db3 - (-30981)
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
    *** PSM_RDB_LOAD: header #634 not found
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
    error: db4 error(-30981) from db->close: DB_RUNRECOVERY:

    ......"



    What is these, and why? How to fix?
     
  2. FWC

    FWC Well-Known Member

    Joined:
    May 13, 2002
    Messages:
    354
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Ontario, Canada
    Try running Rebuild RPM Database under Software in WHM.
     
  3. WeMasterz5

    WeMasterz5 Well-Known Member

    Joined:
    Feb 24, 2003
    Messages:
    361
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Miami
    so does this mean it fixed this error


    D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.18165
    D: creating directory /var/lib/rpmrebuilddb.18165
    D: opening old database with dbapi 3
    D: opening db environment /var/lib/rpm/Packages joinenv
    rpmdb: region error detected; run recovery.
    error: db4 error(-30981) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
    D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
    error: cannot open Packages index
    D: removing directory /var/lib/rpmrebuilddb.18165

    Complete!

    cPanel.net Support Ticket Number:
     
  4. WeMasterz5

    WeMasterz5 Well-Known Member

    Joined:
    Feb 24, 2003
    Messages:
    361
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Miami
    keeping notes from cpanel support ticket in case this works

    It sounds like the rpm db is corrupt, so it might help to log in and
    cd /usr/lib/rpm , rm -f *__*db the rpm -rebuilddb and see if that helps, but there
    could be a lot of things wrong with it.


    root@host1 [/usr/lib/rpm]# rpm -rebuilddb
    rpmdb: region error detected; run recovery.
    error: db4 error(-30981) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
    error: cannot open Packages index



    What does

    ls -al /var/lib/rpm

    show ?

    Does a stack trace help show what is wrong ? (strace -f rpm -rebuilddb)

    root@host1 [/]# ls -al /var/lib/rpm
    total 14012
    drwxr-xr-x 3 rpm rpm 4096 Jul 16 14:53 ./
    drwxr-xr-x 12 root root 4096 Jul 21 19:07 ../
    -rw-r--r-- 1 rpm rpm 2703360 Jul 16 17:45 Basenames
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 15:57 Conflictname
    -rw-r--r-- 1 root root 8192 Jul 16 14:53 __db.001
    -rw-r--r-- 1 root root 1310720 Jul 16 14:53 __db.002
    -rw-r--r-- 1 root root 360448 Jul 16 14:53 __db.003
    -rw-r--r-- 1 rpm rpm 307200 Jul 16 17:45 Dirnames
    -rw-r--r-- 1 rpm rpm 1363968 Jul 16 17:45 Filemd5s
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 17:45 Group
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 17:45 Installtid
    drwxrwx--- 2 rpm mail 4096 May 2 12:19 mail/
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 17:45 Name
    -rw-r--r-- 1 rpm rpm 8667136 Jul 16 17:45 Packages
    -rw-r--r-- 1 rpm rpm 86016 Jul 16 17:45 Providename
    -rw-r--r-- 1 rpm rpm 36864 Jul 16 17:45 Provideversion
    -rw-r--r-- 1 root root 12288 Jul 16 16:02 Pubkeys
    -rw-r--r-- 1 rpm rpm 94208 Jul 16 17:45 Requirename
    -rw-r--r-- 1 rpm rpm 49152 Jul 16 17:45 Requireversion
    -rw-r--r-- 1 rpm rpm 49152 Jul 16 17:45 Sha1header
    -rw-r--r-- 1 rpm rpm 24576 Jul 16 17:45 Sigmd5
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 17:45 Triggername





    root@host1 [/usr/lib/rpm]# rm -f /var/lib/rpm/__db.*
    root@host1 [/usr/lib/rpm]# rpm -rebuilddb


    root@host1 [/usr/lib/rpm]# ls -al /var/lib/rpm
    total 13260
    drwxr-xr-x 3 rpm rpm 4096 Jul 21 19:39 ./
    drwxr-xr-x 12 root root 4096 Jul 21 19:39 ../
    -rw-r--r-- 1 rpm rpm 2646016 Jul 16 17:45 Basenames
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 15:57 Conflictname
    -rw-r--r-- 1 root root 8192 Jul 21 19:39 __db.001
    -rw-r--r-- 1 root root 1310720 Jul 21 19:39 __db.002
    -rw-r--r-- 1 root root 360448 Jul 21 19:39 __db.003
    -rw-r--r-- 1 rpm rpm 307200 Jul 16 17:45 Dirnames
    -rw-r--r-- 1 rpm rpm 1339392 Jul 16 17:45 Filemd5s
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 17:45 Group
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 17:45 Installtid
    drwxrwx--- 2 rpm mail 4096 May 2 12:19 mail/
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 17:45 Name
    -rw-r--r-- 1 rpm rpm 8187904 Jul 16 17:45 Packages
    -rw-r--r-- 1 rpm rpm 90112 Jul 16 17:45 Providename
    -rw-r--r-- 1 rpm rpm 36864 Jul 16 17:45 Provideversion
    -rw-r--r-- 1 root root 12288 Jul 16 16:02 Pubkeys
    -rw-r--r-- 1 rpm rpm 102400 Jul 16 17:45 Requirename
    -rw-r--r-- 1 rpm rpm 49152 Jul 16 17:45 Requireversion
    -rw-r--r-- 1 rpm rpm 49152 Jul 16 17:45 Sha1header
    -rw-r--r-- 1 rpm rpm 24576 Jul 16 17:45 Sigmd5
    -rw-r--r-- 1 rpm rpm 12288 Jul 16 17:45 Triggername

    then from in your WHM do the update apache

    this got me to the atual updates this time with out any errors, I do not know if my case was the same as yours, these notes were taken off my cpanel support ticket, I will update this post after its done compiling

    cPanel.net Support Ticket Number:
     
  5. WeMasterz5

    WeMasterz5 Well-Known Member

    Joined:
    Feb 24, 2003
    Messages:
    361
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Miami
    Waiting for httpd to restart....
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    finished.
    httpd status

    28306 28305 28304 28303 28302 28295



    httpd started ok


    with no errors

    cPanel.net Support Ticket Number:
     
Loading...

Share This Page