Only do this while the mailserver is in the frozen state. If the mailserver is working normally, we will not find the problem in the core file.
(The commands we actually typed are in red.)
root# ps auxw | grep mailserver root 29225 0.5 5.3 125892 27332 ? Ssl Jun30 218:43 /opt/kerio/mailserver/mailserver /opt/kerio/mailserver root 29229 0.0 4.0 36108 20668 ? Sl Jun30 0:57 /opt/kerio/mailserver/plugins/avserver 32 37 root 29236 0.0 2.9 28020 15024 ? Sl Jun30 0:02 /opt/kerio/mailserver/plugins/spamserver 32 39 root 440 0.0 0.1 4360 648 pts/2 R+ 16:48 0:00 grep mailserver root# kill -SEGV 29225 root# gzip /opt/kerio/mailserver/core.29225 root# ls -l /opt/kerio/mailserver/core.29225.gz -rw------- 1 root root 5517819 Jul 30 16:49 /opt/kerio/mailserver/core.29225.gz root#
In this example, the process showing "/opt/kerio/mailserver/mailserver /opt/kerio/mailserver" is the Kerio MailServer process. The PID for this process is 29225 in this example. It will be different every time.
The "kill" command is used to create the core file and terminate the process. You will need to start KMS again after doing this.
The "gzip" command is used to compress the core file so that it can be sent to us via FTP.
Gzip the most recent core, and send it to our FTP site. Call Kerio technical support for an FTP account.