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/

0 (0)
Article Rating (No 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
Nagios XI - Issues with mod_gearman and Performance Data Newlines: "\n"
Viewed 1581 times since Tue, Feb 2, 2016
Enabling Oracle Linux Optional Repository
Viewed 6408 times since Mon, May 14, 2018
Nagios XI - WMI Troubleshooting
Viewed 10198 times since Mon, Apr 24, 2017
Nagios XI - Missing localhost Alerts
Viewed 3121 times since Sun, Nov 5, 2017
Nagios XI - SNMP MIB Upload Problems
Viewed 3737 times since Mon, Apr 10, 2017
Pages Not Displaying Correctly
Viewed 2567 times since Mon, Jan 25, 2016
Nagios XI - ERROR: unable to open include file: /etc/mrtg/conf.d/xxxxxxx.cfg
Viewed 3396 times since Wed, Jun 1, 2016
Nagios XI - Problems with $ Signs in the Check Command
Viewed 3158 times since Tue, Jan 26, 2016
Nagios XI - Windows Memory Usage - Physical
Viewed 7507 times since Tue, Jan 26, 2016
Nagios XI - Apply Configuration Fails - Backend login to the Core Configuration failed
Viewed 8887 times since Tue, Aug 2, 2016