Grid Failure Logs

In case there is an unexpected grid failure, Report the failure to CA technical support. Below are examples of these types of failures:

Grid reboots for no apparent reason and the operator did not issue a grid reboot command (this would be reported on the grid's dashboard)
One of the grid servers crashes or becomes unresponsive (this would be reported on the grid's dashboard)
The CA 3Tera AppLogic GUI locks up and becomes unresponsive
One of the CA 3Tera AppLogicstandard appliances that is shipped with the release fails for any of the following reasons (this may be reported on the grid's dashboard):
- Fails to boot
- Crashes
- Becomes unresponsive
An CA 3Tera AppLogic CLI command hangs or fails for no apparent reason

Before submitting a bug report to CA, review the release notes to verify the problem is not already known.

With the bug report, collect all of the following logs including backups (that is, xxx.1, xxx.2, and so on) from the grid and send them to CA (the grid and servers logs require administrator access). You may use the 3tsrv utility on each server to collect the server specific logs and information.

Grid controller
- /var/log/messages
- /var/log/applogic
- /var/log/3tshell
- /var/log/secure
Servers
- /var/log/messages/
- /var/log/applogic
- /var/log/xen/ (all Xen logs in this folder)
- /var/log/secure
Appliance logs - only for appliance failures
- /var/log/messages/
- /var/log/applogic
- /var/log/secure
Container and BFC Logs
- /opt/bfc/logs directory on an installed system

In addition to the logs above, collect the following information about each server within the grid (dom0):

lspci
lspci -n
lspci -v
lsmod
cat /proc/cpuinfo
cat /proc/meminfo
dmidecode
smartctl -a for all physical disks on the server