[OpenAFS] Linux client connection timed out after server failure

Steven Jenkins steven.jenkins@gmail.com
Thu, 16 Aug 2012 12:31:13 -0400


--047d7b16021365eae704c76492e1
Content-Type: text/plain; charset=ISO-8859-1

Two things come to mind:

1- Sometimes fileservers are also db servers, and the 'connection timed
out' was because I forgot to update CellServDB and restart the client.  If
you watch network traffic, you would see this as an attempt to connect to
the old IP address but on the vlserver port, not the fileserver port.
2- I don't recall the interaction of open files and fs checkv, but there
might be a bug there.  That would be straightforward to test.

Steven

On Thu, Aug 16, 2012 at 12:20 PM, chas williams - CONTRACTOR <
chas@cmf.nrl.navy.mil> wrote:

> On Thu, 16 Aug 2012 11:19:09 -0400
> Bob Hoffman <hoffman@cs.pitt.edu> wrote:
>
> > On 8/16/12 10:53 AM, Derrick Brashear wrote:
> > > it should recover in 2 hours, which is the vldb refresh time.
> >
> > Apparently that doesn't work for me.  After six days, I was still
> > getting "Connection timed out."
>
> i had the same thing happen to me as well during a server change.
> after 2 hours, the volume information still hadnt updated.  fs checkv
> did fix things though.  seems like there might be a bug.
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>

--047d7b16021365eae704c76492e1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Two things come to mind:<br><br>1- Sometimes fileservers are also db server=
s, and the &#39;connection timed out&#39; was because I forgot to update Ce=
llServDB and restart the client.=A0 If you watch network traffic, you would=
 see this as an attempt to connect to the old IP address but on the vlserve=
r port, not the fileserver port.<br>
2- I don&#39;t recall the interaction of open files and fs checkv, but ther=
e might be a bug there.=A0 That would be straightforward to test.<br><br>St=
even<br><br><div class=3D"gmail_quote">On Thu, Aug 16, 2012 at 12:20 PM, ch=
as williams - CONTRACTOR <span dir=3D"ltr">&lt;<a href=3D"mailto:chas@cmf.n=
rl.navy.mil" target=3D"_blank">chas@cmf.nrl.navy.mil</a>&gt;</span> wrote:<=
br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On Thu, 16 Aug 2012 11:19:09 -0400<br>
Bob Hoffman &lt;<a href=3D"mailto:hoffman@cs.pitt.edu">hoffman@cs.pitt.edu<=
/a>&gt; wrote:<br>
<br>
&gt; On 8/16/12 10:53 AM, Derrick Brashear wrote:<br>
&gt; &gt; it should recover in 2 hours, which is the vldb refresh time.<br>
&gt;<br>
&gt; Apparently that doesn&#39;t work for me. =A0After six days, I was stil=
l<br>
&gt; getting &quot;Connection timed out.&quot;<br>
<br>
i had the same thing happen to me as well during a server change.<br>
after 2 hours, the volume information still hadnt updated. =A0fs checkv<br>
did fix things though. =A0seems like there might be a bug.<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>

--047d7b16021365eae704c76492e1--