[OpenAFS] afs on windows problem

Robbie Foust rfoust@duke.edu
Thu, 23 Mar 2006 15:28:03 -0500


Actually it looks like the afsd_service blew up again.  I got a minidump=20
- I'll send a bug report.

Thanks,

- Robbie


Robbie Foust wrote:

> Here's a new error - got two of these today (same client as before):
>
> Event Type:    Error
> Event Source:    AFS Client
> Event Category:    None
> Event ID:    1001
> Date:        3/23/2006
> Time:        1:07:47 PM
> User:        N/A
> Computer:    (removed)
> Description:
> The description for Event ID ( 1001 ) in Source ( AFS Client ) cannot=20
> be found. The local computer may not have the necessary registry=20
> information or message DLL files to display messages from a remote=20
> computer. You may be able to use the /AUXSOURCE=3D flag to retrieve thi=
s=20
> description; see Help and Support for details. The following=20
> information is part of the event: Bad vcp!! :=20
> LSNs[idx_session]=3D[1],lanas[idx_session]=3D[4],ncbp->ncb_lsn=3D[1],nc=
bp->ncb_lana_num=3D[4].=20
>
> Data:
> 0000: 95 00 01 00 a8 40 c3 09   ?...=C2=AE@=E2=88=9A.
> 0008: 31 00 00 00 00 00 00 00   1.......
> 0010: 00 00 00 00 00 00 00 00   ........
> 0018: 00 00 00 00 00 00 00 00   ........
> 0020: 00 00 00 00 00 00 00 00   ........
> 0028: 00 00 00 00 00 00 00 00   ........
> 0030: 04 00 00 00 00 00 00 00   ........
> 0038: 31 00 00 00 a8 04 00 00   1...=C2=AE...
>
>
> Robbie Foust wrote:
>
>> Thanks for the info.  I've bumped it up to 60 seconds, but it didn't=20
>> help any.  I have 14 of these events so far today.  I guess its=20
>> really not a big deal since the client still seems to work fine and=20
>> since you already know what causes it.
>>
>> - Robbie
>>
>>
>> Jeffrey Altman wrote:
>>
>>> The warning is caused because the CIFS client timed out before the RX
>>> request to the file server completed.   This is not unusual.  The RX
>>> request will complete when it completes and the CIFS client will crea=
te
>>> a new connection.
>>>
>>> You can try increasing the minimum timeout period for the CIFS client
>>> in order to reduce the number of these errors.  The default timeout
>>> period is 45 seconds.
>>>
>>>> From the OpenAFS release notes:
>>>
>>>
>>>
>>> [HKLM\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters]
>>> SessTimeout
>>>
>>> If the minimum SMB timeout is not specified the value is 45 seconds.
>>> See http://support.microsoft.com:80/support/kb/articles/Q102/0/67.asp
>>>
>>> Jeffrey Altman
>>>
>>>
>>> Robbie Foust wrote:
>>> =20
>>>
>>>> I've updated my terminal server to RC10 last night. This morning I s=
ee
>>>> about 5 event log entries that were logged throughout the morning th=
at
>>>> show this (pasted below). What is the best way to figure out what is
>>>> causing this warning?
>>>>
>>>> Event Type: Warning
>>>> Event Source: AFS Client
>>>> Event Category: None
>>>> Event ID: 1005
>>>> Date: 3/22/2006
>>>> Time: 10:13:22 AM
>>>> User: N/A
>>>> Computer: (removed)
>>>> Description:
>>>> The description for Event ID ( 1005 ) in Source ( AFS Client )=20
>>>> cannot be
>>>> found. The local computer may not have the necessary registry
>>>> information or message DLL files to display messages from a remote
>>>> computer. You may be able to use the /AUXSOURCE=3D flag to retrieve =
this
>>>> description; see Help and Support for details. The following=20
>>>> information
>>>> is part of the event: Pkt straddled session startup, took 0 ms, ncb
>>>> length 133.
>>>> Data:
>>>> 0000: ff 53 4d 42 72 00 00 00 =CB=87SMBr...
>>>> 0008: 00 18 53 c8 00 00 00 00 ..S=C2=BB....
>>>> 0010: 00 00 00 00 00 00 00 00 ........
>>>> 0018: 00 00 ff fe 00 00 00 00 ..=CB=87=CB=9B....
>>>> 0020: 00 62 00 02 50 43 20 4e .b..PC N
>>>> 0028: 45 54 57 4f 52 4b 20 50 ETWORK P
>>>> 0030: 52 4f 47 52 41 4d 20 31 ROGRAM 1
>>>> 0038: 2e 30 00 02 4c 41 4e 4d .0..LANM
>>>> 0040: 41 4e 31 2e 30 00 02 57 AN1.0..W
>>>> 0048: 69 6e 64 6f 77 73 20 66 indows f
>>>> 0050: 6f 72 20 57 6f 72 6b 67 or Workg
>>>> 0058: 72 6f 75 70 73 20 33 2e roups 3.
>>>> 0060: 31 61 00 02 4c 4d 31 2e 1a..LM1.
>>>> 0068: 32 58 30 30 32 00 02 4c 2X002..L
>>>> 0070: 41 4e 4d 41 4e 32 2e 31 ANMAN2.1
>>>> 0078: 00 02 4e 54 20 4c 4d 20 ..NT LM
>>>> 0080: 30 2e 31 32 00 0.12.
>>>>
>>>>
>>>>
>>>>
>>>> Jeffrey Altman wrote:
>>>>
>>>> =20
>>>>
>>>>> Please send bug reports to openafs-bugs@openafs.org.
>>>>> Minidumps contain mucho private data and should not be published
>>>>> publicly.  After you file a bug report you will receive a response
>>>>> indicating what you should do with the dump file.
>>>>>
>>>>> in your bug report state what you mean by afsd_service.exe being
>>>>> unresponsive.
>>>>>
>>>>> Jeffrey Altman
>>>>>
>>>>>
>>>>> Robbie Foust wrote:
>>>>>
>>>>>
>>>>>   =20
>>>>>
>>>>>> Would this problem also cause the afsd_service to become
>>>>>> unresponsive? I created a mindump just in case (what do I do with
>>>>>> it?).  I'll still
>>>>>> upgrade to the latest RC tonight.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> - Robbie
>>>>>>
>>>>>>
>>>>>> Robbie Foust wrote:
>>>>>>
>>>>>> =20
>>>>>>     =20
>>>>>>
>>>>>>> Jeffrey Altman wrote:
>>>>>>>
>>>>>>>          =20
>>>>>>>
>>>>>>>> Christopher D. Clausen wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>              =20
>>>>>>>>
>>>>>>>>> I believe he said he was using build 1.4.0097.  Isn't that
>>>>>>>>> 1.4.1-rc7? The build that marked servers as down even when=20
>>>>>>>>> they were
>>>>>>>>> up?
>>>>>>>>>
>>>>>>>>>                   =20
>>>>>>>>
>>>>>>>>
>>>>>>>> Yes indeed.  Somehow that item is no longer in the changelog I=20
>>>>>>>> keep.
>>>>>>>>
>>>>>>>> The current release is 1.4.1-rc10.  Please upgrade.
>>>>>>>>
>>>>>>>>
>>>>>>>>               =20
>>>>>>>
>>>>>>>
>>>>>>> Awesome - I'll do that tonight.   At least I know what the=20
>>>>>>> problem is
>>>>>>> now though. :-)
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> - Robbie
>>>>>>>
>>>>>>>           =20
>>>>>>
>>>>>>
>>>>>> =20
>>>>>>      =20
>>>>>
>>>>>
>>>>  =20
>>>
>>>
>>
>>
>
>


--=20
Robbie Foust, CISSP, A+
OIT - CSI
Duke University