While reviewing Real-Time monitoring, the Exinda appliance is showing No policy despite Circuit policies being enabled.
This Web UI issue might happen after the device's unexpected reboot.
This article provides details on the possible root cause and resolution steps for such No policy problem.
The unexpected reboot might be caused because of the disk space being fully occupied. Web UI cannot display the Virtual Circuits (VC) policies then.
The common reason for the high disk usage is several sysdumps being generated while certain Exinda services, such as MySQL, statisticsd, jboss, etc are crashing.
The sysdumps can be deleted from the Exinda CLI.
- Access the CLI through SSH using Putty on Windows or Terminal app on Mac/Linux.
- Execute the following commands:
Important: if you're prompted for a License key while running
_shellcommand, you need to Activate the Restricted Commands License, open a Support Ticket and ask them to activate it.
- Delete all sysdump files located in /var/tmp folder.
rm -rf /var/tmp/sysdump*
- Restart Jboss.
- Fast reboot the appliance.
reload mode kexec