6 Troubleshooting Exachk for Exalogic

This chapter contains the following sections:

6.1 Potential Problems

You might encounter the following problems when running Exachk:

6.1.1 Runtime Command Timeouts

During the health check process, if a particular compute node, storage node, or switch does not respond to the health-check command within a pre-defined duration, Exachk terminates that command. To prevent the program from freezing, Exachk automatically terminates commands that exceed the default timeouts. On a busy system, Exachk terminates commands when the target of the check does not respond within the default timeout.

For information about extending the timeout duration, see Table 4-1.

Note:

To avoid runtime command timeouts from occurring during health checks, ensure that you run the tool when there is least load on the system.

6.1.2 Issues With the Local Environment Settings

See Section 4.1.

6.2 Getting Support for Exachk

For support on any problems that you might encounter while using Exachk, create a service request on the My Oracle Support website:

http://support.oracle.com

Note:

You might see some errors in the exachk_error.log file. Most of these errors do not indicate any serious problem with Exachk or the system. To prevent these errors from appearing on the screen and cluttering the display, Exachk directs the errors to the exachk_error.log file. You usually need not report any of these errors to Oracle Support.