Logs for SQL and Server Processes

If you are experiencing transaction conflicts, you need to provide support with all the log files for the time period that the problem occurred.

Make sure you have enough free disk space for the log. For more information, see EXAsupport.

Prerequisite

There are no prerequisites for this procedure.

Procedure

The ConfD examples are written in Bash on a Linux terminal running the Exasol tool confd_client, which is accessed by connecting to EXAClusterOS on the database nodes using Exasol Deployment Tool (c4). You can also interact with ConfD from an external tool using Python and XML-RPC. For more information, see ConfD.

Placeholder values are indicated with UPPERCASE characters. Replace the placeholders with your own values.

  1. Use the c4 connect command to connect to EXAClusterOS on the database access node. For example:

    c4 connect -t1/cos

    For more information about c4 commands, see Exasol Deployment Tool (c4).

  2. To find the name of the database, use the ConfD job db_list:

    confd_client -c db_list

  3. To create an SQL server process log, use the command-line tool EXAsupport (exasupport) which collects the logs . Make sure to specify the start date (-s) and end date (-t). Dates are in the format YYYY-MM-DD. For example:

    exasupport -s 2022-08-11 -t 2022-08-11 -e DB_NAME -x1

    If the log file was created successfully, you will see the following message containing the file name:

    Successfully stored debug information into file /exa/tmp/support/exacluster_debuginfo_2022_08_11-23_27_20.tar.gz

  4. To disconnect from EXAClusterOS, type exit or CTRL+D.

  5. The database access node is typically n10. The COS port is typically 20002. To find the database access node's IP address and COS port, use the c4 Show Current Deployments (ps) command. For example: 

    c4 ps
  6. Copy the logs to your local computer using a Secure File Copy (scp) command. Use the exact file name and path previously displayed. For example: 
    scp -P $COS_PORT -i ~/.ssh/$PEM_FILE.xml root@$DB_ACCESS_NODE_IP:/exa/tmp/support/$EXACLUSTER_FILENAME.tar.gz /path/to/folder/

    If you don't remember your PEM file name, search for the CCC_AWS_KEY_PAIR_FILE value in your config file using the following command: c4 config | grep CCC_AWS_KEY_PAIR_FILE.

Verification

To verify the log was successfully copied, use the List Directory Contents (ls) command on your local machine. For example:

ls -lahtr | grep exacluster_debuginfo

returns:

-rwxrwxrwx 1 nc nc  2.3G Apr 13 16:59 exacluster_debuginfo_2022_08_11-23_27_20.tar.gz