Server abends when an older ds.nlm is applied to a server with a newer permanent configuration parameter - ndsinit.

  • 3083559
  • 03-Apr-2008
  • 26-Apr-2012


Novell eDirectory for All Platforms
Novell NetWare 6.5 Support Pack 6


Server was running NetWare 6.5 Support Pack 6, eDirectory 8.7.3 SP9 with an eDirectory 8.7.3 SP9 FTF patch. Then a permanent configuration parameter was added to the server via iMonitor. This was a new parameter that was only understood by the new version of ds.nlm contained in the FTF such as Advanced Referral Costing or the Failed Authentication Delay option.
(For an example please see KB 3479868.)
Then the server was patched with NetWare 65 SP7. This backrev's the dsloader.nlm and ds.nlm to eDirectory version 8.7.3 SP9 (pre-FTF). After the first reset during the Support Pack 7 installation the server abended when the ds agent loaded. In the abend log it can be seen that the process that abends the server is the NDSInit process in the function GetConfigParm. Below is the stack from the abend log.
Running process: NDSInit Process
Thread Owned by NLM: DS.NLM
Stack pointer: 88EBAC30
OS Stack limit: 88EB7000
Scheduling priority: 67371008
Wait state: 5050030 Blocked on Semaphore
Stack: 8D15B812 (DS.NLM|GetConfigParm+D4)
--0000002D (LOADER.NLM|KernelAddressSpace+2D)
--00000008 (LOADER.NLM|KernelAddressSpace+8)
--88EB8EAC ?
--0000002D (LOADER.NLM|KernelAddressSpace+2D)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000008 (LOADER.NLM|KernelAddressSpace+8)


During the GetConfigParm function eDirectory will scan thru the current permanent configuration parameters set for that server on both the pseudoserver object and ncp server object. If it encounters a parameter that it does not recognize the server will abend.
1. Bring the server up without allowing the eDirectory agent to load. " server -ndb "
2. Copy back over to the server the newer ds.nlm and dsloader.nlm.
3. Reset the server.
4. Reapply the eDirectory 8.7.3 SP9 FTF.
5. Reset the server once again.

Additional Information

This has been resolved in eDirectory 8.7.3 SP10. The server will no longer abend if eDirectory encounters an unknown permanent configuration parameter.