Skip to main content
The Qlik February 2020 release has been delayed by a couple of weeks due to a security vulnerability that recently surfaced with Node.js, which is impacting a large portion of the software industry. The release is expected to be delivered before the end of the month, with a target date of February 25th, as Qlik is actively running tests to ensure that the February GA release is stable and not affected by this security malware.
To read more about this vulnerability:
QlikWorld 2020 Global Conference. Keynote speaker Malcolm Gladwell. Register now and save

Troubleshooting Qlik Associative Big Data Index

This section describes problems that can occur when deploying, indexing or using Qlik Associative Big Data Index. You can enable verbose logging to get more information for troubleshooting.

Enable verbose logging for an app

If you have problems with a live mode app, you can enable verbose logging of all traffic between the QIX engine and the QSL system manager with the script variable QABDI_TraceQslToSystemLogAtVerbosity. The traffic related to the specific app is logged in the Qlik Sense Engine log.

The variable has the following settings to control which severity level to apply to the messages. You need to set the severity level to be at least as high as the engine System log level in Qlik Management Console, or the messages will not be displayed in the log.

  • 0 = off
  • 1 or 2 = Error

    Messages regarding unexpected situations and errors that prevent the server from operating normally, or when a service or application has to shut down in order to prevent data loss..

  • 3 = Warning

    Messages with an indication that an error will occur, if no action is taken.

  • 4 = Info

    Normal operational messages that may be harvested for reporting or measuring throughput. No action is required.

  • 5 = Debug

    Information useful to developers for debugging purposes. This level is not useful during normal operation as it generates vast amounts of logging information.

Example: Enable logging with Info severity level

SET QABDI_TraceQslToSystemLogAtVerbosity=4;

You need to reload the app after changing the variable setting. You also need to have the engine System log level set to at least 4 in Qlik Management Console.

Note: Verbose logging for Qlik Associative Big Data Index can create a large number of log messages. We recommend that you enable it only when troubleshooting problems with an app as it can have an impact on performance.

The Qlik Sense app hangs

If you experience that the Qlik Sense app hangs and does not respond to input, this is either due to:

  • Qlik Associative Big Data Index components in the cluster are unstable.
  • The Qlik associative engine is unstable.

The first step is to verify that Qlik Associative Big Data Index services are running on all nodes in the cluster:

  • Indexing Manager
  • Indexing Symbol Servers
  • Indexing Indexer Servers
  • QSL Executor and Registry
  • QSL Manager
  • QSL Workers

Connect to all nodes and check that Qlik Associative Big Data Index services are running with:

  • ps -ef | grep -E '[i]ndexer_tool|[q]sl_processor_tool'

If indexing and QSL services are not responding or have stopped running, you should kill all running processes and restart the services.

To kill all QSL and Indexer processes:

cd /home/ubuntu/dist/runtime/scripts/qsl_processor ./ cd /home/ubuntu/dist/runtime/scripts/indexer ./

To restart services:

cd /home/ubuntu/dist/runtime/scripts/indexer ./ cd /home/ubuntu/dist/runtime/scripts/qsl_processor ./

We also recommend that you restart the Qlik associative engine:

  1. Connect to the Qlik Sense client host with RDP.
  2. Open Services in Settings.
  3. Locate the Qlik Sense Engine Service (Qlik Sense) process and restart the process.
  4. If the Qlik Sense Engine Service Stop operation is taking a long time, you need to kill the process in Task Manager and then start the service from Services.