Bug report

Before you file a bug report, please try to verify that it is a bug and that it hasn’t been filed already. The following resources can help you:

If you aren’t able to find a resolution, we would like you to fill out the form below and send it to bugs@oblaksoft.com. Please include a concise bug summary into the email subject.

Bug Report Form

MySQL version
From MySQL client run: SELECT @@version;

ClouSE version
From MySQL client run: SELECT @@clouse_version;
From shell (go to plugin directory) run: strings clouse.so | grep @VERSION@

Operating system information
From shell run: uname -a

Bug Type
Choose one: code defect, feature/change request, suggestion, documentation, security.

Repro steps (what did you do?)
We would appreciate a short list of steps, the shorter the better:) Please use the exact list of commands that led to the problem (every little detail may matter) or provide a MySQL / shell / perl / etc. script that can be used to reproduce the problem.

Expected result (what did you expect to happen?)

Actual result (what has actually happened?)
Please describe the results as precisely as possible. If the results contain error or other messages please copy and paste the messages with all the details. If MySQL error log contains errors from ClouSE, provide those as well. In the case of a crash please send stack backtrace from MySQL error log and in the case of a hang capture backtrace for the running mysqld process. See How-tos section below.

Any other details that can help identify the problem.


  1. How to generate a Core dump when mysqld crashes.

    1. Remove any limits on core dump size. To do so include the ulimit -c unlimited command to the scripts that are used to execute the mysqld program prior to mysqld invocation. If running mysqld manually from shell, run the ulimit -c unlimited command before running mysqld.
    2. Add the core-file option to my.cnf in [mysqld] section (http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-program-options-common.html#option_ndb_common_core-file).
    3. You may need to enable the following settings as well and optionally set up naming pattern for dumps being generated:
      echo 2 > /proc/sys/fs/suid_dumpable
      mkdir /tmp/coredumps
      chmod 770 /tmp/coredumps
      echo /tmp/coredumps/core > /proc/sys/kernel/core_pattern
      echo 1 > /proc/sys/kernel/core_uses_pid

  2. How to get a Core dump for a running process.

    From shell run:

    sudo gcore processId

    Or alternatively from shell run:

    sudo gdb -p processId --batch -ex gcore

  3. How to capture a backtrace for a running process.

    From shell run:

    sudo gdb -p processId --batch -ex "thread apply all backtrace full" > backtrace.txt

  4. How to get a backtrace from a Core dump.

    From shell run:

    sudo gdb --core=coreFile --se=procFile --batch -ex "thread apply all backtrace full" > backtrace.txt

    For example:

    sudo gdb --core=~/temp/core.4723 --se=/opt/mysql/server-5.5/bin/mysqld --batch -ex "thread apply all backtrace full" > backtrace.txt


Twitting ...