Cause

If jboss is not up and running for any reason, users will see this message and will be unable to log into the appliance.

These reasons can include:

The database is not operational

The jboss process not deploying properly

The Proxy is resetting the jboss connection

There is no space left on the device

The device is just starting up after a reboot and is not ready to accept a login

Resolution

Troubleshoot

Please follow the troubleshooting steps below:

Clear the browser cache.

If for any reason, the browser cache is trying to provide a cached page, whereas the Exinda login page has been updated by Java, this message will be shown on the screen. Clearing the cache or using a different browser will help.

Restart process jboss

Note: If the above doesn't help, go to the command line and restart jboss using the following commands

enconf tservice jboss restart

Note: Wait for 5 minutes before accessing the Web Interface.

Restart the database and jboss

service database restart

[Wait for 3-4 minutes, or do the command 'show log continuous' from the en level and wait until the message "Database now online" is seen]

service jboss restart

If the above do not help, restart the proxy service.

service proxy restart

Contact Support.

If the above doesn't work, open a case with Exinda TAC, as it will require a deeper examination into the device.

Internal Notes

Steps for TAC Support

Verify if browser cache has been cleared.

Verify is jboss was restarted.

Go to the shell and clear the directory /var/data/jboss/tmp/vfs

Also check space in /var partition and clear temporary files if necessary.

Check this directory /opt/tms/jboss/standalone/deploy for any *.undeployed files, and delete them.