Windows AFS client refuses to start.

View: New views
4 Messages — Rating Filter:   Alert me  

Windows AFS client refuses to start.

by Anders Magnusson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

we have entered a state on the computers in a newly installed WinXP lab
where the afs daemon won't start, and I do not really understand what is
the problem.

I have attached the afsd_init.log file, someone (Jeffrey? :-)  may
understand the magics written in it.

-- Ragge

14:20:30: Create log file
14:20:30: Created log file
PATH=C:\Program Files\Autodesk\Maya2008\bin;C:\Program Files\Autodesk\AliasStudio2009\bin;C:\Program Files\Hummingbird\Connectivity\12.00\Exceed;C:\PROGRA~1\MKSTOO~1\bin;C:\PROGRA~1\MKSTOO~1\bin\X11;C:\PROGRA~1\MKSTOO~1\mksnt;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared\;C:\Program Files\Windows Imaging\;C:\Program Files\MATLAB\R2008a\bin;C:\Program Files\MATLAB\R2008a\bin\win32;C:\Robcad\bin\;C:\Robcad\xml\;C:\Robcad\tools\;C:\Program Files\proeWildfire 4.0\bin;C:\Program Files\proeWildfire 4.0\mech\bin;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\MIT\Kerberos\bin;C:\Program Files\OpenAFS\Common;C:\Program Files\OpenAFS\Client\Program2008-08-28 14:20:30: OEM Code Page = 850
2008-08-28 14:20:30: locale =  C
2008-08-28 14:20:30: running on 2000+ - using RegisterServiceCtrlHandlerEx
2008-08-28 14:20:31: C:\Program Files\OpenAFS\Client\Program\afsd_service.exe version 1.5.3600
2008-08-28 14:20:31: Signature Verification disabled
2008-08-28 14:20:31: Num of Process Modules: 35
2008-08-28 14:20:31: C:\Program Files\OpenAFS\Client\Program\libosi.dll version 1.5.3600
2008-08-28 14:20:31: C:\Program Files\OpenAFS\Common\afsrpc.dll version 1.5.3600
2008-08-28 14:20:31: C:\Program Files\OpenAFS\Common\afspthread.dll version 1.5.3600
2008-08-28 14:20:31: C:\Program Files\OpenAFS\Common\afsauthent.dll version 1.5.3600
2008-08-28 14:20:31: C:\Program Files\OpenAFS\Client\Program\libafsconf.dll version 1.5.3600
2008-08-28 14:20:31: osi_InitDebug code 0
2008-08-28 14:20:31: gethostname LUL-F131-W001R
2008-08-28 14:20:31: Trace Options = 0
2008-08-28 14:20:31: Default trace buffer size 10000
2008-08-28 14:20:31: osi_LogCreate log addr 9e5c20
2008-08-28 14:20:31: Cache size 800000
2008-08-28 14:20:31: Chunk size 262144 (18)
2008-08-28 14:20:31: Block size 4096
2008-08-28 14:20:31: Defaulting to 4 background daemons
2008-08-28 14:20:31: Defaulting to 25 server threads
2008-08-28 14:20:31: Status cache entries: 20000
2008-08-28 14:20:31: Default volume cache entries: 3333
2008-08-28 14:20:31: Default cell cache entries: 1024
2008-08-28 14:20:31: Logoff token transfer on
2008-08-28 14:20:31: Logoff token transfer timeout 120 seconds
2008-08-28 14:20:31: Default root volume name root.afs
2008-08-28 14:20:31: Mount root /afs
2008-08-28 14:20:31: Default cache path C:\WINDOWS\TEMP\AFSCache
2008-08-28 14:20:31: Cache type is FILE
2008-08-28 14:20:31: Cache Validation on Startup
2008-08-28 14:20:31: Set to trap on panic
2008-08-28 14:20:31: Sys name x86_win32 i386_w2k i386_nt40
2008-08-28 14:20:31: SecurityLevel is crypt
2008-08-28 14:20:31: CM ForceAnonVLDB is off
2008-08-28 14:20:31: DNS will be used to find AFS cell servers
2008-08-28 14:20:31: Freelance client feature is activated
2008-08-28 14:20:31: Dot files/dirs will be marked hidden
2008-08-28 14:20:31: Maximum number of multiplexed sessions is 50
2008-08-28 14:20:31: Maximum number of VCs per server is 100
2008-08-28 14:20:31: SMB authentication type is EXTENDED
2008-08-28 14:20:31: RX extraPackets is 120
2008-08-28 14:20:31: RX Peer Statistics gathering is enabled
2008-08-28 14:20:31: RX Process Statistics gathering is enabled
2008-08-28 14:20:31: RX Hot Thread is enabled
2008-08-28 14:20:31: CM CallBackPort is 7001
2008-08-28 14:20:31: EnableServerLocks: server requested
2008-08-28 14:20:31: CM DeleteReadOnly is 0
2008-08-28 14:20:31: CM BPlusTrees is 1
2008-08-28 14:20:31: No PrefetchExecutableExtensions
2008-08-28 14:20:31: CM OfflineReadOnlyIsValid is 0
2008-08-28 14:20:31: CM GiveUpAllCallBacks is 0
2008-08-28 14:20:31: CM FollowBackupPath is 0
2008-08-28 14:20:32: First Network address 82f04983 SubnetMask ffffff00
2008-08-28 14:20:32: HardDeadTimeout is 0
2008-08-28 14:20:32: IdleDeadTimeout is 30
2008-08-28 14:20:32: lanmanworkstation : SessTimeout 45
2008-08-28 14:20:32: ConnDeadTimeout is 22
2008-08-28 14:20:32: HardDeadTimeout is 45
2008-08-28 14:20:39: Cache File "C:\WINDOWS\TEMP\AFSCache" already exists
2008-08-28 14:20:40: Existing File Size: 00000000:346598CC
2008-08-28 14:20:40: Granularity - 10000
2008-08-28 14:20:40: Configuration changed or Not a persistent cache file
2008-08-28 14:20:40: Error mapping view of file: 8
2008-08-28 14:20:40: cm_InitMappedMemory code 66543208
2008-08-28 14:20:40: afsd_InitCM failed: error initializing cache file (code = -1)
2008-08-28 14:20:40: --- begin dump ---
a - Dir Lookup   Hits: 0      
a -            Misses: 0      
a -             Enums: 0      
a -            Create: 0      
a -            Remove: 0      
a - Dir Times  Lookup: 0              
a -            Create: 0              
a -            Remove: 0              
a - B+ Lookup    Hits: 0      
a -      Inexact Hits: 0      
a -    Ambiguous Hits: 0      
a -            Misses: 0      
a -            Create: 0      
a -            Remove: 0      
a -        Build Tree: 0      
a -         Free Tree: 0      
a -          DV Error: 0      
a - B+ Time    Lookup: 0              
a -            Create: 0              
a -            Remove: 0              
a -             Build: 0              
a -              Free: 0              
a - dumping cells - cm_data.currentCells=0, cm_data.maxCells=0
a - Done dumping cells.
a - dumping volumes - cm_data.currentVolumes=0, cm_data.maxVolumes=0
a - Done dumping volumes.
a - dumping all scache - cm_data.currentSCaches=0, cm_data.maxSCaches=0
a - Done dumping all scache.
a - dumping cm_data.scacheHashTable - cm_data.scacheHashTableSize=0
a - Done dumping cm_data.scacheHashTable
begin dumping smb_vc_t
done dumping smb_vc_t
begin dumping DEAD smb_vc_t
done dumping DEAD smb_vc_t
2008-08-28 14:20:40: --- end   dump ---

