Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 9 Jul 2013 23:15:48 +0000 (UTC)
From: "Omkar Vinit Joshi (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12617496.1353767405368.22375.1373411748451@arcas>
In-Reply-To: <JIRA.12617496.1353767405368@arcas>
References: <JIRA.12617496.1353767405368@arcas>
Subject: [jira] [Commented] (YARN-241) Node Manager fails to launch
 containers after NM restart in secure mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Omkar Vinit Joshi commented on YARN-241:
----------------------------------------

I tried restarting NM several times in secured mode.. but containers successfully start /finish on it. However now this authentication happens irrespective of security and instead of container tokens, nmtokens are getting used. 
                
> Node Manager fails to launch containers after NM restart in secure mode
> -----------------------------------------------------------------------
>
>                 Key: YARN-241
>                 URL: https://issues.apache.org/jira/browse/YARN-241
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.0.2-alpha, 2.0.1-alpha
>            Reporter: Devaraj K
>            Assignee: Omkar Vinit Joshi
>            Priority: Critical
>
> After restarting the Node Manager it fails to launch containers with the below exception.
>  {code:xml}
> 2012-11-24 17:21:56,141 INFO org.apache.hadoop.ipc.Server: IPC Server listener on 8048: readAndProcess threw exception java.lang.IllegalArgumentException: Invalid key to HMAC computation from client 158.1.131.10. Count of bytes read: 0
> java.lang.IllegalArgumentException: Invalid key to HMAC computation
>         at org.apache.hadoop.security.token.SecretManager.createPassword(SecretManager.java:153)
>         at org.apache.hadoop.yarn.server.security.ContainerTokenSecretManager.retrievePassword(ContainerTokenSecretManager.java:109)
>         at org.apache.hadoop.yarn.server.security.ContainerTokenSecretManager.retrievePassword(ContainerTokenSecretManager.java:44)
>         at org.apache.hadoop.security.SaslRpcServer$SaslDigestCallbackHandler.getPassword(SaslRpcServer.java:194)
>         at org.apache.hadoop.security.SaslRpcServer$SaslDigestCallbackHandler.handle(SaslRpcServer.java:220)
>         at com.sun.security.sasl.digest.DigestMD5Server.validateClientResponse(DigestMD5Server.java:568)
>         at com.sun.security.sasl.digest.DigestMD5Server.evaluateResponse(DigestMD5Server.java:226)
>         at org.apache.hadoop.ipc.Server$Connection.saslReadAndProcess(Server.java:1199)
>         at org.apache.hadoop.ipc.Server$Connection.readAndProcess(Server.java:1393)
>         at org.apache.hadoop.ipc.Server$Listener.doRead(Server.java:710)
>         at org.apache.hadoop.ipc.Server$Listener$Reader.doRunLoop(Server.java:509)
>         at org.apache.hadoop.ipc.Server$Listener$Reader.run(Server.java:484)
> Caused by: java.security.InvalidKeyException: No installed provider supports this key: javax.crypto.spec.SecretKeySpec
>         at javax.crypto.Mac.a(DashoA13*..)
>         at javax.crypto.Mac.init(DashoA13*..)
>         at org.apache.hadoop.security.token.SecretManager.createPassword(SecretManager.java:151)
>         ... 11 more
>  {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira