[
https://issues.apache.org/jira/browse/HDFS-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103211#comment-13103211
]
Tom White commented on HDFS-2323:
---------------------------------
> the start-dfs.sh script will not work without first overlaying the Common and
> HDFS target directories
Yes, this is because the scripts assume that there is a single HADOOP_PREFIX
directory containing bin, conf, etc. It might be a good idea to loosen this at
some point, but this bug fix isn't the place to do it.
> start-dfs.sh script fails for tarball install
> ---------------------------------------------
>
> Key: HDFS-2323
> URL: https://issues.apache.org/jira/browse/HDFS-2323
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Tom White
> Assignee: Tom White
> Attachments: HDFS-2323.patch
>
>
> I build Common and HDFS tarballs from trunk then tried to start a cluster
> with start-dfs.sh, but I got the following error:
> {noformat}
> Starting namenodes on [localhost ]
> sbin/start-dfs.sh: line 55:
> /Users/tom/tmp/hadoop/libexec/../bin/hadoop-daemons.sh: No such file or
> directory
> sbin/start-dfs.sh: line 68:
> /Users/tom/tmp/hadoop/libexec/../bin/hadoop-daemons.sh: No such file or
> directory
> Starting secondary namenodes [0.0.0.0 ]
> sbin/start-dfs.sh: line 88:
> /Users/tom/tmp/hadoop/libexec/../bin/hadoop-daemons.sh: No such file or
> directory
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
