Server health and performance
Crashes and NSD, memory pools, transaction logging, server tasks, start-up and shutdown.
Use the arrow keys and Enter, or click a result to open it.
Insufficient memory - NSF pool is fullOne of Domino's internal memory pools has run out of space.Recovery Manager: Log File is FullDomino's transaction log has no room left, so the server can't log changes safely.Process [path] ([pid]) has terminated abnormallyA Domino program crashed. Domino normally runs NSD to capture diagnostics and, if Fault Recovery is enabled, restarts the server.Shared Memory from a previous Notes/Domino run has been detected, this process will exit nowDomino found shared memory left over from an earlier run and refuses to start until it has been cleaned up.Server Error: Insufficient MemoryThe server you were using ran out of memory while doing something memory-hungry for you, such as resolving a link across several replicas.Insufficient memory - NSF directory manager pool is fullOne of Domino's internal memory pools, used to track open databases, has run out.Maximum number of memory segments that Notes can support has been exceededThe server has used up all the shared memory segments Domino can manage.The buffer pool is too full to bring in another pageDomino's NSF buffer pool (the cache for database pages) has no room left for the page it needs.Recovery Manager: Assigning new DBIID for [database] (need new backup for media recovery).With transaction logging on, Domino gave the database a new database instance ID (DBIID). Older backups and logs can no longer be used to…Recovery Manager: Log scan in progress, try again laterThe transaction log is busy being scanned, so a backup or restore request has to wait.Configuration Error: Server record not foundAt startup, Domino could not find a Server document matching the name in the server's ID file, so it won't start.Error updating view [view] in [database]: [error]The Update or Updall indexer could not bring a view index up to date.Waiting for all tasks to completeDomino is shutting down and waiting for server tasks to finish before it can stop.AllocHandle: OUT OF PRIVATE HANDLES!A Domino process has used up its allowance of private memory handles, usually because something keeps allocating memory without freeing it.PANIC: LookupHandle: null handleDomino code tried to use a memory handle that was empty or already freed, so the process stopped itself to protect data and the server…Fatal Error signal = 0x[code] PID/TID = [pid]/[tid]A Domino process received a fatal operating system signal and crashed. Domino then runs NSD to capture diagnostics and terminates the…LkMgr BEGIN Long Held Lock DumpThe lock manager noticed a database lock held for an unusually long time and dumped details of it. HCL describes it as informational, but…Begin scan of databases to be consistency checkedDuring start-up Domino is looking for databases that were not closed cleanly last time, so it can run fixup on them before users open them.Recovery Manager: Restart Recovery complete. ([number]/[number] databases needed full/partial recovery)At start-up Domino checked the transaction log and replayed or rolled back any unfinished changes so that logged databases are consistent.Recovery Manager: Media Recovery complete for [database], last update applied [date] [time]A restored database has had the archived transaction log records replayed up to the time shown, bringing it forward from the backup.Server error: Access to this server has been restricted by the administratorThe server has been put into restricted mode, so it refuses new database opens from ordinary users and servers. Administrators can still…Error attempting to load or run [program]: Unable to locate programDomino was asked to start a task or program but could not find its executable in the Domino program directory.Server exiting: Server is already running (in another process)Domino found another copy of the same server, or what looks like one, already running on this machine, so the new start-up stopped.Error writing to process file pid.nbf, Server exiting: Cannot write or create file (file or disk is read-only)At start-up Domino could not write pid.nbf, the file it uses to track its own processes, so it stopped.Server exiting: Could not open the ID fileDomino could not open the server ID named in its notes.ini, so it cannot identify itself and stops.Server exiting: The ID file is write protectedDomino can read the server ID but is not allowed to write to it, and it needs write access so it can update the ID.PANIC: Error encountered reading transaction log!The server could not read its transaction log during start-up or recovery, so it stopped rather than risk damaging databases.THREAD [thread] WAITING FOR [semaphore type] 0x[code] [semaphore name] (R=[n],W=[n],WRITER=[thread],1STREADER=[thread]) FOR [ms] msA server thread waited longer than the timeout (normally 30 seconds) for an internal lock held by another thread.
Need a hand with this?
Paste your exact message into What's That Error? for a plain-English explanation, or get in touch. I've been supporting Domino and Notes for 28 years.
The errors, causes and fixes on this site are carefully researched, drawing on HCL documentation and 28 years of hands-on Domino and Notes experience. Every environment is different, though, and a solution that works in one may not be right for yours. Exact wording can also vary between Domino and Notes versions.
This information is general guidance only and is provided without warranty of any kind. Always back up your data and test changes on a non-production system first. To the extent permitted by law, Bruinsma Services Pty Ltd accepts no responsibility or liability for any loss, damage, downtime or other consequence arising from use of this information. For advice specific to your environment, please contact me.