EM wrote:
Two segments finished today, one just fine and parses fine. The other one fetched with -noParsing, failed although not on the same spot. I'm attaching the output received with ctrl-break.
That's interesting... What number of threads did you use? Could you perhaps send me this fetchlist (off-list, to ab at getopt dot org). If you used non-standard settings in your configuration, I'd love to take a look at the content of your conf/ dir.
By "failed" do you mean that the fetcher process appeared to be hanging indefinitely, or something else?
Because the first segment went fine, would I be right in assuming that something's wrong with my RAM?
No. This is some sort of deadlock, either within our code or somewhere in HttpClient.
-- Best regards, Andrzej Bialecki <>< ___. ___ ___ ___ _ _ __________________________________ [__ || __|__/|__||\/| Information Retrieval, Semantic Web ___|||__|| \| || | Embedded Unix, System Integration http://www.sigram.com Contact: info at sigram dot com ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Nutch-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-general
