User Guide

Troubleshooting the NetWare Server 143
Server Operating System Administration Guide
103-000148-001
August 30, 2001
Novell Confidential
Manual 99a38 July 17, 2001
File Cache in the Server Memory Administration Guide. To solve the
problem, add more RAM.
7 Check for memory leaks.
Do the LRU Sitting Time and Long Term Cache Hits gradually decline
over time, even when network traffic has not increased and no new
applications have been installed on the server?
If yes, the server might have a memory leak. See “Resolving Server
Memory Leaks” on page 137.
If the problem still occurs, follow the troubleshooting steps in “Using a
Troubleshooting Methodology” on page 105, search the Novell
Knowledgebase (http://support.novell.com/search/kb_index.jsp), and contact
a Novell Support Provider.
Resolving Locked Device Errors
To resolve a locked device error, try one or more of the following:
 Wait for a while (sometimes a few hours); the task in process might
complete and free the device.
 Retry the action that resulted in the error.
 Delete all user connections and disable logins.
 For a disk device error, unload NLM programs (other than the device
driver) that might be using the disk. Dismount all volumes on the disk.
If you have tried all of the above without success, contact a Novell Support
Provider or the drive manufacturer.
Resolving Event Control Block Allocation Errors
Event control block allocation system messages can occur when you first start
the server or after the server has been running for some time.
These messages indicate that the server was unable to acquire sufficient
packet receive buffers, usually called event control blocks (ECBs). Running
out of ECBs is not a fatal condition. However, it can indicate either a LAN or
server problem.
Servers that run for several days where high loads occur in peaks might exceed
the set maximum number of ECBs, causing the system to generate ECB
system messages.