[Mailman-Users] Odd results running nightly_htdig

[Richard Barrett]

On Saturday, October 18, 2003, at 03:38  pm, Paul Kleeberg wrote:

> This has been going on for a while but I have finally decided to 
> address it.  Old list, originally on Listproc, converted last 
> February.  Some older messages have large attachments.  I have just 
> updated to mm2.1.3 and cleaned up the archives after editing the mbox 
> file and then using arch --wipe ... and blow_away_htdig.  When I use 
> nightly_rundig, I get the following:
>
>> [root at gns mailman]# cron/nightly_htdig
>> pg->type:  0
>> ************************************
>> ************************************
>> ************************************
>> page size:8192
>>  00-07: Log sequence number.  file  : 0
>>  00-07: Log sequence number.  offset: 0
>>  08-11: Current page number.  : 53
>>  12-15: Previous page number. : 0
>>  16-19: Next page number.     : 0
>>  20-21: Number of item pairs on the page. : 0
>>  22-23: High free byte page offset.       : 8192
>>     24: Btree tree level.                 : 0
>>     25: Page type.                        : 0
>> entry offsets:
>>     0:  0  0  0  0  0  0  0  0 35  0  0  0  0  0  0  0  0  0  0  0
>>    20:  0  0  0 20  0  0 fc 1f fc 1f ec 1f e8 1f d8 1f d4 1f c4 1f
>>    40: c0 1f b0 1f ac 1f 9c 1f 98 1f 88 1f 84 1f 74 1f 70 1f 60 1f
>>
>> <snip>
>>
>>  8140: 61 74 65 87  0  0  0  2  1  0  1  0  1  0  1  0  b  0  1 64
>>  8160: 61 74 65 87  0  0  0  2  1  0  1  0  1  0 81  0  b  0  1 64
>>  8180: 61 74 65 87  0  0  0  2  1  0 81  0
>> [root at gns mailman]#
>
> The indexing has appeared to work.  log/error does not have an entry 
> for this.  Any ideas?  Should I do anything or should I ignore it?  RH 
> 8.0, htdig 3.2 (RedHat's htdig - have been reluctant to remove it for 
> fear of breaking something else).
>

I have no clue what is generating this output but I would guess it 
stems from one of HTdig's programs being invoked by the HTdig rundig 
script which has been executed by nightly_htdig.

nightly_htdig executes rundig on behalf of each list with new postings 
to the archive (since the last time rundig was run on behalf of that 
list) using the command:

<path-to-rundig> -c $prefix/archives/htdig/<listname>.conf

Try running that command by hand and see if the output you are 
concerned about is generated. If so then it is an HTdig issue and 
posting to whatever the htdig support list is may be the best bet.

Let us know how you get on.

> Paul
> --
> Paul Kleeberg
> paul at fpen.org
>
-----------------------------------------------------------------------
Richard Barrett                               http://www.openinfo.co.uk