Domino & Notes error

PANIC: Error encountered reading transaction log!

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

  1. Check the transaction log path is mounted, healthy and has free space
  2. Back up the whole data directory and the log directory before changing anything
  3. If the logs cannot be recovered, move the log files and nlogctrl.lfh out of the log directory so Domino creates new ones at start-up (any changes still only in the log are lost)
  4. Take a new full backup afterwards, as database instance IDs change; contact HCL Support if unsure

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.

Disclaimer

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.