We are using v5.5.0, I inherited the system...now, reverse-engineering the configuration. There are:
108 Hosts
1,247 Services
12 Contacts
149 Commands
0 Service Dependencies
22 Host Groups
3 Service Groups
2 Contact Groups
0 Host Dependencies
Current Performance Settings for the Nagios xi Database are:
* Maximum Commands Age: 480 minutes
* Maximum Events Age: 480 minutes
* Maximum SNMP Trap Age: 30 days
* Maximum Scheduled Reports History Age: 90 days
* Maximum Expired Auth Token Age: 24 hours
* Maximum Expired Session Age: 24 hours
* Maximum Audit Log Age: 45 days
* Optimize Interval: 60 minutes
The /store/backup directory is very large over 50 GB which is filling up /. The /var/lib/mysql dbase directory is also very large. Particularly, the "xi_eventqueue.ibd" (8.9G) and "xi_meta.ibd" (40.0 G).
All the checks (for the services) are running every 5 minutes and crashing the system as the kauditd cannot keep up with all the messages coming in. This is going to be the first of many help request posts. I am used to the old free version of Nagios. What attributes do I need to modify to scale back the about of checks being logged? And what are the best practices/recommendations for the backups?
FYI, I have modified the /root/scripts/automysqlbackup to send the backups to an NFS mountpoint. But we can't keep those backups for ever.
Nagios xi Backups Large
-
- Posts: 318
- Joined: Wed Aug 23, 2023 11:27 am
Re: Nagios xi Backups Large
Hi @jdbstr,
There should be a Backup Limit setting that you can configure to control how many backups are stored before the oldest ones are rotated out. I don't know what the default setting would have been on version 5.5.0 of Nagios xi, but configuring this should fix that issue going forward. This setting is located within Admin > System Backups > Scheduled Backups > Local.
The xi_eventqueue and xi_meta should be getting automatically rotated. if they aren't, you can run this locally to truncate those tables, as they are generally used to track historical data and only need to be retained as is useful to your operation of xi.
If you want to scale back the amount of checks being performed you could reduce the check intervals on some of your checks, but generally the volume you're reporting should be acceptable if log and backup rotation are functioning correctly.
Given the age of your Nagios xi installation, I would advise updating your xi to the latest version you are able to in order to get access to bug fixes and general UI improvements, as some of these rotation issues may have been fixed in the interim. Please let us know if you have any more questions about this, or anything else!
There should be a Backup Limit setting that you can configure to control how many backups are stored before the oldest ones are rotated out. I don't know what the default setting would have been on version 5.5.0 of Nagios xi, but configuring this should fix that issue going forward. This setting is located within Admin > System Backups > Scheduled Backups > Local.
The xi_eventqueue and xi_meta should be getting automatically rotated. if they aren't, you can run this locally to truncate those tables, as they are generally used to track historical data and only need to be retained as is useful to your operation of xi.
Code: Select all
echo "truncate table xi_events; truncate table xi_meta; truncate table xi_eventqueue;" | mysql -u root -pnagiosxi nagiosxi
Given the age of your Nagios xi installation, I would advise updating your xi to the latest version you are able to in order to get access to bug fixes and general UI improvements, as some of these rotation issues may have been fixed in the interim. Please let us know if you have any more questions about this, or anything else!
-
- Posts: 2
- Joined: Wed Feb 12, 2025 1:21 pm
Re: Nagios xi Backups Large
My mistake...our version of Nagios is only a year or so old.
Thanks for the replay jsimon. I will take a look.
Thanks for the replay jsimon. I will take a look.