You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@whirr.apache.org by Frank Scholten <fr...@frankscholten.nl> on 2012/02/22 10:56:00 UTC

No directory, logging in with HOME=/ , error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or directory

Hi all,

I see this message several times in the log when I start a Hadoop cluster.

No directory, logging in with HOME=/
, error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or directory

I can SSH into the nodes but Hadoop isn't started obviously. I
navigated to /user/local/hadoop and found the bin directory to be
empty. Do you know what might be causing this and also: how do you
generally debug these kind of problems?

Cheers,

Frank

Re: No directory, logging in with HOME=/ , error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or directory

Posted by Andrei Savu <sa...@gmail.com>.
Look into /tmp for a logs folder. That contains the scripts execution logs
and you should be able to see why it failed - I assume the download failed
for the Hadoop tarball.

On Wed, Feb 22, 2012 at 9:56 AM, Frank Scholten <fr...@frankscholten.nl>wrote:

> Hi all,
>
> I see this message several times in the log when I start a Hadoop cluster.
>
> No directory, logging in with HOME=/
> , error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or
> directory
>
> I can SSH into the nodes but Hadoop isn't started obviously. I
> navigated to /user/local/hadoop and found the bin directory to be
> empty. Do you know what might be causing this and also: how do you
> generally debug these kind of problems?
>
> Cheers,
>
> Frank
>

Re: No directory, logging in with HOME=/ , error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or directory

Posted by Andrei Savu <sa...@gmail.com>.
It's strange that we are still seeing this problem - I've added a retry
loop around curl some time ago. I guess we need to improve that!

On Wed, Feb 22, 2012 at 11:44 AM, Frank Scholten <fr...@frankscholten.nl>wrote:

> I looked in /tmp/logs/stderr and found
>
> OpenJDK Runtime Environment (IcedTea6 1.9.10)
> (6b20-1.9.10-0ubuntu1~10.04.3)
> OpenJDK Client VM (build 19.0-b09, mixed mode, sharing)
> curl: (18) transfer closed with 390578 bytes remaining to read
> curl: (22) The requested URL returned error: 404
>
> gzip: stdin: unexpected end of file
> tar: Unexpected EOF in archive
> tar: Unexpected EOF in archive
> tar: Error is not recoverable: exiting now
> curl: (22) The requested URL returned error: 404
> curl: (22) The requested URL returned error: 404
>
> However I can't see which url is giving problems. Perhaps remove the
> --silent flag for curl?
>
> Cheers,
>
> Frank
>
> On Wed, Feb 22, 2012 at 11:10 AM, Ashwanth Kumar
> <as...@googlemail.com> wrote:
> > If you look closely, i guess you will not have JAVA installed on your
> > system. I had this problem due to sun-java6-jdk package being removed
> from
> > the Ubuntu repos.
> >
> > On Wed, Feb 22, 2012 at 3:26 PM, Frank Scholten <fr...@frankscholten.nl>
> > wrote:
> >>
> >> Hi all,
> >>
> >> I see this message several times in the log when I start a Hadoop
> cluster.
> >>
> >> No directory, logging in with HOME=/
> >> , error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or
> >> directory
> >>
> >> I can SSH into the nodes but Hadoop isn't started obviously. I
> >> navigated to /user/local/hadoop and found the bin directory to be
> >> empty. Do you know what might be causing this and also: how do you
> >> generally debug these kind of problems?
> >>
> >> Cheers,
> >>
> >> Frank
> >
> >
> >
> >
> > --
> >
> > Ashwanth Kumar / ashwanthkumar.in
> >
> >
>

Re: No directory, logging in with HOME=/ , error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or directory

Posted by Frank Scholten <fr...@frankscholten.nl>.
I looked in /tmp/logs/stderr and found

OpenJDK Runtime Environment (IcedTea6 1.9.10) (6b20-1.9.10-0ubuntu1~10.04.3)
OpenJDK Client VM (build 19.0-b09, mixed mode, sharing)
curl: (18) transfer closed with 390578 bytes remaining to read
curl: (22) The requested URL returned error: 404

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404

However I can't see which url is giving problems. Perhaps remove the
--silent flag for curl?

Cheers,

Frank

On Wed, Feb 22, 2012 at 11:10 AM, Ashwanth Kumar
<as...@googlemail.com> wrote:
> If you look closely, i guess you will not have JAVA installed on your
> system. I had this problem due to sun-java6-jdk package being removed from
> the Ubuntu repos.
>
> On Wed, Feb 22, 2012 at 3:26 PM, Frank Scholten <fr...@frankscholten.nl>
> wrote:
>>
>> Hi all,
>>
>> I see this message several times in the log when I start a Hadoop cluster.
>>
>> No directory, logging in with HOME=/
>> , error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or
>> directory
>>
>> I can SSH into the nodes but Hadoop isn't started obviously. I
>> navigated to /user/local/hadoop and found the bin directory to be
>> empty. Do you know what might be causing this and also: how do you
>> generally debug these kind of problems?
>>
>> Cheers,
>>
>> Frank
>
>
>
>
> --
>
> Ashwanth Kumar / ashwanthkumar.in
>
>

Re: No directory, logging in with HOME=/ , error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or directory

Posted by Ashwanth Kumar <as...@googlemail.com>.
If you look closely, i guess you will not have JAVA installed on your
system. I had this problem due to sun-java6-jdk package being removed from
the Ubuntu repos.

On Wed, Feb 22, 2012 at 3:26 PM, Frank Scholten <fr...@frankscholten.nl>wrote:

> Hi all,
>
> I see this message several times in the log when I start a Hadoop cluster.
>
> No directory, logging in with HOME=/
> , error=-su: /usr/local/hadoop/bin/hadoop-daemon.sh: No such file or
> directory
>
> I can SSH into the nodes but Hadoop isn't started obviously. I
> navigated to /user/local/hadoop and found the bin directory to be
> empty. Do you know what might be causing this and also: how do you
> generally debug these kind of problems?
>
> Cheers,
>
> Frank
>



-- 

Ashwanth Kumar / ashwanthkumar.in