Backtrace Information

This article explains how to collect backtraces from your Exasol system.

If you open a support case because you are experiencing performance problems or operations that hang, you need to provide backtrace information for the time period when the problem occurred.

In on-premises deployments of Exasol 2025.1 and later you can use Exasol Admin to create an archive with logs and other information to include with your support case. For other versions of Exasol you must use EXAsupport.

Prerequisites

You must have enough free disk space for the logs. For more information, see EXAsupport.

Procedure

  1. You will need the play ID of the deployment in the following steps. To find out the play ID, use c4 ps.

    Example:
    Copy 
    ./c4 ps
          N  PLAY_ID   NODE  MEDIUM  INSTANCE     DB_VERSION  EXTERNAL_IP     INTERNAL_IP  STAGE  STATE    UPTIME    TTL
      ┌─  1  c3275f84  11    host    -            2025.1.0    203.0.113.11    10.0.0.11    d      -        03:50:12  +∞
      │   1  c3275f84  12    host    -            2025.1.0    203.0.113.12    10.0.0.12    d      -        03:50:13  +∞
      │   1  c3275f84  13    host    -            2025.1.0    203.0.113.13    10.0.0.13    d      -        03:50:13  +∞
      └─  1  c3275f84  14    host    -            2025.1.0    203.0.113.14    10.0.0.14    d      -        03:50:13  +∞

  2. Connect to the cluster operating system (COS) using c4 connect -i PLAY_ID -s cos.

    Example:
    Copy 
    ./c4 connect -i c3275f84 -s cos

    For more information about how to use c4 commands, see How to use c4.

  3. Use exasupport -b to collect backtraces. The -b option accepts the following values:

    • EXASolution server processes or 1

    • EXASolution SQL processes or 2

    • EXAClusterOS processes or 3

    • ETL JDBC Jobs or 4

    Example:
    Copy 
    exasupport -b 1,2,3,4

    If a file was successfully created, EXAsupport returns a success message with the file name.

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

  4. Use Control+D or type exit to disconnect from COS.

  5. Copy the file to your local computer by connecting to COS and using the cat command:

    Copy 
    ./c4 connect -t <DEPLOYMENT>.<NODE>/cos -- "cat /exa/tmp/support/$FILENAME" > $FILENAME
    Example:
    Copy 
    ./c4 connect -t 1.11/cos -- "cat /exa/tmp/support/my_log" > my_log

Verification

To verify that the file was successfully copied, use the ls command in the target folder on your local machine.

Example:
Copy 
ls -lahtr ~/mylogs | grep exacluster_debuginfo
-rwxr-xr-x  1 user group 9.8K Sep 20 17:38 exacluster_debuginfo_2022_08_11-23_27_20.tar.gz

To learn more about how to use EXAsupport, see EXAsupport.