14.1.2 Steps to take when the HADB server did not terminate abnormally

This subsection describes the steps to take when the HADB server did not terminate abnormally.

Procedure

Check the message.

If the HADB server did not terminate abnormally, use a text editor to open the server message log file and check any error message that has been output.

The server message log file is /spool/adbmessageXX.log in the server directory. XX in the file name is a sequential number between 01 and 04. Open the file with the latest modification date and time.

Based on the ID of the last error message that was output, see the manual HADB Messages, and check the cause of the error and the recommended action to take under Action.
Take the action described under Action.

Eliminate the cause of the error by following the steps described under Action. After eliminating the cause of the error, restart the HADB server. After the transactions that were being processed when the error occurred are rolled back, the HADB server starts.

Important: Note that if an error occurs (for example, when an application program or command does not terminate or when the HADB server does not respond), a message might not be output. In such a case, collect troubleshooting information as explained in 14.2 Collecting troubleshooting information (adbinfoget command), and then contact the customer support center.