Collecting information to analyze a core file

{question}

What information should I collect for the Support Team to analyze a core dump?

{question}

{answer}

Like any Linux process, when a SingleStore process crashes, it can be configured to generate a core_file at the time of the crash. These are very helpful and usually required to root cause the crash.

For our team to properly analyze the core file, the following information is required from node that crashed:

1. The core file itself. This can sometimes be many gigabytes in size. Core files typically get created in the data directory of the node which has crashed and produced a core dump.

2. The libc files from your host system. Run the following command which creates a directory in your /tmp directory with all the necessary lib files to analyze the core dump. Upload the libs directory created from this command to the support ticket.

mkdir /tmp/libs && ldd [path_to_memsqld] | awk 'NF == 4 {print $3}; NF == 2 {print $1}' | grep -v "linux-vdso" | xargs -I '{}' cp {} -t /tmp/libs/

• Run ps aux | grep memsqld | grep -v safe to locate the path of the memsqld process.
  
  For example:
  

  ubuntu@kafka:~$ ps aux | grep memsqld | grep -v safe
  memsql 14026 12.7 3.3 4359704 549672 ? Sl 18:47 30:23 /opt/singlestoredb-server-7.8.17-69cee1f1a3/memsqld --defaults-file /var/lib/memsql/eaaceb9a-610d-44f9-9f57-689b8e5bb2c4/memsql.cnf --user 113
  memsql 14027 0.0 0.4 291408 81200 ? Ssl 18:47 0:00 /opt/singlestoredb-server-7.8.17-69cee1f1a3/memsqld --defaults-file /var/lib/memsql/eaaceb9a-610d-44f9-9f57-689b8e5bb2c4/memsql.cnf --user 113

3. The output of the following command: cat /etc/*-release.

Collect these three things (the core file, the library names and actual files, and the output of the last command) and send them to support so we can help in investigating the nature of the crash.

{answer}