Sounds similar to what caused my corrupted
database...
Try the mysql UI - see if it reports any
corrupted table when you switch to using the
aspseek DB, if it does then repair them.
Just my $0.02
Quoting "Dr. John Takacs" <[EMAIL PROTECTED]>:
> I had just completed spidering 1.5 million URLs
and experienced a power
> failure. Obviously a hard shutdown.
>
> My count was at 1.5 million URLs as I had just
done an index -S prior to
> the crash.
>
> I re-booted, and when I went to execute index -
D, I got a core dump. It
> stalled at calculating ranks and then gave the
core dump.
>
> Well, wanting to solve this on my own (dumb
mistake), I decided to
> backup mysql database and back up the
aspseek/var directory per a
> message Kir wrote.
>
> I then cleaned out aspseek and reinstalled it.
>
> I then deleted the reinstalled apseek/var
directory and placed my backup
> apseek/var directory there.
>
> I then executed index -D.
>
> It went through its customary display of
information, and when it got to
> calculating ranks, it said:
>
> Calculating ranks [Aborted....
>
> I need some help! What can I do? At least I
have my URLs backed up,
> but I really don't want to go through that
again.
>
> Any ideas?
>
> Thanks in advance.
>
> John
>
>
-------------------------------------------------
This mail sent through UK Online webmail
