Bobcares

Nagios scheduled downtime – How we do it!

by | Jan 25, 2020

Scheduled downtime in Nagios is done for a host or a service.

The Scheduling downtime is done from the web interface and or running scripts in the Nagios.

Here at Bobcares, we often receive requests regarding Nagios as a part of our Server Management Services.

Today, let’s see how our Support Engineers schedule downtime for host and service in Nagios.

 

Schedule downtime in Nagios for a host

Recently one of our customers contacted us to set up a scheduled downtime for a server in Nagios. Let’s discuss how we help our customers on the same.

First, we log in to the Nagios web interface.

Then we click on services in the left pane.

From the list, we click on the hostname.

Then from the Hosts commands we click on “Schedule downtime for this host”

The Host and the Author will be automatically filled. In the comment box, we enter the reason for the scheduled task.

Now we enter the Start Time and End Time of the scheduled process. The start and end time need to be specified in mm/dd/yyyy hh:mm:ss format.

Then we select the Type. There are 2 types Fixed and Flexible.

The Fixed time will start and stop at the time we specify in the schedule.

We use the Flexible type when we are not sure about the downtime. Thus, we specify the time in If Flexible, Duration:. Flexible downtime starts when the host goes down or becomes unreachable between the start and end times.

Then we mention the Child Host and Nagios needs to do with the Child process.

Nagios scheduled downtime

Once we verify the details, we click on commit to save the schedule.

 

Schedule downtime in Nagios for a service

First login to Nagios web interface and we click on services in the left pane.

From the list, we find the host server and click on the service to schedule it.

Then from the Hosts commands we click on “Schedule downtime for this host”

In the comment box, we enter the reason for the scheduled task.

Then we enter the Start Time and End Time of the scheduled process in the format mm/dd/yyyy hh:mm:ss.

We select the schedule type as Fixed or Flexible as per the requirement.

Then we mention the Child Host and Nagios needs to do with the Child process.

We verify the details, we click on commit to save the schedule.

 

A common error in scheduling downtime

Recently one of our customers contacted telling us that the scheduled time is not working for his Nagios host. Thus, on checking we found that the entry was missing in the Scheduled Downtime.

Now let’s discuss how our Support Engineers resolve the error for our customers.

 

Missing entry in scheduled downtime

Thus, our Support Engineers login to the server. On checking the error log we found that the below error.

[error] [client xxx.xx.xxx.xx] Couldn't resolve host 'localhost', referer: http://xx.xx.xx.xx/nagiosxi/includes/components/xicore/downtime.php

On checking the hosts file the localhost entry was missing.

Thus, we edit the hosts file and add the localhost entry.

Finally, we restart the Apache service.

service apache2 restart

 

[Ned any further assistance with Nagios? – We’ll help you]

 

Conclusion

In short, we’ve discussed how our Support Engineers schedule downtime for a host and a service. Also, we’ve discussed the common error that can occur during scheduling downtime.

PREVENT YOUR SERVER FROM CRASHING!

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.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

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

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

Privacy Preference Center

Necessary

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]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

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
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

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

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

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.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF