John: Quite simple really.
You have \\afs\cs.wisc.edu\s\std\bin in the PATH environment variable under which the afsd_service.exe is started. The end result is that every time afsd_service.exe tries to load a dll the computer tries to access \\afs\cs.wisc.edu\s\std\bin and times out because "guess what?" the afs service has not yet started. Jeffrey Altman Secure Endpoints Inc. John Perkins wrote: > We've seen a handful of computers at our site get stuck during the > AFS initialization sequence. Here is a snippet from the afsd_init.log: > > 10/23/2008 3:07:31 PM: cm_GetRootCellName code 0, cm_freelanceEnabled= 1, > rcn= c > s.wisc.edu > 10/23/2008 3:07:31 PM: Mountpoint[0] = .cs%cs.wisc.edu:root.cell. > 10/23/2008 3:07:31 PM: Mountpoint[1] = .cs.wisc.edu%cs.wisc.edu:root.cell. > 10/23/2008 3:07:31 PM: Mountpoint[2] = cs.wisc.edu#cs.wisc.edu:root.cell. > 10/23/2008 3:07:31 PM: Mountpoint[3] = @cell#cs.wisc.edu:root.cell. > 10/23/2008 3:07:31 PM: Mountpoint[4] = cs#cs.wisc.edu:root.cell. > 10/23/2008 3:07:31 PM: Mountpoint[5] = [EMAIL PROTECTED]:root.cell. > 10/23/2008 3:07:31 PM: cm_GetSCache code 0 scache 2a1f408 > 10/23/2008 3:07:31 PM: cm_InitDaemon complete > 10/23/2008 3:07:31 PM: RPC server listening > 10/23/2008 3:07:31 PM: MpsSvc Service could not be opened for query: 0x424 > 10/23/2008 3:07:31 PM: StoreAnsiFilenames = 0 > 10/23/2008 3:07:31 PM: EnableSMBAsyncStore = 1 > 10/23/2008 3:07:31 PM: AutoStart 0x2 > 10/23/2008 3:07:31 PM: SMBAsyncStoreSize = 131072 > 10/23/2008 3:07:31 PM: daemonCheckDownInterval is 180 > 10/23/2008 3:07:31 PM: LAN adapter number 3 > 10/23/2008 3:07:31 PM: daemonCheckUpInterval is 240 > 10/23/2008 3:07:31 PM: Using >AFS< as SMB server name > 10/23/2008 3:07:31 PM: daemonCheckVolInterval is 3600 > 10/23/2008 3:07:31 PM: smb_localNamep is >AFS< > 10/23/2008 3:07:31 PM: daemonCheckCBInterval is 60 > 10/23/2008 3:07:31 PM: Netbios NCBRESET lana 3 succeeded > 10/23/2008 3:07:31 PM: daemonCheckVolCBInterval is 0 > 10/23/2008 3:07:31 PM: lana_list.length 1 > 10/23/2008 3:07:31 PM: daemonCheckLockInterval is 60 > 10/23/2008 3:07:31 PM: daemonCheckTokenInterval is 180 > 10/23/2008 3:07:31 PM: daemonCheckOfflineVolInterval is 600 > 10/23/2008 3:07:31 PM: daemonPerformanceTuningInterval is 0 > 10/23/2008 3:07:34 PM: Netbios NCBADDNAME lana=3 code=0 retcode=0 complete=0 > 10/23/2008 3:07:34 PM: Netbios NCBADDNAME added new name >AFS < > 10/23/2008 3:07:34 PM: Netbios NCBADDNAME succeeded on lana 3 > > 10/23/2008 3:07:34 PM: smb_NetbiosInit smb_LANadapter=3 > 10/23/2008 3:07:34 PM: Setting SMB server domain name to [RACHEL] > 10/23/2008 3:07:34 PM: smb_StartListeners > 10/23/2008 3:07:34 PM: smb_Init complete > 10/23/2008 3:07:34 PM: Windows Firewall Configuration succeeded > 10/23/2008 3:07:34 PM: GlobalAutoMap thread completed > 10/23/2008 3:28:23 PM: Mountpoint[0] = .cs%cs.wisc.edu:root.cell. > 10/23/2008 3:28:23 PM: Mountpoint[1] = .cs.wisc.edu%cs.wisc.edu:root.cell. > 10/23/2008 3:28:23 PM: Mountpoint[2] = cs.wisc.edu#cs.wisc.edu:root.cell. > 10/23/2008 3:28:23 PM: Mountpoint[3] = @cell#cs.wisc.edu:root.cell. > 10/23/2008 3:28:23 PM: Mountpoint[4] = cs#cs.wisc.edu:root.cell. > 10/23/2008 3:28:23 PM: Mountpoint[5] = [EMAIL PROTECTED]:root.cell. > > Once we see the Mountpoint[x] entries show up, the AFS client is > running properly. My question is what would cause this to wait 20 > minutes before this continues on. > > I did collect an "fs trace" log (trace starting when server starts) in > /afs/cs.wisc.edu/u/j/o/john/public/html/winafs-logs/1.5.5403-delay > > If anyone can shed some light on what might be causing this delay, > please enlighten me. >
smime.p7s
Description: S/MIME Cryptographic Signature
