|
From: Michael T. <mic...@gm...> - 2018-11-07 15:22:06
|
I had a similar experience when I installed a new SSD. My advice: anything other that starting with a fresh tree and your most recent backup is just wasting time, and yes, you may have to re-install stuff. My debacle affected media paths as well, if I remember correctly. All good now, though, and it has made me a better person in as far as I do backups all the time! Mike On Wed, 7 Nov 2018 at 15:05, Paul Culley <pau...@gm...> wrote: > It seems likely that the system update did something to the Berkeley > database. Unless you have specifically disabled backups, Gramps should > have made a backup the last time you closed it. > > You might try starting Gramps, and then dismiss the error dialog, and use > the Family tree manager to create a new tree. And then import the most > recent backup file. "Edit/Preferences/Family Tree/Backup path" should tell > you where to find the backup. > > If Gramps cannot create a new Family tree, then you may have to reinstall > from the .deb file again. Or use Preferences to change to an SQLite > database (which we think should be less likely to have problems like this). > > If you don't have a backup, Start Gramps again, and close the error window. > You will then have a Gramps instance without a tree, and can try the > built-in repair from the Family Tree manager as shown here: > > > https://gramps-project.org/wiki/index.php?title=Database_Formats#Repairing_a_Corrupt_Database > > Paul C. > > On Wed, Nov 7, 2018 at 8:03 AM Peter Flynn <pe...@si...> wrote: > >> This error message popped up today. >> >> > Gramps has detected a problem in opening the 'environment' of the >> > underlying Berkeley database used to store this Family Tree. The most >> > likely cause is that the database was created with an old version of >> > the Berkeley database program, and you are now using a new version. It >> > is quite likely that your database has not been changed by Gramps. >> >> I did do a system update yesterday or the day before but on checking the >> apt history, libdb was not involved (nor has it been in any previous >> upgrade) so "old version of the Berkeley database program" doesn't seem >> a likely candidate. Is there a way of testing this independently? Or has >> Mint perhaps hidden some of the Berkeley code in a different package? >> >> There were two messages on the console: >> >> > 2018-11-07 12:53:13.685: WARNING: grampletpane.py: line 1160: Failed to >> load gramplets from >> /home/peter/.gramps/gramps50/Gramplets_dashboardview_gramplets.ini because >> While reading from >> '/home/peter/.gramps/gramps50/Gramplets_dashboardview_gramplets.ini' [line >> 15]: option 'detached_width' in section 'Top Surnames' already exists >> >> That sounds like a Gramps error, not a Berkeley.db error. >> >> > 2018-11-07 12:53:36.308: WARNING: write.py: line 634: Error opening db >> environment: (-30973, 'BDB0087 DB_RUNRECOVERY: Fatal error, run database >> recovery -- BDB1544 process-private: unable to find environment') >> >> Does this offer any hints to the devs about what has happened? >> >> What is involved if I want to "run database recovery". >> >> > If possible, you should revert to your old version of Gramps >> >> I'm using 5.0.0. I upgraded to that about four months ago by removing >> the old version installed by Mint from its repos, and installing the >> .deb provided on the Gramps site. That updated the database and it's >> been working fine under 5.0.0 until today. >> >> > and its support software; >> >> What is that? I only know of the Gramps application. >> >> > export your database to XML; close the database; then upgrade again >> > to this version of Gramps and import the XML file in an empty Family >> > Tree. >> That may be possible, but I suspect the older version of Gramps simply >> won't be able to open the database. >> >> > Alternatively, it may be possible to use the Berkeley database recovery >> tools. >> > >> > (-30973, 'BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery >> > -- BDB1544 process-private: unable to find environment') >> >> I'm not familiar with the Berkeley database recovery tools. And I'm not >> yet convinced that this is where the problem lies. >> >> ///Peter >> >> >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> https://gramps-project.org >> > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > https://gramps-project.org |