<?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: GSS exception error seen in a scenario even after having valid kerberos ticket in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/GSS-exception-error-seen-in-a-scenario-even-after-having/m-p/231199#M193043</link>
    <description>&lt;P&gt;my guess would be that this is a race condition on env-2, leading to the situation that your process doesn't really see the renewed ticket. Can you change the logging, so that the threads are logging the ticket dates when failing?&lt;/P&gt;&lt;P&gt;If it is a load issue with the KDC, you would see the error messages on other clients as well, and it should also by chance go away again. My assumption is that you have thread by thread getting the authentication error, and when all your threads are 'down' you see that no file is moved anymore.&lt;/P&gt;&lt;P&gt;just to be sure (as mentioned I don't think the root cause is to be found here): check that the hfds name node and your AD are in time sync also.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Dec 2017 15:43:31 GMT</pubDate>
    <dc:creator>arald</dc:creator>
    <dc:date>2017-12-27T15:43:31Z</dc:date>
  </channel>
</rss>

