Overview

There are instances where the monitoring database can become corrupted on the Exinda appliance, and cause no data to be displayed in the pie charts of the dashboard. This can happen for a variety of reasons, including power loss, errors during a firmware upgrade, etc.

Solution

Note: During this troubleshooting, it will be necessary to perform some maintenance on the database. There is a chance that a section of the monitoring database will be cleared while performing this maintenance. If unsure of any of the steps described herein, please, refrain from executing it and contact Exinda Support immediately.

If you have a valid license and a supported device:

If you have recently upgraded the Exinda firmware, wait for 30 minutes after the upgrade is complete to give your device time to upgrade the database. Otherwise, continue with the steps below.
Clear the browser cache and wait 10 minutes before trying to access the login page again.
Force reboot the device from the CLI using the reload force command
Restart the services, in the config mode:
```
    en
    conf t
    service jboss restart
    service datad restart
    service collector restart
    service database restart
```
Note: If you do not have access to the CLI, you need to open a Support Ticket asking them to activate the Restricted Commands License.
Clear the temporary jboss files by deleting all the content in the 'var/data/jboss/tmp/vfs' folder.
```
_shell
cd /var/data/jboss/tmp/vfs/
rm -rf *
```
If after 15 minutes the issue is still unresolved, the database is likely corrupted (check the message log files in /var/log folder for MySQL-related errors).
You will need to clear the database partition. Start the clearing process by stopping the database engine process from the _shell using the Restricted Commands License
```
_shell
pm process mysqld terminate
```
Exit the shell and execute the database cleanup:
```
en
conf t
clear database
```
Cleanup the monitor data using the _shell
```
    _shell
    cd /var/data/monitor
    rm -rf *
```
Important: If the rm command is accidentally executed in the wrong location, damage could be done to the system as there would be no prompting to remove data. You can use the pwd command to check if you are indeed in the 'monitor' partition.

Afterward, restart the daemons again:

    pm process mysqld restart
    pm process datad restart
    pm process collectord restart
    pm process monitord restart
    pm process jboss restart

Wait for 10 mins for the startup of these processes.

Testing

Your database-related issues should be solved, eg: the illustrations (pie charts and report data) should be displayed in the dashboard.

Articles in this section

The Monitoring Database Has Stopped or Become Corrupted

Overview

Solution

Testing

Articles in this section

Overview

Solution

Testing

Related articles