Reboot Alerts If onQ identifies a problem, determines that a reboot will fix the problem, onQ initiates that reboot and restarts protection. If onQ has enough time prior to the reboot to log the cause for the reboot, it will do so, providing a detail explanation in the alert. Otherwise, a generic message appears in the alert. Example reboot alerts are listed in the following table: Severity & Subject Message Cause What do I do? NOTIFY – Rebooting onQ Process holding the repo lock (3044) cannot be found. The contents of the lock file is: Repo marked dirty on Mon Sep 06 21:24:28 -0700 2010 by 3044 (../src/squirt-add ["--repo", "repo", "--log-level", "INFO", "--ref-file", "/opt/BCVdata/BCVServer/current/addlist.%ALL"]).... sent once – immediately Nothing. onQ rebooted the onQ VM and restarted protection. However, If onQ Protection does not start correctly, please contact Quorum Support for assistance. NOTIFY – Rebooting onQ Protection is enabled but the manager process cannot be found.... sent once – immediately
