It seems to me that if you run nutch in deploy mode and make changes to config files then you need to rebuild .job file again unless you specify config_dir option in hadoop command.
Alex. -----Original Message----- From: Christopher Gross <[email protected]> To: user <[email protected]> Sent: Mon, Oct 1, 2012 1:22 pm Subject: Re: Building Nutch 2.0 I have my 1.3 set up in a /proj/nutch/ directory that has the bin, conf, lib, logs, ..etc.., with NUTCH_HOME pointing there. I don't quite see what the difference would be for 2.x as long as NUTCH_HOME pointed to the right place. Is there documentation anywhere on how to do a deployment? -- Chris On Mon, Oct 1, 2012 at 3:59 PM, Lewis John Mcgibbney <[email protected]> wrote: > Hi Chris, > > On Mon, Oct 1, 2012 at 8:52 PM, Christopher Gross <[email protected]> wrote: >> OK, I added the port being used by hbase to iptables, and now I'm farther. >> >> I'm getting: >> 12/10/01 19:44:17 ERROR fetcher.FetcherJob: Fetcher: No agents listed >> in 'http.agent.name' property. >> >> But I do have an entry there, and it matches the first in the >> robots.agents as well. > > This can only mean that you have not recompiled this stuff into the > runtime/local directory. > >> >> How should I have this laid out? Should I be running out of the >> 'runtime' dir, or is it fine that I've pulled all those files out and >> into a /proj/nutch-2.1/ directory (so there's a bin, conf, lib, >> ..etc.. in there, with NUTCH_HOME pointing to that dir). > > OK so you are running locally. I can't say whether its OK to copy the > directories and their content elsewhere as I've never done it however > I would avoid unless absolutely necessary. It terms of the directory > layout Nutch 2.x is identical to 1.x. > > It really helps if you make explicit which back end you intend to use > as the config may alter accordingly.
