[
https://issues.apache.org/jira/browse/HDFS-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HDFS-2323:
----------------------------
Attachment: HDFS-2323.patch
There are a couple of problems:
1. The scripts refer to "bin/hadoop-daemons.sh" not "sbin/hadoop-daemons.sh".
2. The secondary namenode should not be started at all since it's not
configured to, but the script tries to start it since the test for "0.0.0.0"
fails due to a trailing space.
This patch fixes both of these.
> 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
