Most commonly known files or logs that can fill up OP5 filesystem or disk spaces

Some of the known large files contributing to disk space include:

1. Backup files having this naming convention - <hostname.company.com.year-month-day>.backup this is by default stored under /root if not configured to have a separate filesystem mount. Those ones oftentimes are in gigabytes depending on the size of your monitoring system.
2. Files /opt/monitor/var/archives/naemon.log-<date> - are naemon archive log files that normally rotates every day.
3. If the culprit happens to be the database, mon log purge can be run to remove old database entries (example, those older than 2 years) that may no longer be relevant for reporting.

Please refer to documentation. OP5 Monitor - Database maintenance and removing old data – Support - ITRS Group

Other than those files and factors affecting available disk space, there are also system-generated files that needs Linux Systems Administrator’s assistance. Like the following:

• /var/log/messages*
• coredump files depending on how the system is configured
• Files under /var/spool/ folder
• And others

We usually recommend installing and using ncdu to get a graphical representation of what’s taking up space, it’s easy to use and normally very helpful.

To install the package:

# yum install ncdu