Qlik Community

Ask a Question

Support Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team


Troubleshooting Replicate crashes on Linux.

Digital Support
Digital Support

Troubleshooting Replicate crashes on Linux.

The core dump creation may differ between the different flavors of Linux, however, these the generic instructions when not using a special service for capturing the dumps. There will be another article for Linuxes with the abrt service. 


Linux OS level configurations

1. Check if the core-dump is enabled




$ ulimit -a | grep core
core file size (blocks, -c) 0




The core dump setting for the Linux is '0' which means that it's disabled.

2. Enable the core dump settings for Linux, you need to set the size large enough to contain the process image, or 'unlimited':




$ ulimit –c unlimited​




3. Another setting is the location of the generated core dumps:

To find out the current location:




$ cat /proc/sys/kernel/core_pattern




If the result include "abrt", this means that Redhat's abrt service is running, and you may already have core dumps configured.
There will be another article describing the abrt service, the  stackoverflow article provides additional information.

If the abrt is not in use, you should get a path. To modify the core location perform the followings:




$ echo '/tmp/core_%e.%p' | sudo tee /proc/sys/kernel/core_pattern




4. When the crash occurs the following files should be collected:
  • Replicate logs, repcmdxxxxx.log files.
  • The core dump is generated you can detect it by the date that is shown in the Replicate's log.
Labels (1)
Version history
Revision #:
6 of 6
Last update:
‎2020-08-28 05:49 AM
Updated by: