DEBUG_SHUTDOWN

🛠️
Parameter: DEBUG_SHUTDOWN
Short description: Logs the entire server shutdown sequence (task order, blockers, timeouts) – helpful when quit / exit hangs on the console.

Profile

Parameter
DEBUG_SHUTDOWN
Category
Logging / Debug
Component
Server
Available since
10.0
Supported versions
10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1
GUI equivalent
notes.ini only (no GUI)
Possible values
0 = off (default), 1 = basic, 2 = verbose (per task, incl. NSD triggers)

Description

During shutdown, the Domino server terminates all tasks in a defined order: stop accepting new sessions, complete running operations, flush caches, signal tasks, optionally force-kill after timeout. DEBUG_SHUTDOWN writes a console/log line for each step with timestamp, status, and any triggered NSD triggers if individual tasks do not terminate in time.
Ideal for topics such as server does not respond to quit, an individual task blocks the shutdown, restart takes unusually long, NSD is triggered during shutdown, cluster failover behavior.

Example configuration

DEBUG_SHUTDOWN=2 Debug_Outfile=/local/notesdata/IBM_TECHNICAL_SUPPORT/shutdown.log DEBUG_OUTFILE_UNIQUE=1

Notes & pitfalls

  • Takes effect only on the next shutdown.
  • Entries appear in console.log and in Debug_Outfile.
  • Complementary to DEBUG_SERVER_STARTUP, DEBUG_THREADID, Server_Shutdown_Timeout, and NSD configuration.
  • For recurring shutdown hangs, set DEBUG_OUTFILE_UNIQUE=1 so that logs are not overwritten.
  • On cluster servers, enable in parallel on all members.