About self-healing

Self-healing is a pre-configured response and action to specific types of service failures. When a failure occurs, N-able N-central automatically restarts the service or executes a script configured by the administrator to try to resolve the issue. The system then verifies if the problem has been resolved and sends the appropriate notifications.

When creating a Self Healing action that runs a script that contains spaces, you need to enclose the script name in quotes.

You cannot use self-healing on services that are in service groups or services monitored by the N-able N-central server.

Self-healing at the device level is only available under the following conditions:

  • The device where the service has been added is in Professional mode.
  • The operating system of the device is Microsoft Windows.
  • The device where the service has been added is being monitored by a Windows agent or probe.

Self-Healing does not run for the first 15 minutes after a Windows device starts up to prevent a flood of self-healing tasks for services still in the process of starting. If you configured a self-healing task for a Windows Service, it will trigger during this window, but will not execute on the device as part of this fail-safe. As a result, the service remains in a failed state. Ensure that the number of attempts per hour is increased to ensure that it the task has another chance to run after that 15 minute window.

You can also modify the Execution Timeout to allow more attempts. This timeout is not the amount of time the agent waits for the self-healing action to run. It is a window in which it will try to self-heal before manual intervention would be required. Setting the Execution Timeout to one hour, and only allowing one attempt per hour means only one attempt will ever be made. In the situation where a service has failed to start after a reboot, it triggers during the first 15 minutes and not try again afterward, as it has hit its limit of attempts and is not allowed to try again in the next hour.

The second self-healing attempt and afterward, based on maximum per hour/day per Execution Timeout, waits for the same duration as the scan interval of the service. Ensure that the Execution Timeout and Scan Interval allows for additional attempts in conjunction with the number of attempts per hour/day.

The following services are not applicable to Windows devices and therefore cannot leverage the Self-Healing functionality of N-able N-central.

CPU (ADTRAN) Firewall - FortiGate NIC Status (VMware)
ADTRAN - Device Health Firewall - SonicWALL Paper Supply Level
ADTRAN - Memory Firewall - Watchguard Physical Drive (VMware)
Agent Status Firewall - ZyWALL Power Consumption (VMware)
Application Compliance Fortinet CPU Printer Page Count (HP)
Backup Manager Events Fortinet Disk Printer Conf Changes
Backup Manager Status Fortinet Memory Printer Cover Status
CA Replication Events Fortinet Sessions Printer Display
CCM CTI Registration Frame Relay Printer Page Count
CCM Call Mgr Status Juniper (ScreenOS) - Sessions Printer Status
CCM Conference Registration Juniper Secure Access - Concurrent Users Printer Toner Level
CCM Gateway Registration Lexmark - Hopper Status Power Supply (VMware)
CCM MGCP Gateway Lexmark - Paper Jam Status RAID Status (VMware)
CCM Phone Lexmark - Tray Status Security Logs
CCM Phone Registration License Compliance SonicWALL CPU
CCM VoiceMail Registration Logical Drive (VMware) SonicWALL Memory
Cisco Connections Maintenance Mode (VMware) Temperature Status (VMware)
CPU – Juniper (ScreenOS) Memory - Cisco Untangle – Firewall
CPU – Juniper Secure Access Memory – Juniper (ScreenOS) Untangle – IPS
CPU (VMware) Memory – Juniper Secure Access Untangle – Phish
CPU – Watchguard Memory – Juniper Secure Access Untangle – Protocol Filter
CPU (Cisco) Memory (VMware) Untangle – Router
Cisco Unity Express Mailbox NetBotz Airflow Untangle – Spam
Connections – Watchguard NetBotz Audio Untangle – Spyware
Datastore (VMware) NetBotz Dewpoint Untangle – Virus
Ethernet Errors NetBotz Door Switch Untangle – Web Filter
Fan Status (VMware) NetBotz Humidity Windows Event Log
Firewall - Cisco NetBotz Temperature  

What do you want to do?