db bug..

FreeBSD 4.4 machine..
Untarred tarball..
cd ~/dcc-dccd-1.0.43
./configure
make
make install


bash-2.05# rm /var/dcc/dcc_db*

bash-2.05# /var/dcc/libexec/dbclean -N

dccproc 1.0.43 clearing database /var/dcc/dcc_db

Jan 30 12:18:06 hostname dbclean[6560]: 1.0.43 clearing database /var/dcc/dcc_db
hashed 209 records containing 209 checksums, compressed 0 records
Jan 30 12:18:07 hostname dbclean[6560]: hashed 209 records containing 209
checksums, compressed 0 records 8192 hash entries total, 209 or 2% used
Jan 30 12:18:07 hostname dbclean[6560]: 8192 hash entries total, 209 or 2%
used

bash-2.05# dccproc -V
1.0.43

bash-2.05# /var/dcc/libexec/start-dccd

Jan 30 12:18:19 hostname dccd[6594]: 1.0.43 listening to port 6277 with /var/dcc

bash-2.05# cat ~/superclean.email | dccproc
Return-Path: <kbo@gpl.inter7.com>
Message-ID: <20011008234051.7288.qmail@to.com>
Date: 8 Oct 2001 23:40:51 -0000
Content-type:
To: postmaster@test.com
From: kbo@gpl.inter7.com
Subject: Hello
Content-Type: text


This is a new message body mutation.

I am ignoring subject lines now.
bash-2.05#


Jan 30 12:18:28 hostname dccd[6594]: query: bad hash list entry at 0x1eab
Jan 30 12:18:28 hostname dccd[6594]: "query: bad hash list entry at
0x1eab" sent to client 32771 at 127.0.0.1,1772
Jan 30 12:18:28 hostname dccproc[6598]: DCC 127.0.0.1: ERROR  query: bad
hash list entry at 0x1eab


An offline clean and on-line clean remedies the problem temporarily in the
DB.. This can be verified by performing a dccproc -Q.  No error messages
are displayed and the values look proper.  Remove the -Q, and the above
error messages occur again.   This is a machine that .42 works perfectly
on.  Any ideas?


Kyle Stone
kstone@win.net