Overview

This article guides you on how to troubleshoot if you are unable to access Web UI.

Process

1. Check if the database is running:
   CLI command: show service database
If the database is not running:
   CLI command: service database restart
   
2. If the database is running but still unable to access Web UI, restart JBoss:
   CLI command: service jboss restart
   
3. If the database is still stopped after a restart, check if the monitor or var partition is full:
   • Check the space partition using the shell command: df -h
   • Check which files are using up space using the shell command: du -x /var |sort -rn| head -20
     
4. If /var/ is full or have 0% free space, remove the files that du -x show??
   1. Change directory to the folder where the file is located: rm -rf [filename]
   2. Repeat until df -h shows free space in /var.
   3. Once /var creates a free space, restart the database using the CLI command: service database restart
      
5. If /var is not full and the database still won't start or keeps crashing, it is most likely database corruption.
   1. Change directory to the monitor partition: cd /var/data/monitor
   2. Check if you are indeed in the monitor partition: pwd
   3. Clear the partition: rm -rf *
      
6. If it is the JBoss files that are filling up the var partition, stop the JBoss process using CLI command: service jboss terminate
   
7. Clear the contents of var/data/jboss/tmp/vfs.