Re: Windows AFS client refuses to start.

by Jeffrey Altman-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

2008-08-28 14:20:40: Error mapping view of file: 8
2008-08-28 14:20:40: cm_InitMappedMemory code 66543208

ERROR_NOT_ENOUGH_MEMORY                                       winerror.h
# Not enough storage is available to process this command.

The size of the cache file is larger than the contiguous blocks of
memory in the afsd_service process.

Make your cache smaller.




smime.p7s (4K) Download Attachment

Re: Windows AFS client refuses to start.

by Anders Magnusson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Jeffrey Altman wrote:

> 2008-08-28 14:20:40: Error mapping view of file: 8
> 2008-08-28 14:20:40: cm_InitMappedMemory code 66543208
>
> ERROR_NOT_ENOUGH_MEMORY                                       winerror.h
> # Not enough storage is available to process this command.
>
> The size of the cache file is larger than the contiguous blocks of
> memory in the afsd_service process.
>
> Make your cache smaller.
>  
Hm, the cache size is set to 800MB which works in all other computer labs.

What may be causing this, can it happen anytime?  And how little memory
may it be
available?  Also, wouldn't it be better if afsd just complained in the
log and resized the
cache file to something smaller that worked?

-- Ragge
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@...
https://lists.openafs.org/mailman/listinfo/openafs-info

Re: Windows AFS client refuses to start.

by Jeffrey Altman-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Anders Magnusson wrote:
> What may be causing this, can it happen anytime?  

Fragmentation of the process memory space is dependent upon what
is installed on the machine that is hooking itself into the
afsd_service.exe process memory space.

It won't randomly happen.

> And how little memory
> may it be
> available?  

Totally dependent upon where DLLs are instructed by the developers
to load themselves into memory.

> Also, wouldn't it be better if afsd just complained in the
> log and resized the > cache file to something smaller that worked?

I don't think so.  I think that if you have applications injecting
themselves into your processes' memory space that you should figure
out what they are.  they could be something unwanted.

If I resize the cache I must flush it.  That could be just as painful
as not being able to load it depending on your network availability.

Jeffrey Altman

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@...
https://lists.openafs.org/mailman/listinfo/openafs-info
LightInTheBox - Buy quality products at wholesale price!