EXAsupport

This section explains how to access and use EXAsupport.

In case you have an issue with Exasol, our Support team can help you resolve it. To get help, create a case.

To make it possible for the Support team to investigate and troubleshoot your issue, you need to provide log files from your system. EXAsupport is an Exasol 8 command-line tool used to create logs. This section explains how to access and use EXAsupport.

For more information about how to gather information for Support and create different types of logs, see Log Files for Support.

Access EXAsupport

EXAsupport is available on every database node. To access EXAsupport, log into the database access node using Exasol Deployment Tool (c4).

c4 connect -t1/cos

To get started with EXAsupport, view the EXAsupport help.

exasupport -h

The user executing the EXAsupport commands is the user who is logged into the node, which is typically root. There are no extra authentication steps when using EXAsupport in this way.

EXAsupport Option Definitions

Long Option Short Option Description
--help -h

Lists all options, definitions, and syntax.

--debug-info=DEBUGINFO -d DEBUGINFO

Comma separated list of Debuginfo to retrieve:

  • 1 = EXAClusterOS logs
  • 2 = Coredumps
  • 3 = EXAStorage
  • metadata or 0 = all
--start-time=YYYY-MM-DD [HH:MM] -s YYYY-MM-DD [HH:MM]

Start time of logs.

--stop-time=YYYY-MM-DD [HH:MM] -t YYYY-MM-DD [HH:MM] Stop time of logs.
--exasolution=EXASOLUTIONLOGS -e EXASOLUTIONLOGS Comma separated list of system names, or "All databases".
--exasolution-log-type=EXASOLUTION_LOG_TYPE -x EXASOLUTION_LOG_TYPE

One of these EXASolution log types (digit or full name):

  • 1 = All

  • 2 = SQL processes

  • 3 = Server processes

--session=SESSION -i SESSION Comma separated list of specific sessions from which to get logs.
--backtraces=BACKTRACES -b BACKTRACES

Process back traces:

  • 1 = EXASolution server processes

  • 2 = EXASolution SQL processed

  • 3 = EXAClusterOS processes

  • 4 = ETL JDBC Jobs

--nodes=NODES -n NODES Comma separated list of node IDs. By default, all online nodes will be included in the log.
--only-archives -a Only download archives.
--only-open-files -f Only download open files.
--estimate -m Only estimate size of debug information.
--outfile=OUTFILE -o OUTFILE Output file to local, or remote: <remote volume name>,<path in volume>.

Check Free Disk Space

Logs can become very large. Before you generate a log, determine the estimated size of the log and ensure you have enough free disk space on the node to store it.

  1. To estimate the resulting log file size, add the Estimate parameter (-m) to the end of the EXAsupport command that you want to run. EXAsupport will then perform a dry run of the command and return an estimated size for the result. For example:

    [root@n10 ~]# exasupport -x2 -m
    12.34 MB

  2. To check your free disk space on the node that will store the log, run the command df (disk free) with the option -h (human readable). For example:

    [root@n10 ~]# df -h
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/nvme1n1     98G   24G   70G  26% /
    /dev/root        20G  1.8G   18G   9% /var/log/host
    tmpfs           372M  872K  371M   1% /run/lvm
    none             64M     0   64M   0% /dev
    none            1.9G     0  1.9G   0% /dev/shm
    none            1.9G     0  1.9G   0% /tmp