CloudBolt Appliance is Unresponsive Due to MySQL Error

Overview:

CloudBolt does not respond correctly and when this happens jobs start to fail and become stuck in pending status or the jobs get queued up. This generally happens due to several factors for example if there is not enough RAM for the CloudBolt server and would need to add accordingly. One of the other main factors to look out for in the logs would be MySQL error, as shown in Figure 1:

^{Figure 1:}

File "/usr/local/lib/python3.6/site-packages/MySQLdb/connections.py", line 50, in defaulterrorhandler
raise errorvalue
File "/usr/local/lib/python3.6/site-packages/MySQLdb/cursors.py", line 247, in execute
res = self._query(query)
File "/usr/local/lib/python3.6/site-packages/MySQLdb/cursors.py", line 411, in _query
rowcount = self._do_query(q)
File "/usr/local/lib/python3.6/site-packages/MySQLdb/cursors.py", line 374, in _do_query
db.query(q)
File "/usr/local/lib/python3.6/site-packages/MySQLdb/connections.py", line 277, in query
_mysql.connection.query(self, query)

However, the clue to the issue is in Figure 2, where it specifies that a certain table is full in the database:

^{Figure 2:}

django.db.utils.OperationalError: (1114, "The table 'history_serverhistory_custom_field_values' is full")

Solution:

1. One way to resolve this issue is to check the size of the disk for the VM for which CloudBolt is installed.

2. Make sure the root volume is not at 100% full.

3. Run this command for the disks: df -h

4. Extend the disk or free up space.