[OpenAFS] 1.3.6000 delays - are they caused by DNS?

[Christopher D. Clausen]

I can also confirm the problems.
http://www.acm.uiuc.edu/~cclausen/OpenAFSForWindows-1.3.6000-afsd_init_log1.txt

Setting UseDNS = 0 did not help.

I am running Windows 2003 Server, Enterprise Edition with KfW 2.5 and
using the loopback adapter.  OpenAFS was working fine for the most part
with 1.3.52 with only the crashes that I reported through rt, but those
appeared to have been caused by mis-matched versions of some of the
files.

Here is info from the event log:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date:  19-Mar-04
Time:  3:43:10p
User:  N/A
Computer: KBS-CDC
Description:
Faulting application afsd_service.exe, version 1.3.6000.0, faulting
module unknown, version 0.0.0.0, fault address 0x00000000.

It appears as though the afspthread.dll in the installer does not match
the version number of everything else:
 1.3.5299.0 shp     10,752 03-18-2004 afspthread.dll

Could that be a problem?

I have also noticed that typing in "tokens" at a cmd prompt seems to
take longer that it did under the 1.3.52 client.

On Friday, March 19, 2004 2:57p <rmdyer@uncc.edu> wrote:
> Jeffrey,
>
> I can confirm the problems others are having.
>
> 1.  Running "afs_config.exe" then traversing from the "General" tab
> to the "Drive Letters" tab takes about 10 seconds.
>
> 2.  Runing the "afscreds.exe" then choosing the "Drive Letters" tab
> also causes a pause of about 10 seconds.
>
> 3.  Stopping the AFS service sometimes causes a crash, aka...send
> mail to Microsoft, etc.
>
> 4.  Changing the UseDNS value has no effect.
>
> Here's a copy of my "c:\winnt\temp\afsd_init.log"...
>
>
http://www.coe.uncc.edu/~rmdyer/OpenAFSforWindows-1-3-6000_afsd_init_log1.txt
>
> Rodney
>
>
> At 01:56 PM 3/19/2004, Jeffrey Altman wrote:
>> for those experiencing delays with afscreds.exe.
>> do the delays go away if you set?
>>
>>  HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters
>>       UseDNS (DWORD) = 0x00
>>
>> and then restart the AFS Client Service?
>>
>> Jeffrey Altman