Results 1 to 4 of 4

Thread: Cannot upgrade to RC2

  1. #1
    Marco NNTP User

    Default Cannot upgrade to RC2

    Hello Everyone.

    I just tried an upgrade to RC2 using "zypper dup" but I am always
    getting the following messages

    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run
    database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
    run database recovery
    error: cannot open Filedigests index using db3 - (-30977)
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
    database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
    database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
    database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
    database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
    run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
    run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
    run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
    run database recovery
    rpmdb: PANIC: fatal region error detected; run recovery
    error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error,
    run database recovery


    Abbrechen, wiederholen, ignorieren? [a/w/i] (a):

    I had the Repositories PackMan and Backports added. After I got that
    error first I deaktivated those two packages, but it didnt help..still
    the same.

    Any ideas?

    Thanks

  2. #2

    Default Re: Cannot upgrade to RC2

    Code:
    sync: DB_RUNRECOVERY: Fatal error, run database recovery
    sync: DB_RUNRECOVERY: Fatal error, run database recovery - Google Search

  3. #3
    Marco NNTP User

    Default Re: Cannot upgrade to RC2

    Am 29.10.2009 18:16, schrieb Akoellh:
    >
    > Code:
    > --------------------
    > sync: DB_RUNRECOVERY: Fatal error, *run database recovery*
    > --------------------
    >
    >
    > 'sync: DB_RUNRECOVERY: Fatal error, run database recovery - Google
    > Search' (http://tinyurl.com/yz977o2)
    >
    >

    Thanks, seems to work until now. I interpreted the error that zypper
    already tried to run the db recovery. But right, the answer was on the
    first google link

  4. #4
    Marco NNTP User

    Default Re: Cannot upgrade to RC2

    Am 29.10.2009 18:16, schrieb Akoellh:
    >
    > Code:
    > --------------------
    > sync: DB_RUNRECOVERY: Fatal error, *run database recovery*
    > --------------------
    >
    >
    > 'sync: DB_RUNRECOVERY: Fatal error, run database recovery - Google
    > Search' (http://tinyurl.com/yz977o2)
    >
    >


    Thanks, seems to work until now. I interpreted the error that zypper
    already tried to run the db recovery. But right, the answer was on the
    first google link

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •