Hi Andi, Thanks for your quick answer.
restore recovery .. those 2 words are really confusingthe Recovery didn't worked at all whatever files removed or not. (here must be a bug somewhere I guess).
Can I help tracking it ?To be able to restore It took me time, tests and nerves before understanding that the file to use with the -r option was binary_backup.tgz (I even unsuccessfully tried to targz existing *.db and DB* files...)
Ok so finally the binary_backup.tgz + -r option did the trick and I think I get now everything back in order.
Now here are some questions : - is the binary_backup.tgz file saved at each closing time ?- why is chandler so sensible with closing without properly quitting ? (I already had some prbs with this before) Shouldn't it only store in database on commit and wait for new modifications ?
- What is this weird concept of environment around the database that can be corrupted AND impossible to recover ?
- Am I wrong If I say that : RECOVER = restore database environment RESTORE = restore database from backup ?- If I want to be sure to backup my data, important files in the profile are :
- *.db and DB* (raw data)
- binary_backup.tgz (backup to restore)
- no use to save database environement thus recover doesn't always
work and no important data in it ?
Again big big thank first for you work on chandler and then to help me with my crash problems. I think I know better how to be sure not to lost my chandler data and that's nice feeling.
Paul Le 11/08/09 16:59, Andi Vajda a écrit :
On Tue, 11 Aug 2009, Paul Girard wrote:Hi there, I am a happy user (for some months now) of Chandler. Today my macbook badly stopped (end of battery without suspend) without closing properly chandler. And now Chandler doesn't start. It gets an exception from recovery : RepositoryRunRecoveryError (see complete error trace below) Ok now what ?I tried to copy paste my profile folder from this morning backup but changenothing...I think my database isn't corrupted since it's from backup and since I wasdoing nothing when the crash happened. Would that be a recovery bug ? Could I bypass recovery process and try access to current database ?Recovery doesn't recover data files, it recovers the 'environment' used by Berkeley DB. The error you're seeing is saying that this environment is corrupt. If you run recovery, you're rebuilding this environment, possibly recovering some data that hadn't yet been written to the actual data files.As always, backing up your __repository__ directory before any such operations, especially after a hard computer crash, is strongly recommended.You can run recovery with the -R command line flag. What's somewhat of concern here, though, is that it should have attempted recovery automatically...If that fails, the next thing to attempt is deleting the __db.00? files and the log.00000000?? files from your __repository__ (these so-called environment files) and run recovery again.When you do a repository backup (using the relevant menu or the --backup option) only your *.db and DB_* files are actually backed up. When then running restore (using -r), recovery is run for you. In other words, if you know that you have a good repository backup archive around, you can start chandler from it, telling it to restore that backup with -r (yes, this overwrites your current __repository__ directory, back it up first).See chandler --help for a list of all command line flags.And, repeating myself, before attempting any of this, just to be sure, make a complete copy of your __repository__ directory in case something goes wrong.To find the correct location of your __repository__ directory see http://chandlerproject.org/bin/view/Projects/ProfileDirectory, that directory is in your profile directory.Andi..Chandler is great but if it can't manage the database properly, it's suicidal to put all my info in there !Please tell me that actually it's a minor problem, that my data are safe andthat chandler will... please..Thanks for your help, I like chandler and I hope this is just a bad "joke".Paul, python web-dev using django ps: I couldn't connect to IRC channel ... Seconds since last error: 4 Chandler Version: 1.0.3 OS: posix Platform Type: darwin Platform Details: Darwin-9.7.0-i386-32bit Architecture: i386 Python Version: 2.5.1 (r251:54863, Feb 6 2009, 19:02:12) [GCC 4.0.1 (Apple Inc. build 5465)] Traceback (most recent call last): File "/Applications/Chandler.app/Contents/Resources/Chandler.py", line 101, in main return realMain()File "/Applications/Chandler.app/Contents/Resources/Chandler.py", line 80,in realMain app = wxApplication(redirect=redirect, useBestVisual=useBestVisual)File"/Applications/Chandler.app/Contents/Resources/release/site-packages/wx/_core.py", line 7901, in __init__ self._BootstrapApp()File"/Applications/Chandler.app/Contents/Resources/release/site-packages/wx/_core.py", line 7498, in _BootstrapApp return _core_.PyApp__BootstrapApp(*args, **kwargs)File"/Applications/Chandler.app/Contents/Resources/application/Application.py",line 377, in OnInit options) File"/Applications/Chandler.app/Contents/Resources/application/Utility.py", line1102, in openRepositoryOrBackup view = openRepository(options, repoDir) File"/Applications/Chandler.app/Contents/Resources/application/Utility.py", line1071, in openRepository view = initRepository(repoDir, options) File"/Applications/Chandler.app/Contents/Resources/application/Utility.py", line685, in initRepository repository.open(**kwds)File"/Applications/Chandler.app/Contents/Resources/release/site-packages/chandl erdb-0.7_37-py2.5-macosx-10.5-i386.egg/chandlerdb/persistence/DBRepository.py", line 970, in open raise RepositoryRunRecoveryError, recover RepositoryRunRecoveryError: True
_______________________________________________ [email protected] mailing list unsubscribe here: http://lists.osafoundation.org/mailman/listinfo/chandler-users Chandler wiki: http://chandlerproject.org/wikihome
