Re: [htdig] HTDig Aborted and Segmentation Faults

[Jim C. <li...@yg...>]

On Friday, March 21, 2003, at 05:32 AM, Abbie Greene wrote:

> I'm having some problems running HTDig on two certain folders.  The
> documents it's indexing are either HTML or TXT.  I ran HTDig awhile 
> back
> on one of the folders (2002 10Ks), and it indexed everything fine (the
> database is around 1.1G, and takes a couple of days to run).  However I
> received some new files to index in with these older ones, so I ran
> htdig -a -c [conf file] -vvv -s to index the new files.  However, I 
> kept
> receiving a segmentation fault after about 2 hours of htdig running.  I
> thought 'oh the problem must be the new files'...however I ran .htdig 
> on
> the new files, (only 100 or so), and everything indexed great.  So now 
> I
> have an 'old' files database that does not contain the new ones and a
> new file database.  However when I run htdig on all the files it always
> fails.  It doesn't seem to fail on the same file each time, but around
> the same timespan after it started.  I tried running .htmerge to merge
> the two databases...no way.  It 'killed' my linux box...totally brought
> it to a screeching halt after about 3 hours ... just ate up all the
> resources.  Any ideas how I might get these two databases together?

With the 3.2 code you can supply multiple config parameters in your 
search page. So if you set up separate config files for each database 
you want to search and specify each in the search page, htsearch should 
hit all of the database and present the merged results. Perhaps this 
would serve as a temporary work around?

> The other is an abort notice I'm receiving when I run HTDig on a set of

There is a known problem with database corruption in recent 3.2 
snapshots. This is likely the problem responsible for the aborts and 
segfaults you are running into. Efforts are currently being made to 
track down and correct the problem.

> Last question (I promise).  My htsearch.htm file has several different
> conf files to choose from using radio buttons.  When a user chooses a
> certain cof file on the first screen, how can that variable be passed 
> to
> the next screen (like header.html) so that the relevant radio button is
> checked?  I see that htsearch uses $&(CONF)" however I wasn't sure how
> to utilize this in the sense of 'checking' radio buttons.

If you haven't already done so, you might want to take a look at the 
following two attributes.

http://www.htdig.org/dev/htdig-3.2/attrs.html#allow_in_form
ttp://www.htdig.org/dev/htdig-3.2/attrs.html#build_select_lists

Jim

> I'm running htdig 3.2.0b4 on redhat linux 8.0.