<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Sentry Kerberos Issue in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sentry-Kerberos-Issue/m-p/21802#M3780</link>
    <description>&lt;P&gt;Many thanks Darren!&lt;/P&gt;</description>
    <pubDate>Wed, 19 Nov 2014 14:57:42 GMT</pubDate>
    <dc:creator>eoino</dc:creator>
    <dc:date>2014-11-19T14:57:42Z</dc:date>
    <item>
      <title>Sentry Kerberos Issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sentry-Kerberos-Issue/m-p/21741#M3778</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a CDH 5.1.3 cluster managed by cloudera manager. It's fully kerberised and uses AD 2003 as the KDC. I have enabled sentry and everything seems to work fine. However, every morning, beeline stops working and the hiveserver2 log shows the below issue. Currently the only fix i have is to restart hiveserver. With sentry disabled everything works fine. I've tried redeploying kerberos configs, regenerating credentials and increasing the kerberos ticket timeout. Anyone have any ideas where to look?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;8:34:40.148 AM&lt;/TD&gt;&lt;TD&gt;ERROR&lt;/TD&gt;&lt;TD&gt;sentry.org.ape.thrift.transport.TSaslTransport&lt;/TD&gt;&lt;TD&gt;&lt;PRE&gt;SASL negotiation failure&lt;BR /&gt;javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]&lt;BR /&gt;	at com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212)&lt;BR /&gt;	at sentry.org.apache.thrift.transport.TSaslClientTransport.handleSaslStartMessage(TSaslClientTransport.java:94)&lt;BR /&gt;	at sentry.org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:253)&lt;BR /&gt;	at sentry.org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:1)&lt;BR /&gt;	at org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClient$UgiSaslClientTransport.baseOpen(SentryPolicyServiceClient.java:115)&lt;BR /&gt;	at org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClient$UgiSaslClientTransport.access$000(SentryPolicyServiceClient.java:77)&lt;BR /&gt;	at org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClient$UgiSaslClientTransport$1.run(SentryPolicyServiceClient.java:101)&lt;BR /&gt;	at org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClient$UgiSaslClientTransport$1.run(SentryPolicyServiceClient.java:99)&lt;BR /&gt;	at java.security.AccessController.doPrivileged(Native Method)&lt;BR /&gt;	at javax.security.auth.Subject.doAs(Subject.java:415)&lt;BR /&gt;	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1554)&lt;BR /&gt;	at org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClient$UgiSaslClientTransport.open(SentryPolicyServiceClient.java:99)&lt;BR /&gt;	at org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClient.&amp;lt;init&amp;gt;(SentryPolicyServiceClient.java:151)&lt;BR /&gt;	at org.apache.sentry.provider.db.SimpleDBProviderBackend.&amp;lt;init&amp;gt;(SimpleDBProviderBackend.java:52)&lt;BR /&gt;	at org.apache.sentry.provider.db.SimpleDBProviderBackend.&amp;lt;init&amp;gt;(SimpleDBProviderBackend.java:48)&lt;BR /&gt;	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)&lt;BR /&gt;	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)&lt;BR /&gt;	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)&lt;BR /&gt;	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)&lt;BR /&gt;	at org.apache.sentry.binding.hive.authz.HiveAuthzBinding.getAuthProvider(HiveAuthzBinding.java:247)&lt;BR /&gt;	at org.apache.sentry.binding.hive.authz.HiveAuthzBinding.&amp;lt;init&amp;gt;(HiveAuthzBinding.java:88)&lt;BR /&gt;	at org.apache.sentry.binding.hive.authz.HiveAuthzBinding.&amp;lt;init&amp;gt;(HiveAuthzBinding.java:81)&lt;BR /&gt;	at org.apache.sentry.binding.hive.HiveAuthzBindingHook.&amp;lt;init&amp;gt;(HiveAuthzBindingHook.java:98)&lt;BR /&gt;	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)&lt;BR /&gt;	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)&lt;BR /&gt;	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)&lt;BR /&gt;	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)&lt;BR /&gt;	at java.lang.Class.newInstance(Class.java:374)&lt;BR /&gt;	at org.apache.hadoop.hive.ql.hooks.HookUtils.getHooks(HookUtils.java:59)&lt;BR /&gt;	at org.apache.hadoop.hive.ql.Driver.getHooks(Driver.java:1162)&lt;BR /&gt;	at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:440)&lt;BR /&gt;	at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:352)&lt;BR /&gt;	at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:995)&lt;BR /&gt;	at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:988)&lt;BR /&gt;	at org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:98)&lt;BR /&gt;	at org.apache.hive.service.cli.operation.SQLOperation.run(SQLOperation.java:163)&lt;BR /&gt;	at org.apache.hive.service.cli.session.HiveSessionImpl.runOperationWithLogCapture(HiveSessionImpl.java:514)&lt;BR /&gt;	at org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:222)&lt;BR /&gt;	at org.apache.hive.service.cli.session.HiveSessionImpl.executeStatement(HiveSessionImpl.java:204)&lt;BR /&gt;	at org.apache.hive.service.cli.CLIService.executeStatement(CLIService.java:168)&lt;BR /&gt;	at org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:316)&lt;BR /&gt;	at org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1373)&lt;BR /&gt;	at org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1358)&lt;BR /&gt;	at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)&lt;BR /&gt;	at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)&lt;BR /&gt;	at org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:57)&lt;BR /&gt;	at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:244)&lt;BR /&gt;	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)&lt;BR /&gt;	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)&lt;BR /&gt;	at java.lang.Thread.run(Thread.java:745)&lt;BR /&gt;Caused by: GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)&lt;BR /&gt;	at sun.security.jgss.krb5.Krb5InitCredential.getInstance(Krb5InitCredential.java:147)&lt;BR /&gt;	at sun.security.jgss.krb5.Krb5MechFactory.getCredentialElement(Krb5MechFactory.java:121)&lt;BR /&gt;	at sun.security.jgss.krb5.Krb5MechFactory.getMechanismContext(Krb5MechFactory.java:187)&lt;BR /&gt;	at sun.security.jgss.GSSManagerImpl.getMechanismContext(GSSManagerImpl.java:223)&lt;BR /&gt;	at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:212)&lt;BR /&gt;	at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:179)&lt;BR /&gt;	at com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:193)&lt;BR /&gt;	... 49 more&lt;/PRE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;8:34:40.151 AM&lt;/TD&gt;&lt;TD&gt;WARN&lt;/TD&gt;&lt;TD&gt;org.apache.hadoop.security.UserGroupInformation&lt;/TD&gt;&lt;TD&gt;&lt;PRE&gt;PriviledgedActionException as:hive/gb-slo-hdp-0001.dunnhumby.co.uk@DUNNHUMBY.CO.UK (auth:KERBEROS) cause:sentry.org.apache.thrift.transport.TTransportException: GSS initiate failed&lt;/PRE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Fri, 16 Sep 2022 09:13:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sentry-Kerberos-Issue/m-p/21741#M3778</guid>
      <dc:creator>eoino</dc:creator>
      <dc:date>2022-09-16T09:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: Sentry Kerberos Issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sentry-Kerberos-Issue/m-p/21762#M3779</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;This is a known issue in Sentry that was fixed in CDH 5.1.4 and 5.2. Please upgrade your Cloudera Manager, then upgrade CDH to resolve this issue.&lt;BR /&gt;&lt;BR /&gt;Be sure to follow upgrade instructions, as there are special steps required when upgrading to CDH 5.2.&lt;BR /&gt;&lt;A target="_blank" href="http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/installation_upgrade.html"&gt;http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/installation_upgrade.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Darren</description>
      <pubDate>Tue, 18 Nov 2014 19:28:18 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sentry-Kerberos-Issue/m-p/21762#M3779</guid>
      <dc:creator>Darren</dc:creator>
      <dc:date>2014-11-18T19:28:18Z</dc:date>
    </item>
    <item>
      <title>Re: Sentry Kerberos Issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sentry-Kerberos-Issue/m-p/21802#M3780</link>
      <description>&lt;P&gt;Many thanks Darren!&lt;/P&gt;</description>
      <pubDate>Wed, 19 Nov 2014 14:57:42 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sentry-Kerberos-Issue/m-p/21802#M3780</guid>
      <dc:creator>eoino</dc:creator>
      <dc:date>2014-11-19T14:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: Sentry Kerberos Issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sentry-Kerberos-Issue/m-p/62471#M3781</link>
      <description>&lt;P&gt;I'm experiencing the same issue in 5.7.0. Can you offer any detail on the issue and why we might be sseing it in 5.7.0?&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2017 17:36:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Sentry-Kerberos-Issue/m-p/62471#M3781</guid>
      <dc:creator>wjsandman</dc:creator>
      <dc:date>2017-12-04T17:36:49Z</dc:date>
    </item>
  </channel>
</rss>

