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.

Nagios migration to new Linux server – How we do it

by | Feb 15, 2021

Nagios migration to a new Linux server involves transferring all the existing data, defined hosts, services, email alert scripts, and Pnp4nagios data.

After the migration, we need to update/add the clients with the IP of the new server, so that both Nagios get alerts.

Finally, once we are comfortable with a new migration, we can decommission the old one.

Here at Bobcares, we often get requests from our customers to migrate Nagios to a new Linux server as part of our Server Management Services.

Today, let’s see how our Support Engineers migrate the Nagios tool to another server.

 

Nagios migration to new Linux server

Usually, many customers approach us to migrate the Nagios from one Linux server to another Linux server.

Now let’s see how our Support Engineers help the customers to migrate Nagios to a new Linux server.

1. First, we install fresh CentOS Linux on a new server and configure the required services.

2. After that, we proceed with the installation of Nagios Core and its dependencies.

We also ensure that Nagios Core is running.

3. Thereafter, we proceed with transferring configuration files of Nagios. It mainly includes Nagios configuration files and Nagios Apache configuration files.

 

Nagios configuration files in Linux server

Main configuration files: $NAGIOS_HOME/etc/*.cfg
Host and services configuration files: $NAGIOS_HOME/etc/objects/*.cfg
Alert scripts: (if any customized email alerts b – for alert scripts used check-in commands.cfg and search for notification commands)

Here is the command that we run to transfer Nagios configuration files to the new server.

[[email protected] ~]# scp /usr/local/nagios/etc/*.cfg testserver:/usr/local/nagios/etc/

[[email protected] ~]# scp /usr/local/nagios/etc/objects/*.cfg testserver:/usr/local/nagios/etc/objects/

 

Nagios Apache configuration in Linux server

HTTP configuration file: /etc/httpd/conf.d/nagios.conf

Here is the command that we run to transfer Nagios Apache configuration files to the new server.

[[email protected] ~]# scp /etc/httpd/conf.d/nagios.conf testserver:/etc/httpd/conf.d/

4. Then we check whether the Nagios configuration is proper or not, by running the below command.

[[email protected] ~]# /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

If the prompt then ends with the following, then it indicates that the migration is proper.

Total Warnings: 0
Total Errors: 0

5. If there is any Pnp4nagios data migration, we will assist you. PNP4Nagios is one such external program in which Nagios pass the performance data to an external program that can store that data for later analysis as Nagios Core does not have its own performance data engine built in to process this performance data.

6. Then we change the IP address configuration of both servers.

For the newly installed and configured Nagios Linux server, we give the address of the old Nagios server and vice versa!

7. Finally, we reboot both machines and ensure the new Nagios server is working well.

[Need any assistance with Nagios migration? – We’ll help you]

 

Conclusion

Today, we saw how our Support Engineers helped our customers in migrating the Nagios server to a new Linux server.

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 *

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

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

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

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