You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/12/23 21:44:00 UTC
[jira] [Resolved] (IMPALA-5385) Print appropriate error for failed
TGT creation due to /tmp being full
[ https://issues.apache.org/jira/browse/IMPALA-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-5385.
-----------------------------------
Resolution: Duplicate
IMPALA-9359 addresses the general problem.
> Print appropriate error for failed TGT creation due to /tmp being full
> ----------------------------------------------------------------------
>
> Key: IMPALA-5385
> URL: https://issues.apache.org/jira/browse/IMPALA-5385
> Project: IMPALA
> Issue Type: Bug
> Components: Security
> Reporter: Sailesh Mukil
> Priority: Major
> Labels: errorhandling
>
> When CS is not able to generate TGT due to lack of space, it crashes after start and the error shows up as
> javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
> at com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212)
> at org.apache.thrift.transport.TSaslClientTransport.handleSaslStartMessage(TSaslClientTransport.java:94)
> at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:253)
> at org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
> We need the error to show that /tmp is full instead of the just the absence of a TGT.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)