You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/04/07 15:35:41 UTC

[jira] [Created] (HADOOP-14291) S3a "No auth" message to include diagnostics

Steve Loughran created HADOOP-14291:
---------------------------------------

             Summary: S3a "No auth" message to include diagnostics
                 Key: HADOOP-14291
                 URL: https://issues.apache.org/jira/browse/HADOOP-14291
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: fs/s3
    Affects Versions: 2.8.0
            Reporter: Steve Loughran


There's a whole section in s3a troubleshooting because requests can get auth failures for many reasons, including

* no credentials
* wrong credentials
* right credentials, wrong bucket
* wrong endpoint for v4 auth
* trying to use private S3 server without specifying endpoint, so AWS being hit
* clock out
* joda time
....

We can aid with debugging this by including as much as we can in in the message and a URL To a new S3A bad auth wiki page.

Info we could include
* bucket
* fs.s3a.endpoint
* nslookup of endpoint
* Anything else relevant but not a security risk

Goal; people stand a chance of working out what is failing within a bounded time period








--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org