hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2324) start-dfs.sh and stop-dfs.sh are not working properly
Date Wed, 14 Sep 2011 20:00:09 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104839#comment-13104839
] 

Devaraj K commented on HDFS-2324:
---------------------------------

Thanks Tom for the info.

I am not overlaying the Common and HDFS directories. I am not getting any problem other than
"/bin/hdfs: No such file or directory" for secondary name nodes. 

I feel it is better to handle this error also. Whoever doesn't want to overlay the Common
and HDFS directories they can use without facing any problems.   

Please provide your opinion on this.

> start-dfs.sh and stop-dfs.sh are not working properly
> -----------------------------------------------------
>
>                 Key: HDFS-2324
>                 URL: https://issues.apache.org/jira/browse/HDFS-2324
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.24.0
>            Reporter: Devaraj K
>             Fix For: 0.24.0
>
>         Attachments: HDFS-2324.patch
>
>
> When we execute start-dfs.sh, it is gving the below error.
> {code:xml}
> linux124:/home/devaraj/NextGenMR/Hadoop-0.24-09082011/hadoop-hdfs-0.24.0-SNAPSHOT/sbin
# ./start-dfs.sh
> ./start-dfs.sh: line 50: /home/devaraj/NextGenMR/Hadoop-0.24-09082011/hadoop-common-0.24.0-SNAPSHOT/libexec/../bin/hdfs:
No such file or directory
> Starting namenodes on []
> ./start-dfs.sh: line 55: /home/devaraj/NextGenMR/Hadoop-0.24-09082011/hadoop-common-0.24.0-SNAPSHOT/libexec/../bin/hadoop-daemons.sh:
No such file or directory
> ./start-dfs.sh: line 68: /home/devaraj/NextGenMR/Hadoop-0.24-09082011/hadoop-common-0.24.0-SNAPSHOT/libexec/../bin/hadoop-daemons.sh:
No such file or directory
> Secondary namenodes are not configured.  Cannot start secondary namenodes.
> {code}
> It is gving the below error when we execute stop-dfs.sh.
> {code:xml}
> linux124:/home/devaraj/NextGenMR/Hadoop-0.24-09082011/hadoop-hdfs-0.24.0-SNAPSHOT/sbin
# ./stop-dfs.sh
> ./stop-dfs.sh: line 26: /home/devaraj/NextGenMR/Hadoop-0.24-09082011/hadoop-common-0.24.0-SNAPSHOT/libexec/../bin/hdfs:
No such file or directory
> Stopping namenodes on []
> ./stop-dfs.sh: line 31: /home/devaraj/NextGenMR/Hadoop-0.24-09082011/hadoop-common-0.24.0-SNAPSHOT/libexec/../bin/hadoop-daemons.sh:
No such file or directory
> ./stop-dfs.sh: line 44: /home/devaraj/NextGenMR/Hadoop-0.24-09082011/hadoop-common-0.24.0-SNAPSHOT/libexec/../bin/hadoop-daemons.sh:
No such file or directory
> Secondary namenodes are not configured.  Cannot stop secondary namenodes.
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message