Using Kerio Assist tool
Whenever a problem occurs (e.g. when connection is closed improperly, connection "freezes” or Kerio Connect crashed etc.), automatic restart is initiated by the corresponding process. Initiation of the application’s restart also generates and saves a crashdump log that might help discover the problem’s cause. Then, when an administrator connects to Kerio Connect, a Kerio Assist dialog asks them to decide whether the crashdump log would be sent to Kerio Technologies for analysis. Behaviour of the Kerio Assist differs in dependence on the operating system.
- Windows — the Kerio Assist dialog is opened immediately upon the incident.
- Mac OS X, Linux — the Kerio Assist dialog is opened upon the first startup of the Kerio Administration Console after the incident.
However, you can be asked by technical support engineer to initiate kassist manually. In that case, you have to specify some of the parameters. A complete list of parameters is available under the --help option.
NOTE
If you are running Windows 8, make sure you run kassist as Administrator.
EXAMPLES
A/ Windows
cd "C:\Program Files (x86)\Kerio\MailServer\"
kassist -n "description of the problem" -P KMS -e "your@email.com" -N "C:\Program Files (x86)\Kerio\MailServer\user.dmp"
B/ Linux
sudo /opt/kerio/mailserver/kassist -n"description of the problem" -P KMS -e "your@email.com" -N "/opt/kerio/mailserver/core.PID"
NOTE
PID is process identifier number. A higher number doesn't mean a newer process. It is better to sort core files by date to locate the latest one.
You will be prompted for your system password.
C/ Mac OS X
sudo /usr/local/kerio/mailserver/kassist -n "description of the problem" -P KMS -e "your@email.com" -N "/cores/core.PID"
NOTE
PID is process identifier number. A higher number doesn't mean a newer process. It is better to sort core files by date to locate the latest one.
You will be prompted for your system password.
NOTE
The kassist utility must have access to system folders! It's recommended to start it as superuser. Paths in examples may be different on various Linux distributions and platforms. Also, you should have a ticket from your Support team, before performing the upload. This ticket number must be included in any uploads you perform, as part of the investigation of your crash.