[OpenAFS] connection timeouts

Derrick J Brashear shadow@dementia.org
Mon, 22 May 2006 13:11:39 -0400 (EDT)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.andrew.cmu.edu id k4MHBeRl025491

On Mon, 22 May 2006, Juha [UTF-8] J=E4ykk=E4 wrote:

>> Using -s 1500 -x would provide packet payloads. The last 32 bits of th=
>> abort is an error code. I bet it would be -455 (RXGEN_OPCODE), I think
>> that's ffff fe38
> I'll do that next time: after 9 hours of misbehaving, the client starte=
> working again at 14:40:07 *on its own* (i.e. just like if there had
> actually been a network outage - except there never was).

If Ken is right (encrypted) I bet it started working again because the=20
tickets expired.

>>>    call 0: # 182, state precall, mode: error
>> Ok, lagrange.tfy.utu.fi is and that connection is mode
>> error.
> Which means exactly what? And how do I fix it (the next time this
> happens)?

You don't fix it. I think one of the Rx changes we made since 1.3.87 may=20
have fixed it though.