Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Troubleshooting Data Movement gateway

This section describes various actions you can perform to troubleshoot Data Movement gateway.

Viewing and downloading log files

The log files provide information about Data Movement gateway operations. Qlik Support might ask you to provide log files for troubleshooting purposes. You can view or download the log files in the Log viewer. Under normal circumstances, there is no reason to examine the log files, but if you experience repeated failures or other issues, the log files will often help pinpoint the cause.

Information noteViewing and downloading the logs requires the Can consume data role.

To open the Log viewer:

  1. Select Administration from the launcher menu (), and then Data gateways.

  2. Locate your Data Movement gateway. Then, from the menu at the end of the row, select View logs.

    The Log viewer window opens.

  3. From the drop-down list in the top left, choose the type of log that Qlik Support has asked you to view or download.

    The following log types are available:

    • Data Movement gateway logs (repagent) - General events related to the Data Movement gateway services
    • Replication engine logs (repsrv) - Events related to data movement
    • Source connection logs (rependsrv) - Events related to SAP Extractor and SaaS application data sources
    • SaaS application logs (ex-data-provider-agent) - Events related to SaaS applications data sources
    • ELT engine logs (qdi-db-commands-local-agent) - ELT operations on the target including data registration, storage, transformations, and data marts
  4. From the adjacent drop-down list, select the log you want to view or download. The log files are ordered from the newest (the currently active log file) to the oldest. After you select a log file, you can use the and buttons to jump to the start or end of the log file respectively.

    Tip noteThe view of the log file is not updated automatically with the latest messages. To update the view, click to jump to the end of the log file, which will be updated with the latest messages.
  5. To download the log file, click Download.

    The file will either be downloaded to your computer or you will be prompted to save it, depending on your browser settings.

Changing the logging level of the Data Movement gateway logs (repagent)

Qlik Support might ask you to change the current logging level before sending the Data Movement gateway (repagent) logs. You can view and change the current logging level by running the following commands from /opt/qlik/gateway/movement/bin:

  • To view the current logging level, run:

    ./agentctl configuration getloggers
  • To change the logging level to Trace, run:

    ./agentctl configuration setloggers -l Root -v DEBUG
  • To change the logging level to Verbose, run:

    ./agentctl configuration setloggers -l Root –v DETAILED_DEBUG
Information noteAfter running any of the setloggers commands, you need to restart the Data Movement gateway service as described in Restarting the service.

Updating the registration key

Changing the registration key might be necessary in the unlikely event that the key becomes corrupted or if you suspect the data gateway server was accessed by an unauthorized user.

To update the registration key:

  1. Generate and copy the key as described in steps 6-7 of Stage two: Install and set up the Data Movement gateway.
  2. Select Administration from the launcher menu (), and then Data gateways.

  3. Locate your Data Movement gateway. Then, from the menu at the end of the row, select Edit.

  4. Paste the key into the Key field (replacing the existing key) and save the settings.

  5. Return to the Data Movement gateway server and stop and then start the Data Movement gateway service as described in Data Movement gateway service commands.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!