Re: [htdig-dev] Re: New patch [was: new release of htdig]

[Ted Stresen-R. <ted...@ma...>]

Hi,

Might this behavior have something to do with the size of the site you 
are indexing? I am indexing four sites on my local machine (not very 
much to index, in truth) and it occurred to me that perhaps, in order 
to trigger the bug, you have to index a larger amount of information.

I'll give it a whirl indexing Yahoo! to see what happens...

just kidding... but I will try another site that is larger than what I 
have on my hard drive to see if that makes a difference. Also, if you 
have a chance, could post the config file you are using so we are all 
using the same attribute values?

Ted Stresen-Reuter
http://www.tedmasterweb.com/

On Sunday, May 4, 2003, at 01:31  PM, Jim Cole wrote:

> Hi - I am still having problems with this patch applied. The dig makes 
> it much farther than it did last time around, but compression still 
> appears to be an issue. I receive the following a few times toward the 
> end of the dig.
>
> WordDB: CDB___memp_cmpr_read: unable to uncompress page at pgno = 
> 246532
> WordDB: PANIC: Input/output error
> WordDB: CDB___memp_cmpr_read: unable to uncompress page at pgno = 
> 246532
> WordDB: PANIC: Input/output error
>
> Then at the end of the dig, I see the following.
>
> WordDB: CDB___memp_cmpr_read: unable to uncompress page at pgno = 
> 246532
> WordDB: PANIC: Input/output error
> WordDBCursor::Get(17) failed DB_RUNRECOVERY: Fatal error, run database 
> recovery
>
> The referenced page number is the same for every error message. For 
> this test, the default value was used for wordlist_page_size. Both 
> wordlist_compress and wordlist_compress_zlib were set to true, and 
> compression_level was set to 8. I used a fresh copy of the CVS code 
> (as of yesterday) with dbase.patch2 applied.
>
> Jim
>
> On Sunday, April 27, 2003, at 02:27 AM, Lachlan Andrew wrote:
>
>> OK, here is another patch...
>>
>> The problem was that I was using the counts of clean and dirty cache
>> pages, but they were not recorded correctly in the old BDB 2.x
>> (although that didn't show up in my initial tests...).  This patch
>> contains the fix, copied from BDB 3.3.11.
>>
>> Thanks again for your help :)
>>
>> Lachlan
>>
>> On Sun, 27 Apr 2003 12:54, Jim Cole wrote:
>>> I am still running into fatal problems with OS X. I no longer get
>>> the segfault, but instead see the output shown below.
>> <dbase.patch2>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> htdig-dev mailing list
> htd...@li...
> https://lists.sourceforge.net/lists/listinfo/htdig-dev
>