Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Restarting Linux Services With NCPA in Nagios – Let us discuss

by | May 8, 2021

Restarting Linux Services With NCPA? We can help you.

An advanced, cross-platform agent, we can install NCPA on Windows / Linux / AIX / Mac OS X machines.

As part of our Server Management Services, we assist our customers with several Linux queries.

Today, let us see how to automatically restart problematic services on Linux servers using the Nagios Cross-Platform Agent (NCPA).


Restarting Linux Services With NCPA

In order to begin, our Support Techs suggest having an NCPA configured on the Linux machine we would like to restart services on.

Create Restart Script

First, we create a script in the /usr/local/ncpa/plugins directory that will perform the service restart command:

# vi /usr/local/ncpa/plugins/

Then we paste the following code into the terminal session:

sudo service $1 restart
exit 0

Once done, we save the changes and close the file.

Grant NCPA Permission to Restart Services

The Nagios user needs permission to execute the service command.

We execute the following commands as root to give NCPA permission to restart services:

# echo “nagios ALL = NOPASSWD: `which service`” >> /etc/sudoers
# echo ‘Defaults:nagios !requiretty’ >> /etc/sudoers

Test the Commands from Nagios XI Server

Now we will test if the script we just created on the Linux server is working.

The example below will restart the crond service as it is unlikely to cause any issues:

# cd /usr/local/nagios/libexec
# ./ -H -P 5693 -t Str0ngT0k3n -M ‘plugins/’ -a crond

[root@xi-c7x-x64 libexec]# ./ -H -P 5693 -t Str0ngT0k3n -M ‘plugins/’ -a crond
Stopping crond: [ OK ]
Starting crond: [ OK ] | ‘status’=0;1;2;

Since we received back the results from the command, it appears to work.

Create Event Handler Script

Next, we create a script Nagios XI to use for the event handler. It will be called and locate in the /usr/local/nagios/libexec/ directory on the Nagios XI server:

# vi /usr/local/nagios/libexec/

Then we paste the following:

case “$1” in
/usr/local/nagios/libexec/ -H “$2” -P 5693 -t “$3” -M ‘plugins/’ -a “$4”
exit 0

Eventually, we save the changes and close the file.

Now to set the correct permissions we execute the following commands:

# chown apache:nagios /usr/local/nagios/libexec/
# chmod 775 /usr/local/nagios/libexec/

Then we test the script:

# /usr/local/nagios/libexec/ CRITICAL Str0ngT0k3n crond

Once the script runs, it receives three arguments referenced as $1, $2, $3, $4 in the script.

$1 = The state of the service.
$2 = The host address of the Linux server.
$3 = The NCPA Token on the Linux server.
$4 = The name of the service being restarted.

Make note that only when the service is in a CRITICAL state will we execute the command.

Create Event Handler

Moving ahead, we create an event handler on the Nagios XI server to be used by our services.

For that, we navigate to Configure > Core Config Manager.

Select Commands from the list on the left, click the >_ Commands link and then, Add New.

Then we populate the fields with the values on the following page:


Service Restart – Linux



Command type

misc command

Ensure to check the Active check box.

Eventually, Save and Apply Configuration.

Add a Service Check

Now we need to create a Service using the NCPA Monitoring Wizard. To do so, we select the crond service from the list of Services.

Then we finish the wizard to create the new service.

Update Service With Event Handler

Here, we need to do two things:

  • Select Event Handler
  • Add the name of the service we want to restart as a custom variable to the service object.

For that, our Support Techs suggests:

  1. Navigate to Configure > Core Config Manager > Monitoring > Services.
  2. Click the Service status for: crond to edit the service.
  3. Then click the Check Settings tab.
  4. From the Event handler drop-down list, select the option Service Restart – Linux.
  5. For Event handler enabled click On.
  6. Click the Misc Settings tab and then click the Manage Free Variables button.
  7. We will add a custom variable so that the event handler knows the name of the service to restart.
    Name: _SERVICE
    Value: crond
  8. If we click Insert the variable will add to the list on the right.
  9. Then click Close >> Save.
  10. Finally, Apply Configuration for the changes to take affect.


To test, we force the service to stop on the Linux machine:

# service crond stop

We wait for the Nagios service to go to a critical state or force the next check.

Once the Nagios XI Cron Scheduling Daemon service is in a critical state the event handler will execute and the Linux crond service will restart.

Next time Nagios XI checks the Cron Scheduling Daemon service it will return to an OK state.


However, if the event handler does not work properly, check the /usr/local/nagios/var/nagios.log file for any errors.

For example,

[1481763272] SERVICE ALERT:;Cron Scheduling Daemon;CRITICAL;SOFT;1;crond is stopped
[1481763272] wproc: SERVICE EVENTHANDLER job 7 from worker Core Worker 12627 is a non-check
helper but exited with return code 13
[1481763272] wproc: early_timeout=0; exited_ok=1; wait_status=3328; error_code=0;
[1481763272] wproc: stderr line 01: execvp(/usr/local/nagios/libexec/, …)
failed. Errno is 13: Permission denied

Here, we can see that the worker did not have permission to execute the command.

[Need help with the procedures? We are here for you]



In short, today we saw how our Support Techs go about Restarting Linux Services With NCPA.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.