• Home
  • Disclaimer
  • Contact
  • Archives
  • About
  • Subscribe
  • Support
  • Advertise

Kernel Talks

Unix, Linux, & Cloud!

  • How-to guides
    • Howto
    • Disk management
    • Configurations
  • OS
    • HPUX
    • Linux
  • Commands & tools
    • Commands
    • Software & Tools
    • System services
  • Cloud computing
    • AWS CSA preparation guide!
    • Cloud Services
  • Tips & Tricks
  • Linux commands
You are here: Home / Software & Tools

How to restore nagios configuration from backup

Published: March 16, 2016 | Modified: June 20, 2020 | 656 views



Learn to restore Nagios configuration backup. If you messed up Nagios configuration, you can restore last known good config using these steps.

Restore Nagios configuration

Requirement

While troubleshooting or doing some configuration changes (R n D), sometimes you mess up the configuration in Nagios. This leads to no data dashboard. You need to revert back to the last known good configuration so that the tool can resume its work.

Also read: How to install & configure checkmk in Linux

Solution

Normally you should have daily (or frequency of your choice i.e. weekly, hourly, etc.) backups scheduled for tool configuration using services like cron. We will see how to configure this configuration backup in another article.

Now, navigate to the directory where configuration backups are kept. Normally they should be in gunzip format.

Once inside that directory run below restore command.

# check_mk --restore check_mk.11-Mar-2016.tar.gz

After restore to make sure, ownership is well in place, run below command

# chown -R apache:nagcmd /etc/check_mk/conf.d/wato/

Lastly, restart Nagios to take up restored configuration.

# check_mk -R --restart nagios-check_mk

Now go back to the dashboard and check its populated with values!

⇠ Previous article
How to remove password expiry in HPUX HP Unix
Next article ⇢
Processes using high memory, cpu using unix95

Related stuff:

  • What is the difference between su and sudo?
  • Package removal in Linux (YUM & APT)
  • How to install and uninstall Sophos Antivirus in Linux
  • Googler : Search google right from your Linux terminal
  • How to add Oracle Linux public repository in SUSE Manger
  • Assorted list of resources to ease your AWS tasks
  • The complete guide: logrotate utility on Linux
  • How to start, stop & restart MariaDB server in Linux
  • How to configure Cockpit in RHEL 8
  • Our list of SUSE Manager articles
  • Install LAMP in RHEL
  • Troubleshooting check_mk agent in Linux

Filed Under: Software & Tools Tagged With: check_mk Syntax, How to restore last known good nagios wato, Nagios configuration scrambled, Restore nagios, restore nagios configuration, wato

If you like my tutorials and if they helped you in any way, then

  • Consider buying me a cup of coffee via paypal!
  • Subscribe to our newsletter here!
  • Like KernelTalks Facebook page.
  • Follow us on Twitter.
  • Add our RSS feed to your feed reader.

Share Your Comments & Feedback: Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Get fresh content from KernelTalks

  • Email
  • Facebook
  • RSS
  • Twitter

Popular posts

  • How to start, stop & restart MariaDB server in Linux
  • 4 ways to check the size of physical memory (RAM) in Linux
  • How to list YUM repositories in RHEL / CentOS
  • How to reset iptables to the default settings
  • How to rescan disk in Linux after extending VMware disk
  • How to configure login banners in Linux (RedHat, Ubuntu, CentOS, Fedora)
  • What are the huge pages in Linux?
  • How to upgrade package using YUM in RHEL
  • How to remount filesystem in the read-write mode under Linux
  • mount.nfs: requested NFS version or transport protocol is not supported

Get Linux & Unix stuff right into your mailbox. Subscribe now!

* indicates required

This work is licensed under a CC-BY-NC license · Privacy Policy
© Copyright 2016-2020 KernelTalks · All Rights Reserved.
The content is copyrighted to Shrikant Lavhate & can not be reproduced either online or offline without prior permission.