Last update:
Last verified version: AAC 4.4.3
Overview
This article addresses the issue of ASGARD Analysis Cockpit malfunctioning when your disk is full or nearly full. To restore its operation, free up disk space.
Prerequisites
The Analysis Cockpit does not work properly. If this is not the case, please modify the Data Retention Policy to free disk space:
https://analysis-cockpit-manual.nextron-systems.com/en/latest/maintenance/retention.html
Save the files to another system if you want to keep the information. ASGARD does not require the following files and they can be safely removed:
-
/var/lib/asgard-analysis-cockpit/log/*.gz -
/var/lib/asgard-analysis-cockpit/events/*.ok
Expected result
The Cockpit functions properly again. Further optimizations are possible via:
-
Optimizing Data Retention (https://analysis-cockpit-manual.nextron-systems.com/en/latest/maintenance/retention.html )
-
Managing Disk Space in Analysis Cockpit: Safe and Unneeded File Deletion Options
Steps to reproduce
Step 1: Delete to required files
nextron@cockpit:~$ sudo -s
[sudo] password for nextron:
root@cockpit:~# find /var/lib/asgard-analysis-cockpit/events -name "*.ok" -print0 | xargs -0 -I'{}' rm '{}'
Step 2: Restart Elasticsearch
If Elasticsearch does not automatically work again after cleaning up some disk space, restart it under Settings > System > Services or with sudo systemctl restart elasticsearch.service.
If this is not working either, you may need to disable Elasticsearch's read-only mode. See Resolving Elasticsearch Data Acceptance Issues Due to Disk Watermark Limit for a how-to.