Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of sd.codewarrior@gmail.com
 designates 74.125.46.30 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=t6HK/kbi08VsSISiLm8JMj+QHTqswsVNu9/Hjx/oYoMt8ANV899mGR8oIw11bTmJA3
         lTyp7tRrr6rYQ1c05NcG5pg15M4SlbRu5PZDxhzDvUtf8BamcbUI1kxZPrL4RYJx0UFM
         pTQ5GBa28ZR5UhZpmwJ1ce1aUfilq2axAdfjc=
MIME-Version: 1.0
In-Reply-To: <4f10e2890903041418q325f0dc5p6c8bf2f454272b1c@mail.gmail.com>
References: <4f10e2890903041418q325f0dc5p6c8bf2f454272b1c@mail.gmail.com>
Date: Wed, 4 Mar 2009 18:07:24 -0500
Message-ID: <4f10e2890903041507s371ef550nbd9114b3732470a@mail.gmail.com>
Subject: Re: Hadoop FS shell no longer working with S3 Native
From: S D <sd.codewarrior@gmail.com>
To: Hadoop Mailing List <core-user@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=0016e6470ef85e0dfd0464531d40

--0016e6470ef85e0dfd0464531d40
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

My fault on this one. I mistakenly thought the environment variables
(AMAZON_ACCESS_KEY_ID and AMAZON_SECRET_ACCESS_KEY) would override values
set in hadoop-site.xml; I now see that this is not the case for the Hadoop
FS shell commands.

John

On Wed, Mar 4, 2009 at 5:18 PM, S D <sd.codewarrior@gmail.com> wrote:

> I'm using Hadoop 0.19.0 with S3 Native. Up until a few days ago I was
> successfully able to use the various shell functions successfully; e.g.,
>      hadoop dfs -ls .
> To ensure access to my Amazon S3 Native data store I set the following
> environment variables: AMAZON_ACCESS_KEY_ID and AMAZON_SECRET_ACCESS_KEY. Up
> until this morning, this was working fine. Today I tried invoking the above
> shell command (along with several others) and received the following error:
>
> Exception in thread "main" org.apache.hadoop.fs.s3.S3Exception:
> org.jets3t.service.S3ServiceException: S3 PUT failed for '/' XML Error
> Message: <?xml version="1.0"
> encoding="UTF-8"?><Error><Code>InvalidAccessKeyId</Code><Message>The AWS
> Access Key Id you provided does not exist in our
> records.</Message><RequestId>9294E59A199FB551</RequestId><HostId>HPdkhanFEvbz50k5FdwCgQRdOjO4aIBODXiMcBwy6DX7Ve3Jx2uXnujT6oEBhJpN</HostId><AWSAccessKeyId>882</AWSAccessKeyId></Error>...
>
> I have not changed my Amazon access identifiers and I can still use my S3
> Firefox Organizer to access my S3 data (using the same AMAZON_ACCESS_KEY_ID
> and AMAZON_SECRET_ACCESS_KEY as before).
>
> Has anyone else experienced this problem? Has something changed with the
> API that I am unaware of?
>
> Thanks,
> John
>
>
>

--0016e6470ef85e0dfd0464531d40--