Environment
Novell NetWare 6.5 Support Pack 5
Novell eDirectory 8.7.3.9 for NetWare 6.5
Situation
Over a span of hours or two days after being brought up the server
begins to not respond to LDAP requests, NCP connections, etc.
There is no high utilization. The problem can only be
recovered by a re-boot.
Under certain conditions the NetWare server's Work to Do queue is getting corrupted. Below are the steps required to see if this condition exists on a server.
1. Download the following tool: NWMON.NLM: https://www.novell.com/coolsolutions/tools/18341.html
2. Load the NLM on the server.
3. When the server begins to get into an unresponsive state observe the main menu of the NWCONFIG utility's main menu. There are two fields under the section entitiled Directory Thread Usage (max: xxx).
Currently In Use: xxx
Currently Queued: xxx
The max field shows how many threads are available to eDirectory. This will be half the server's Maximum Service Processes. As eDirectory begins to consume threads these threads will only increment the Currently in Use field. However, when the Directory Thread Usage count goes beyond the current max, the Currently Queued will begin to increment as well. If this server has a corrupt Work To Do queue the Currently in Use will be 0 and the Queued count will begin to increment until all threads have been consumed. After this point eDirectory will fail to respond.
Under certain conditions the NetWare server's Work to Do queue is getting corrupted. Below are the steps required to see if this condition exists on a server.
1. Download the following tool: NWMON.NLM: https://www.novell.com/coolsolutions/tools/18341.html
2. Load the NLM on the server.
3. When the server begins to get into an unresponsive state observe the main menu of the NWCONFIG utility's main menu. There are two fields under the section entitiled Directory Thread Usage (max: xxx).
Currently In Use: xxx
Currently Queued: xxx
The max field shows how many threads are available to eDirectory. This will be half the server's Maximum Service Processes. As eDirectory begins to consume threads these threads will only increment the Currently in Use field. However, when the Directory Thread Usage count goes beyond the current max, the Currently Queued will begin to increment as well. If this server has a corrupt Work To Do queue the Currently in Use will be 0 and the Queued count will begin to increment until all threads have been consumed. After this point eDirectory will fail to respond.
Resolution
This issue has been in resolved in Netware 6.5 support pack 6 and
later.