What it means
The server could not read its transaction log during start-up or recovery, so it stopped rather than risk damaging databases.
Common causes
- Damaged or missing log extent files, or a damaged log control file
- The disk holding the transaction log failed, filled up or was not mounted
- Log files deleted, moved or restored out of step with the databases
Quick fixes
- Check the transaction log path is mounted, healthy and has free space
- Back up the whole data directory and the log directory before changing anything
- If the logs cannot be recovered, move the log files and
nlogctrl.lfhout of the log directory so Domino creates new ones at start-up (any changes still only in the log are lost) - Take a new full backup afterwards, as database instance IDs change; contact HCL Support if unsure