[OpenAFS] OpenAFS Windows Client not able to access directory

[David Bear]

--0016e64beb54a4817a046e981b22
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

We see this behavior on occasion as well. Somethings we try:
1) we completely erase the afscache file -- actually stopping the afs
client, renaming the existing afscache file, then restarting the client
2) watch the event logs for signs the afs service is stopping and restarting
unexpectedly -- we have seen the afs client service restart itself and in
process loose tokens --
3) We did get a patch to fix one problem dealing with cache corruption cause
by some old file servers (I think, though secure-endpoints can more fully
comment on the fix)
4) Most of the time, we struggle with this kind of issue for days, then the
issue vanishes -- The symptoms are as outlined below, windows client, unable
to access some locations in afs for which they do have appropriate acls, but
which a specific client machine fails to open.

On Fri, Jul 10, 2009 at 7:16 AM, Karen Eldredge <
karen.eldredge@infoprint.com> wrote:

>
> We have a OpenAFS Windows client  and the user on that system was not able
> to
> access one directory even though the ACLs showed he has access permission.
>  The
> user was able to access this directory from another AFS client, so I
> believe
> that this is an client issue.  Since it was just one AFS directory he could
> not
> access we tried running fs flushv & fs checkv via the  Network Identity
> manager.
>
> When trying to access the AFS directory we got the message network
> directory
> not available (not sure if this is the exact message).  Then we ran the
> cmdebug
> and got the message "failed to get cache entry ...  server or network not
> responding".   We are able to ping the AFS servers.
>
> When this happens what are the best ways to debug the problem?
>
>
>
> _____________________________________________________________________________
> "This message and any attachments are solely for the intended recipient and
> may contain confidential or privileged information. If you are not the
> intended recipient, any disclosure, copying, use, or distribution of the
> information included in this message and any attachments is prohibited. If
> you have received this communication in error, please notify us by reply
> e-mail and immediately and permanently delete this message and any
> attachments. Thank you."
> _____________________________________________________________________________
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>



-- 
David Bear
College of Public Programs at ASU
602-464-0424

--0016e64beb54a4817a046e981b22
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

We see this behavior on occasion as well. Somethings we try:<br>1) we compl=
etely erase the afscache file -- actually stopping the afs client, renaming=
 the existing afscache file, then restarting the client<br>2) watch the eve=
nt logs for signs the afs service is stopping and restarting unexpectedly -=
- we have seen the afs client service restart itself and in process loose t=
okens -- <br>
3) We did get a patch to fix one problem dealing with cache corruption caus=
e by some old file servers (I think, though secure-endpoints can more fully=
 comment on the fix)<br>4) Most of the time, we struggle with this kind of =
issue for days, then the issue vanishes -- The symptoms are as outlined bel=
ow, windows client, unable to access some locations in afs for which they d=
o have appropriate acls, but which a specific client machine fails to open.=
<br>
<br><div class=3D"gmail_quote">On Fri, Jul 10, 2009 at 7:16 AM, Karen Eldre=
dge <span dir=3D"ltr">&lt;<a href=3D"mailto:karen.eldredge@infoprint.com">k=
aren.eldredge@infoprint.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt=
 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
We have a OpenAFS Windows client =C2=A0and the user on that system was not =
able to<br>
access one directory even though the ACLs showed he has access permission. =
=C2=A0The<br>
user was able to access this directory from another AFS client, so I believ=
e<br>
that this is an client issue. =C2=A0Since it was just one AFS directory he =
could not<br>
access we tried running fs flushv &amp; fs checkv via the =C2=A0Network Ide=
ntity<br>
manager.<br>
<br>
When trying to access the AFS directory we got the message network director=
y<br>
not available (not sure if this is the exact message). =C2=A0Then we ran th=
e cmdebug<br>
and got the message &quot;failed to get cache entry ... =C2=A0server or net=
work not<br>
responding&quot;. =C2=A0 We are able to ping the AFS servers.<br>
<br>
When this happens what are the best ways to debug the problem?<br>
<br>
<br>
___________________________________________________________________________=
__<br>
&quot;This message and any attachments are solely for the intended recipien=
t and may contain confidential or privileged information. If you are not th=
e intended recipient, any disclosure, copying, use, or distribution of the =
information included in this message and any attachments is prohibited. If =
you have received this communication in error, please notify us by reply e-=
mail and immediately and permanently delete this message and any attachment=
s. Thank you.&quot; _______________________________________________________=
______________________<br>

_______________________________________________<br>
OpenAFS-info mailing list<br>
<a href=3D"mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a><br=
>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info" target=
=3D"_blank">https://lists.openafs.org/mailman/listinfo/openafs-info</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>David Bear<br>College o=
f Public Programs at ASU<br>602-464-0424<br>

--0016e64beb54a4817a046e981b22--