How to make a coredump

From Zarafa wiki

(Difference between revisions)
Jump to: navigation, search
m (Reverted edits by Umoguga (talk) to last revision by Ddebyttere)
(How to report segfaults and coredumps)
Line 21: Line 21:
<pre>ulimit -c unlimited</pre>
<pre>ulimit -c unlimited</pre>
-
Then start the service. When the services crashes again, you will have a file called 'core' or 'core.PID', where PID is the pid number the process had. Compress this file:
+
Then start the service. When the services crashes again, you will have a file called 'core' or 'core.PID', where PID is the pid number the process had. This file may be found in the starting directory or the path given in the running_path option in the server.cfg file. Compress this file:
<pre>gzip core</pre>
<pre>gzip core</pre>

Revision as of 16:56, 15 February 2012

How to report segfaults and coredumps

When a Zarafa services creates an error, you may see the following error in your log:

Caught SIGSEGV, traceback:
0x0000000000481D87
...

To correctly report this issue to the Zarafa development team, you can write an email to support@zarafa.com with these lines from the log.

You must also add the following information:

  • Zarafa version
  • Distribution name and version
  • Architecture (i386, x86_64)

To help the development team even further, you can create a coredump of the process that crashed. To to that, you need to add the following command before restarting the service again:

ulimit -c unlimited

Then start the service. When the services crashes again, you will have a file called 'core' or 'core.PID', where PID is the pid number the process had. This file may be found in the starting directory or the path given in the running_path option in the server.cfg file. Compress this file:

gzip core

And send the core.gz file to support@zarafa.com with the same information about versions and distributions used. If the compressed file is larger than 40 Mb, please upload it somewhere where we can download the file, and add a link in the email.

Adding ulimit to the Zarafa processes

Instead of manually running ulimit while you are logged in to the terminal.

You may also find that it is easier to add it to the init.d script of the process, for example: /etc/init.d/zarafa-server

If the server process was restarted after adding ulimit to the init.d a coredump will be generated.

Which will generally make it much easier for Zarafa to debug the crash.

Add above line "case "$1" in",

ulimit -c unlimited
Personal tools