[htdig] Re: htdig: htmerge now running for 4500 minutes!!


Didier Gautheron (dgautheron@magic.fr)
Tue, 26 Jan 1999 03:44:48 +0000


Alister van Tonder wrote:
Hi
>
> My htmerge job often runs for several DAYS!!
> Even when I kill the job (after several days) it has produced a
> working searchable database!
>
> This particular job was started at 20h01 on Jan 22nd. The files below
> were created 10 minutes later. In the mean time htmerge continues as
> a job, usually taking all available CPU resources, and continues
> (until I eventually) have to kill it.
>
> A directory listing of the ~/htdig/lib/db directory is as follows:
>
> drwxr-xr-x 2 root root 11264 Jan 24 07:26 .
> drwxr-xr-x 4 root root 1024 Jan 1 10:19 ..
> -rw-r--r-- 1 root root 33153024 Jan 22 20:10 db.docdb
> -rw-rw-r-- 1 root root 740352 Jan 1 11:04 db.docs.index
> -rw-rw-r-- 1 root root 2430976 Jan 2 01:35 db.metaphone.db
>
> -rw-rw-r-- 1 root root 1686528 Jan 2 01:35 db.soundex.db
> -rw-r--r-- 1 root root 47838678 Jan 22 20:10 db.wordlist
htdig end a 20:10
> -rw-r--r-- 1 root root 12288 Jan 22 20:12 db.wordlist.new
At 20:12 htmerge was in a forever loop.
>
> -rw-rw-r-- 1 root root 69552128 Jan 12 01:02 db.words.db
I thing you have a corrupted db.words.db and htmerge was looping in
database code in its first attempt to update it.
db.docs.index was modified Jan 1 and db.words.db Jan 12 , I didn't
double check it but db.docs.index is updated after db.words.db in
htmerge.
My guessing :
Jan 12 you ran rundig, for whatever reason (no space on dev is a big
winner) htmerge failed and you had a corrupted db.
Could you :
- remove db.dwords.db and rerun htmerge (htmerge does it now; as a
matter of fact htmerge keeping the old db.words.db was a genuine bug
:().

Didier

------------------------------------
To unsubscribe from the htdig mailing list, send a message to
htdig@htdig.org containing the single word "unsubscribe" in
the SUBJECT of the message.



This archive was generated by hypermail 2.0b3 on Tue Jan 26 1999 - 08:10:38 PST