Hi there,
I tried out udmsearch on a local site, and it all worked fine. Indexing
was rapid and efficient. Cool Tool :-)
I tried it on external sites, and it goes very fast for a while,
but processes slowly go to sleep, and don't seem to wake up...
Here's a 'ps' listing:
USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND
root 9338 4.1 0.6 4436 3156 ? S N 12:47 1:17 ./indexer
root 9339 5.1 0.6 4596 3224 ? R N 12:47 1:37 ./indexer
root 9340 8.3 0.5 4236 2892 ? R N 12:47 2:38 ./indexer
root 9341 0.6 0.5 4328 2892 ? S N 12:47 0:13 ./indexer
root 9342 1.6 0.5 4328 3048 ? S N 12:47 0:32 ./indexer
root 9343 0.6 0.5 4328 2872 ? S N 12:47 0:11 ./indexer
root 9344 4.1 0.6 4768 3408 ? S N 12:47 1:17 ./indexer
root 9345 6.9 0.6 4708 3408 ? R N 12:47 2:11 ./indexer
root 9346 3.6 0.6 4328 3148 ? S N 12:47 1:09 ./indexer
root 9347 3.5 0.6 4600 3500 ? S N 12:47 1:07 ./indexer
nuggets 11% date
Sun Nov 21 13:23:42 GMT 1999
You can see that they were all started at 12:47, and most have had
only a few minutes (or seconds!) CPU time, yet they remain asleep
(S, not R under STAT)
This is using a Linux 2.2.13 kernel.
and indexer version ...
./indexer -h
indexer from UdmSearch v.2.1.8/MySQL
[...]
Here's the output of indexer -S (in case it's useful)
nuggets 12% ./indexer -S
UdmSearch statistics
Status Expired Total
-----------------------------
0 167191 167221 Not indexed yet
1 2 2 Unknown status
200 2591 46875 OK
301 0 242 Moved Permanently
302 30 1051 Moved Temporarily
304 3 545 Not Modified
403 0 9 Forbidden
404 106 2793 Not found
500 0 4 Internal Server Error
503 23 666 Service Unavailable
504 29 264 Gateway Timeout
-----------------------------
Total 169975 219672
So, any ideas why my indexers stop working ?
ATB,
Simon.
______________
If you want to unsubscribe send "unsubscribe udmsearch"
to [EMAIL PROTECTED]
