Max concurrent service checks (<n>) has been reached. Nudging <service_name> by n seconds ...

Owned by Sebastian Koch
Last updated: Jul 15, 2014
1 min read

Problem

The error message below

Max concurrent service checks (50) has been reached. Nudging <service_name> by n seconds ...

appears one or multiple times in User Web Interface > Reports > Event Log and the system seems to work oddly. 

Solution

Raise the number of maximum concurrent checks or ideally set it to unlimited as the Monitor process will care individually how to schedule and spread checks properly. 

  1. Open the Administration Web Interface > Configuration > Load Configuration
  2. Set Maximum Concurrent Service Checks to 0

See the detail article Load Configuration for more information about the settings.e

The following macros are not currently supported in the footer:
  • style