How to trace ODAG service crash errors in the log files

[Sebastian_Linser]

Sporadic ODAG service errors may be difficult to troubleshoot and require tracing in the log files. This article aims to give a basic understanding of how to trigger the error more reliably and where to look for the associated log files. 

• Before you get started, change the log level to debug in the On Demand Apps settings in the Qlik Sense Management Console. Restarting Qlik Sense Service Dispatcher will apply the new settings.
• ODAG logs are stored in the Qlik Sense log directory in the Logs\OdagService subfolder.

One way to find the cause is to first disable the ODAG service in the service dispatcher config and try to start it manually.

Disable ODAG Service

1. In the file C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf find the [odag] section
2. Add Disabled=true in the parameter list
3. Save the file
4. Restart the Service Dispatcher

Run the ODAG service manually:

1. Start a command prompt in administrator mode
2. Switch to C:\Program Files\Qlik\Sense\ServiceDispatcher folder
3. Run Node\Node.exe ..\OdagService\dist\index.js --secure=true --port=9098
4. If ODAG crashes, the crash will now be shown in the error trace.

Environment:

Qlik Sense Enterprise on Windows