You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sunil Govindan (JIRA)" <ji...@apache.org> on 2018/06/05 18:29:00 UTC
[jira] [Commented] (YARN-8399) NodeManager is giving 403 GSS
exception post upgrade to 3.1 in secure mode
[ https://issues.apache.org/jira/browse/YARN-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502250#comment-16502250 ]
Sunil Govindan commented on YARN-8399:
--------------------------------------
Configuration reuse is causing this problem.
NodeTimelineCollectorManager#startWebApp is getting existing config and then changing the HTTP initializers and setting to same conf object. Fresh conf is to be used while startWebApp call.
> NodeManager is giving 403 GSS exception post upgrade to 3.1 in secure mode
> --------------------------------------------------------------------------
>
> Key: YARN-8399
> URL: https://issues.apache.org/jira/browse/YARN-8399
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineservice
> Reporter: Sunil Govindan
> Assignee: Sunil Govindan
> Priority: Major
> Attachments: YARN-8399.001.patch
>
>
> Getting 403 GSS exception while accessing NM http port via curl.
> {code:java}
> curl -k -i --negotiate -u: https://<nm_host>:<port>/node
> HTTP/1.1 401 Authentication required
> Date: Tue, 05 Jun 2018 17:59:00 GMT
> Date: Tue, 05 Jun 2018 17:59:00 GMT
> Pragma: no-cache
> WWW-Authenticate: Negotiate
> Set-Cookie: hadoop.auth=; Path=/; Secure; HttpOnly
> Cache-Control: must-revalidate,no-cache,no-store
> Content-Type: text/html;charset=iso-8859-1
> Content-Length: 264
> HTTP/1.1 403 GSSException: Failure unspecified at GSS-API level (Mechanism level: Request is a replay (34)){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org