Obtaining a core file

In case of a crash, a core file may make it easier for us to investigate the issue and to provide a fix. However, typically Linux systems are configured so that core files are not generated by default.

In case the crash is easily repeatable, please do as follows to obtain a core file that can be attached to a bug-report (https://mariadb.atlassian.net/projects/MXS).

• Turn yourself into the user maxscale

    user@host$ sudo su - maxscale -s /bin/bash
    [sudo] password for user: 
    No directory, logging in with HOME=/
    maxscale@host:/$
  

  The user maxscale does not have a login shell, which is why it must be specified explicitly.

• Enable core files.

    maxscale@host:/$ ulimit -c unlimited
    maxscale@hosr:/$ ulimit -c
    unlimited
  

  If the last command does not produce unlimited but 0, you may need to enable core files in /etc/security/limits.conf

• Move to a directory where maxscale has write rights. Otherwise, the core file cannot be written.

    maxscale@host:/$ cd /var/lib/maxscale
  

• Start maxscale in the console.

    maxscale@host:/var/lib/maxscale$ /usr/bin/maxscale -d
    Info : MaxScale will be run in the terminal process.
    Syslog logging is disabled.
    Configuration file : /etc/maxscale.cnf
    ...
  

• Do whatever is needed to make maxscale crash.

    MaxScale 1.2.1 received fatal signal 11
  
  
    Writing core dump
    Segmentation fault (core dumped)
  

• Attach the core file to a bug report.