THIS KNOWLEDGE BASE HAS BEEN ARCHIVED AND IS NO LONGER BEING UPDATED
Please visit library.nagios.com/docs for the latest and most up-to-date documentation.
Home » Categories » Products » Nagios XI » Troubleshooting » Common Problems

Nagios XI - Running Out Of Disk Space On The Nagios XI VM

Overview

Running out of HDD space on the Nagios XI server could create a large number of problems - disrupted monitoring, data loss, database corruption, inability to log in the web interface, tons of notifications, etc. If you receive warning or critical alerts about "Root Partition" on localhost, you need to act fast and fix the low HDD space issue. Don't wait until your hard drive is 100% full!

 

Possible Causes

  • Increasing the number of hosts/services has consumed more disk space
  • Large number of backups
  • Large log files

 

Possible Solutions

Always plan ahead and set up your environment in a way that you allow for some growth. You can review the general hardware requirements needed to run Nagios XI here.

It is always a good idea to backup your Nagios XI instance but if you are saving them locally and don't have large enough hard drive, you can run out of space very fast.

By default, the backups are stored in /store/backups/nagiosxi/ directory. It is a good practice to keep an eye on this folder and remove the old backups that you don't need.

Also, there are some mysql and postgres backups in /store/backups/mysql/ and /store/backups/postgresql/ directories. These are created on daily, monthly, and weekly basis by the /root/scripts/automysqlbackup and /root/scripts/autopostgresqlbackup script. Both scripts are run on a cron job. Run the following command to view the crontab:

cat /etc/cron.d/nagiosxi

 

Keep in mind that the /store/backups/mysql/ and /store/backups/postgresql/ directories can also grow quite large. If you need to clear some HHD space you could delete some of the old backups that are no longer needed.

You can disable these two cron jobs if you wish by commenting them out (see below):

# 0 7 * * * root   /root/scripts/automysqlbackup
# 0 8 * * * root   /root/scripts/autopostgresqlbackup

 

Sometimes, your log files can grow out of control, especially if you have a poorly configured checks, system issues, debugging enabled, etc. You can temporarily clear some space by deleting old logs that you might not need.

Tip: In order to view the 10 largest files under /var/log/ directory you can run:

du -a /var/log | sort -n -r | head -n 10

 

Another option is to add another disk and move the existing data to that location. The following KB article walks you through moving /var/log to another disk:

Documentation - Moving /var/log

 

If you don't care about historical data, you can also delete some old nagios log files from the /usr/local/nagios/var/archives/ directory. These files are used for some of the reporting (mainly the legacy reports and the availability report).

 

After clearing some space, you will need to resize the virtual machine by following the steps, outlined in our Nagios XI - Resizing the VM Disk Size document.


 

Final Thoughts

For any support related questions please visit the Nagios Support Forums at:

http://support.nagios.com/forum/



Special Offer For Knowledgebase Visitors! Get a huge discount on Nagios Log Server by clicking below.

Get 60% Off Nagios Log Server!

Did you know? Nagios provides complete monitoring of: Windows, Linux, UNIX, Servers, Websites, SNMP, DHCP, DNS, Email, Storage, Files, Apache, IIS, EC2, and more!

1 (16)
Article Rating (16 Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Backups are not being generated due to tar creation errors
Viewed 5828 times since Thu, Feb 27, 2020
Enabling Oracle Linux Optional Repository
Viewed 21927 times since Mon, May 14, 2018
Nagios XI - Resolving "Cannot connect to database" Error - Core Config Manager
Viewed 10715 times since Mon, Jan 25, 2016
Nagios XI - Core 4 Load Spikes on 1.75 and 7 Hour Intervals
Viewed 6541 times since Mon, Jan 25, 2016
Nagios XI - ERROR: unable to open include file: conf.d/*.cfg
Viewed 11366 times since Sun, May 29, 2016
Nagios XI - HTTP 500 Error / PHP Parse error - Unexpected $end
Viewed 10166 times since Mon, Jan 25, 2016
Nagios XI - Common Upgrade Failures And Solutions
Viewed 17228 times since Thu, Jun 29, 2017
NDOUtils - Message Queue Exceeded
Viewed 19251 times since Thu, Jan 21, 2016
CCM says unapplied changes exist, but none listed
Viewed 8122 times since Mon, Feb 27, 2017
Nagios XI - Apply Configuration Fails - Backend login to the Core Configuration failed
Viewed 28800 times since Tue, Aug 2, 2016