[aseek-users] index halted

From: Ing. Ernesto Rapetti (no email)
Date: Wed Oct 09 2002 - 15:46:16 EDT


I'm running aspseek 1.2.10 on a RedHat 7.3 since a few weeks, and it was
working alright until now, when the index process halts after several
hours.

The database now has a total of 248400 documents. On monday I observed the
error "MySQL server has gone away" reported on this list and set the
max_allowed_packet=10M variable on my.cnf as John advised.

In the new run index worked fine for 9 hours, and then begin to report the
following on logs.txt:

Got next 1 URLs for: 0.001 seconds. Queued docs: 630.Time
1034163064-1034163065.Not available!

What is not available?
Doing a strace I notice this line:

read(3, 0x984c8b8, 81920) = -1 EAGAIN (Resource temporarily
unavailable)

So maybe the connection to the database is dead.

Doing "mysqladmin processlists" shows a connection that is idle since
index is reporting the error, then from the database side the connection
is not closed but index can't fetch new documents.

I'll do a "index -E" and start the process again, but I wonder if I have
to repeat this process every day.

Ernesto.








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD