Can't say for certain, but it looks like something on your system is
sucking down all available RAM/swap space and starving out the processes
being run by your rundig script. Aside from htmerge, it looks like about
every program kicked off by the script (some of which have nothing to do
with the ht://Dig package) is resulting in a segfault; htmerge itself is
failing somewhat more gracefully when the system sort command reports a
memory allocation failure (/bin/sort: Memory exhausted).

Since the failures continue even after htdig crashes, it would seem that
the underlying problem is external to your dig script. However I
wouldn't take that as a certainty without further investigation.

In order to read the core file you need an appropriate debugger (e.g.
gdb if you build ht://Dig with GCC). Even then what you get probably
won't be particularly meaningful if you don't have some development
experience. However if you have a debugger available, someone might be
able to walk you through generating a backtrace that you could submit to
the list.

Jim

On Sun, 10 Apr 2005, Robert Isaac wrote:

htdig 3.1.6 on a Cobalt RaQ550 server.

This has happened again. This time I was running:

[root bin]# bash rundig.sh

This is the log:

Start time: Sun Apr 10 15:20:03 BST 2005
!! Error: Bad annotation destination
!! Error: Bad annotation destination
!! Error: Bad annotation destination
!! Error: Bad annotation destination
rundig.sh: line 43: 27198 Aborted (core dumped) $BASEDIR/bin/htdig $verbose -s -a -c $CONF >>$REPORT
Done Digging: Sun Apr 10 15:24:16 BST 2005
/bin/sort: Memory exhausted
Done Merging: Sun Apr 10 15:24:17 BST 2005
rundig.sh: line 66: 29605 Segmentation fault (core dumped) mv $DBDIR/db.docs.index.work $DBDIR/db.docs.index
rundig.sh: line 67: 29606 Segmentation fault (core dumped) mv $DBDIR/db.words.db.work $DBDIR/db.words.db
End time:


rundig.sh: line 76: 29608 Segmentation fault (core dumped) fgrep "htdig:" $REPORT

rundig.sh: line 78: 29609 Segmentation fault (core dumped) fgrep "htmerge:" $REPORT

rundig.sh: line 80: 29610 Segmentation fault (core dumped) fgrep "rundig:" $REPORT

Total lines in /home/search/tmp/htdig.report:
rundig.sh: line 87: 29612 Segmentation fault (core dumped) mail -s "$SUBJECT - $STARTTIME" $REPORT_DEST <$REPORT
rundig.sh: line 90: 29613 Segmentation fault (core dumped) rm $REPORT


There is a file "core" in /home/search/bin and /home/tmp/htdig but I cannot read them.
There is file "report" in /home/search/tmp and this is:


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ht://Dig general mailing list: <[email protected]>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general

Reply via email to