Unfortunately, the logs have since been overwritten by nutch so I can't
check them, but I am pretty sure those are actually the messages from
the task tracker log on the remote machine. If I am remembering
correctly, all that was shown on the master was a short exception saying
the child failed or something like that. I wish I could be more help but
as I said, when the jobtracker/tasktrackers were stopped and started,
they overwrote the log.
-Matt Zytaruk
Doug Cutting wrote:
Matt Zytaruk wrote:
Exception in thread "main" java.io.IOException: Not a file:
/user/nutch/segments/20060107130328/parse_data/part-00000/data
at org.apache.nutch.ipc.Client.call(Client.java:294)
This is an error returned from an RPC call. There should be more
details about this in a slave log, e.g., a better stack trace, some
context, etc. What do you see there?
We also got this for awhile (seems like the mapred/system dir is
never being created for some reason):
java.io.IOException: Cannot open filename
/nutch-data/nutch/tmp/nutch/mapred/system/submit_euiwjv/job.xml
at org.apache.nutch.ipc.Client.call(Client.java:294)
Again, it would be interesting to see what happened on the other end
of this RPC call. Please look in the remote log.
Doug
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nutch-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
