First, you need a core file above all else. Insure that KMS is on the latest possible version. Before version 6.1.1 KMS did not create core files by default (and contained crashes that are already fixed). UPGRADE!!!
To expedite the process, create a thread dump (it will be a simple text file) and send it in to Kerio support. This will make everything go much faster.
Do not delete the core file. Kerio Support might ask for it later. Instead, compress it.
We need to know about your linux. Please send us the following information as it is critical for our core analysis.
uname -a cat /etc/redhat-release (if you are running Redhat or Fedora) cat /etc/SuSE-release (if you are running SuSE)
Also, we need to know the version of KMS and build number. We also need to know if you are 32 or 64 bit.
Support will look over the thread dump text file and determine if it is a known crash, or if we need the core file.
If the core is needed, support will create an FTP account so that the compressed core file can be uploaded for a detailed analysis.
This should all be handled in an email support ticket for tracking. At any time, especially if the core has just been uploaded, the customer should feel free to call and update support on the issue or ask for an update.