similar to: Database Corrupt Error

Matt <mattator at gmail.com> writes: > thanks didn't know about xapian-check ! > the output > === > docdata: > blocksize=8K items=70 firstunused=3 revision=421 levels=0 root=2 > B-tree checked okay > docdata table structure checked OK > > termlist: > blocksize=8K items=186136 firstunused=62058 revision=421 levels=2 root=12260 > B-tree checked okay >

Hello, I noticed a problem with DatabaseCorruptError exceptions with public-inbox and I guess it's user error... The problem is public-inbox was calling replace_document to modify the DB while iterating through a PostingIterator. At first I thought it was a glass problem, but I've hit it with chert on my dataset, too. I have a standalone Perl script to reproduce the problem at

Just got this error when replacing (updating) a document in the xapian index (using php bindings): Fatal error: Uncaught exception 'Exception' with message 'DatabaseError: Error reading block 16908825: got end of file' Does anyone know what this means exactly? Alec

Hello, I am trying to rebuild an index of 2+ million documents and have not been successful. I am running Python 2.7 Django 1.7 Haystack 2.1.1 Xapian 1.2.21 The index rebuild command I’m using is: django-admin.py rebuild_index --noinput --batch-size=100000 The rebuild completes but an immediate xapian-check returns this error: xapian-check ./archive_index record: baseB blocksize=8K

Hi guys I have implemented xapian on a website, and it currently has about 2M items in its index. Its all been working quite nicely so far, until I tried removing some old items from the index (removing items when the index was smaller was no problems at all). When I try to remove them now (using writabledatabase_delete_document() via php), it halfway freezes up the machine, and the apache

I'm trying to compact (or at least merge) multiple databases, while stripping search records which are no longer required. Backstory: I've inherited the Cyrus IMAPd xapian-based search code from Greg Banks when he left Opera. One of the unfinished parts was removing expunged emails from the search database. We moved from having a single search database to supporting multiple

Hi there, My web app uses Xapian via the PHP bindings. I'm getting this error thrown occasionally when atempting to instantiate a XapianDatabase object for searching. DatabaseCorruptError: Expected block 107 to be level 1, not 0 Here's the line that invokes it: $database = new XapianDatabase(PROJROOT.'/data/xapian/posts'); And my version is xapian-core 1.2.3 with matchspy.

Ocassionally when I'm searching using Omega I get: "DatabaseCorruptError: Cannot open tables at consistent revisions" If I click reload it's all ok, is this the database being updated?, is there a way to avoid the message? Frank

Greetings, I've been wondering about the index format and backwards compatibility. We're using the dev version (for chert) and each svn up means that any indexes created prior to this revision cannot be read. Is this purely a cautious move to prevent errors, and, barring any obvious index format changes, can I safely force the current revision to read existing indexes? eg, by

Hello, I'm having a litle issue with Xapian-1.0.6 with php bindings under php5 when trying to add a new document it throws: Fatal error: Uncaught exception 'Exception' with message 'DatabaseCorruptError: Failed to unlink /var/lib/xapian/trade.ar/termlist.baseA: No such file or directory' in /usr/share/php5/xapian.php:1140 Stack trace: #0 /usr/share/php5/xapian.php(1140):

I have installed the new Xapian 1.4.0 , during the installation, I haven't seen any problems, however, when I execute commands quest and delve I get different versions, and my Perl-based searches return Exception: Couldn't detect type of database ... and what are these glass things in the index directories? There is a no new version of Perl Search::Xapian. $ quest -version quest -

Hi All, I wanted to add a small tweak to my installation of the Query Parser. Should I be editing queryparser.lemony? I tried that and the make didn't include my change. I applied the same change to queryparser_internal.cc and it worked fine. Is the .lemony file something used internally and I can ignore? Or do I need to run something prior to make to convert the files? Thanks, Mike Boone.

Hello folks- I have an issue with my Xapian index, and I am hoping someone can help me out with some ideas. I am running Xapian on Debian Squeeze as part of an openPLM installation. It is a django application that uses Postgresql as the database, and Haystack as the search engine. A couple of weeks ago, I misconfigured a crontab, and it made a recursive backup that filled up the hard drive

We've had some catastrophic filesystem failures that have left us with corrupted databases with empty files and no backup for about 15TB of our data. Recreating the 15TB from source data backups is possible but will take a very very long time. I'm hoping that, given all of the .DB files are still intact, there my be some way to extract their contents and rebuild the other tables. This

Greetings, Using latest svn. I've noticed the following error when performing index merging: postlist: baseB blocksize=8K items=33962 lastblock=534 revision=1 levels=2 root=459 B-tree checked okay Tag containing meta information is corrupt. postlist table errors found: 1 I can still search on this index (I've only checked very small indexes), but merging is now a problem since I check

On Mon, Sep 02, 2013 at 09:21:48AM +0800, jiangwen jiang wrote: > TfIdfWeight and BM25(b=0) also need wdf_upper_bound, it is not exists in > Lucene backends. If you don't provide an implementation of wdf_upper_bound(), the default is to use the collection frequency of the term, so provided that information is available in the lucene files, the lack of wdf_upper_bound information

Hello, Would anyone object to my submitting an entry for xapian-core to the FreeBSD ports collection ? This would make it even easier for any FreeBSD user to install a xapian-based application. By the way, it does not seem quite right that xapian-core 0.9 will install commands with such generic names as 'copydatabase' or 'simplesearch' to /usr/local/bin by default. Either a

Hi, all: I have wrote a demo patch for Backend for Lucene format indexes, Lucene version is 3.6.2. http://lucene.apache.org/core/3_6_2/fileformats.html Now, this demo patch just support the basic features in Lucene. Compound File(.cfs/.cfe)?term vector(.tvx/.tvd/.tvf) delete document(.del) are not supported, skip list in .fdx is not supported too example/quest.cc is used to test this demo.

On Wed, Jun 19, 2013, at 03:49 PM, Olly Betts wrote: > On Wed, Jun 19, 2013 at 01:29:16PM +1000, Bron Gondwana wrote: > > The advantage of compact - it runs approximately 8 times as fast (we > > are CPU limited in each case - writing to tmpfs first, then rsyncing > > to the destination) and it takes approximately 75% of the space of a > > fresh database with maximum

I posted this message first. But it was missing so I post again. I think there is a some bug in build configration files. Can you check up the following errors and fix it? The error has no concern with UTF-8 patch. Environment : CentOS 4.3 x86_64 Sungsoo Kim ---------------------------------- [root at saturn xapian-core-0.9.4_svn6707]# make ... ... mkdir .libs/libxapian.lax/libqueryparser.a