Operations monitoring apps failing with " Error: Connector is not responding (System error: WAIT_TIMEOUT)"

[Andreas_Giesbrecht]

The Operations Monitoring apps fail to reload with:

Error: Connector is not responding (System error: WAIT_TIMEOUT)

The script log may show the error message when connecting to a specific QLogs table/view in the PostgreSQL database for example "public" or "view_performance_engine".

Environment:

Qlik Sense Enterprise on Windows 

The Qlik Sense engine may have extended logging enabled. The increased logging level can lead to an unexpected increase in load and waiting time. 

 

Resolution:

1. Increase the PostgreSQL connection timeout: Operation Monitor is failing with - Error: Connector is not responding (System error: ***) .
2. Verify the database access as described in: How To Verify if Qlik Sense Is Running With Centralized Logging Service
3. Verify if the file data source is working. This can be done in the load script of each app in the section.
   Change:
   

   SET db_v_file_override     =    0;

   to

   SET db_v_file_override     =    1;

4. Verify if the logging level is set too high and set it back to its original state. Debug logging should only be used when actively troubleshooting.
   1. Open the Qlik Sense Management Console
   2. Open the Engine Service
   3. Select Logging in the right-hand menu
   4. Configure the Logging level as desired