[OpenAFS] Rxkd errors, dropped tokens, and mismatched version numbers...

Derrick Brashear shadow@gmail.com
Tue, 18 Dec 2007 16:45:03 -0500


------=_Part_18144_7636116.1198014303621
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

if you're using krb5 directly, not via krb524, transarc servers can't cope,
and you'll need to upgrade them.


On Dec 18, 2007 4:40 PM, Bill Stivers <stiversb@ucsc.edu> wrote:

> Hey all:
>
> I've asked a similar question before, so I do apologise,
> but I was unable to find any additional information on
> what could be done in order to prevent or fix this error
> in our present context.
>
> At UCSC we upgraded from an exclusively transarc
> environment approximately 2 years ago to a mixed
> transarc/openafs environment.  We run some webservers with
> kerberos keytabs, and tokens generated for authentication
> purposes.. and on our Solaris boxes everything was fine..
> but when the services were moved to a RHEL 4-based
> platform, suddenly we began to see serious problems with
> RXK errors.  19270408- the mismatched key version number
> error.  I checked keytabs on the system, and I believed
> that I had taken care of the problem by harmonizing the
> keytab version numbers among all those used by kerberos to
> obtain tokens, but the errors are still kicking around.
>
> I'm wondering if this is a "transarc must go away
> entirely" sort of error situation, if it's a k4 versus k5
> sort of issue, and as well, if anyone has any experience
> with the situation.
>
> Any feedback would be much appreciated.
>
> --
> Bill Stivers
> ITS Core Technologies Systems Admin./Engr.
> UC Santa Cruz
>
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>

------=_Part_18144_7636116.1198014303621
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

if you&#39;re using krb5 directly, not via krb524, transarc servers can&#39;t cope, and you&#39;ll need to upgrade them.<br><br><br><div class="gmail_quote">On Dec 18, 2007 4:40 PM, Bill Stivers &lt;<a href="mailto:stiversb@ucsc.edu">
stiversb@ucsc.edu</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hey all:<br><br>I&#39;ve asked a similar question before, so I do apologise,
<br>but I was unable to find any additional information on<br>what could be done in order to prevent or fix this error<br>in our present context.<br><br>At UCSC we upgraded from an exclusively transarc<br>environment approximately 2 years ago to a mixed
<br>transarc/openafs environment. &nbsp;We run some webservers with<br>kerberos keytabs, and tokens generated for authentication<br>purposes.. and on our Solaris boxes everything was fine..<br>but when the services were moved to a RHEL 4-based
<br>platform, suddenly we began to see serious problems with<br>RXK errors. &nbsp;19270408- the mismatched key version number<br>error. &nbsp;I checked keytabs on the system, and I believed<br>that I had taken care of the problem by harmonizing the
<br>keytab version numbers among all those used by kerberos to<br>obtain tokens, but the errors are still kicking around.<br><br>I&#39;m wondering if this is a &quot;transarc must go away<br>entirely&quot; sort of error situation, if it&#39;s a k4 versus k5
<br>sort of issue, and as well, if anyone has any experience<br>with the situation.<br><br>Any feedback would be much appreciated.<br><br>--<br>Bill Stivers<br>ITS Core Technologies Systems Admin./Engr.<br>UC Santa Cruz<br>
<br>_______________________________________________<br>OpenAFS-info mailing list<br><a href="mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a><br><a href="https://lists.openafs.org/mailman/listinfo/openafs-info" target="_blank">
https://lists.openafs.org/mailman/listinfo/openafs-info</a><br></blockquote></div><br>

------=_Part_18144_7636116.1198014303621--