#472 11-rc3 losing content with gdbm files

Database
closed
DBM (6)
9
2014-08-15
2005-05-04
PypeBros
No

i've been switching to phpwiki 11-rc3 exactly one month
ago after having hard time recovering files that my
previous installation of phpwiki had trashed.

Everything went fine for exactly one month, but
suddenly, this morning, pages got lost.

Several previously-existing pages have the version
number in "pThePage" entry no longer matching the
latest version number in "v1234:ThePage" entry (e.g. i
have pMessageAndPorts telling last version is #3 but
only v2:MessageAndPorts is available)

Moreover, all the pages that have been introduced
past the switch to phpwiki 11-rc3 have lost their
'pThePage' entry aswell.

What the hell is going on ??

Discussion

  • PypeBros

    PypeBros - 2005-05-07

    Logged In: YES
    user_id=45611

    me again. my wiki seems to have magically "self-healed" the
    day after, though some pages are still in an odd state such
    as
    http://clicker.sourceforge.net/wiclicker/index.php/KdsNaming
    which is there but appears as a page to be created from
    other pages
    (http://clicker.sourceforge.net/wiclicker/index.php/KdsDomains)

    What concerns me more is the fact that "recent edits" or
    "recent change" features no longer works and issues the
    following error message:

    Fatal Error:

    lib/WikiDB/backend/dumb/MostRecentIter.php (In template
    'body' < 'html'):28: Error:
    /home/groups/c/cl/clicker/htdocs/wiclicker/lib/WikiDB/backend/dumb/MostRecentIter.php:28:
    : Assertion failed

    Fatal PhpWiki Error

    lib/WikiDB/backend/dumb/MostRecentIter.php (In template
    'body' < 'html'):28: Error:
    /home/groups/c/cl/clicker/htdocs/wiclicker/lib/WikiDB/backend/dumb/MostRecentIter.php:28:
    : Assertion failed

    ErrorManager: error while handling error:

    lib/Request.php:453: Notice: ob_end_flush(): failed to
    delete and flush buffer. No buffer to delete or flush.

     
  • Reini Urban

    Reini Urban - 2005-05-17

    Logged In: YES
    user_id=13755

    The RecentChanges corruption is explainable by the version
    table corruption.

    Do you have a backup?
    Restoring this would heal the corrupt db.

    Otherwise I vaguely remember that some gdbm corruption
    happened before at some installation. I'll try to remember
    where and how we solved this.
    But your server also has some proxy or ob_buffer corruption.
    hmm...

     
  • PypeBros

    PypeBros - 2005-05-17

    Logged In: YES
    user_id=45611

    unfortunately, the most recent backup i have is about one
    month ago, just after i installed 11-rc3 ... that means
    quite a bunch of missing data.

    thanks for the help.

    ps: i don't know too much what's that 'ob_buffer corruption'
    stuff ...

     
  • Reini Urban

    Reini Urban - 2005-05-17

    Logged In: YES
    user_id=13755

    ob_buffer corruption is experienced by a broken html stream
    at the end of the page.
    either caused by the proxy (sf.net) or by php (printf).

     
  • Reini Urban

    Reini Urban - 2005-08-07

    Logged In: YES
    user_id=13755

    I can finally reproduce this on dba and flatfile.
    Mostly it's the OS fault with the db file - not propely
    closed or locked.

    In the meantime I added better error handling to CVS to see
    at last the real cause. dba_insert: PANIC: ...

     
  • Reini Urban

    Reini Urban - 2005-09-11

    Logged In: YES
    user_id=13755

    The fix is to give up gdbm and use a stable dba_handler,
    like berkeley db (db2, db3, db4).

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks