Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Qlik Sense Engine Service stops but engine.exe still running

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Qlik Sense Engine Service stops but engine.exe still running

Last Update:

Oct 18, 2023 8:09:46 AM

Updated By:

Sonja_Bauernfeind

Created date:

Apr 12, 2019 9:57:19 AM

The Qlik Sense Engine Service stops but engine.exe remains running.

This is usually due to a high memory consumption, so when you stop the Qlik Sense Engine Service, the engine.exe will keep running it has released the memory. This can take a long time. 

Possible error message in Windows events log:

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Engine.exe (77404) consumed 66804117504 bytes, dotnet.exe (29264) consumed 581591040 bytes, and dotnet.exe (49860) consumed 523714560 bytes.

 

Resolution:

The engine.exe can be manually stopped.

 

Related Content:

Windows successfully diagnosed a low virtual memory condition  

Labels (1)
Comments
RajaDumpa
Contributor III
Contributor III

Do we know what consumes the engine service even after the Central node is off ,and when no user traffic exists. This happened with 2020 Oct SR release of Qlik Sense. 

 

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @RajaDumpa 

Can you clarify what you mean with "Central Node is off"? The Qlik engine will not stop consuming memory only because there is no traffic; see Why does the Qlik Sense Memory usage remain high?  

All the best,
Sonja 

rockabs
Contributor III
Contributor III

@Sonji  FYI, We have the same issue in our account and that is fixed in May 2022 Patch 4.

RajaDumpa
Contributor III
Contributor III

@Sonja_Bauernfeind  : Sorry, I should have explained the issue a bit better. Since engine is engaged mostly when user traffic exists to perform calculations etc. I assumed that if there is no Traffic at a given point in time, It should be easy to stop the Engine service without being challenged. 

In our case, the Engine Service was consuming 80% of the CPU (256 GB RAM - AWS box) with no trace to the source of its consumption. I had to kill it manually after waiting for 15 mins. event logs doesn't give any details and even Engine logs from that specific node didn't have any logical information. 

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @RajaDumpa as seen in the documentation provided to you, the engine will not drop memory and retain it up to its low working set limit. So if the low working set limit is set to 80%, this is where it stays. 

New user traffic, documents, selection, etc, would then begin to have cached results replaced in memory once activity ticks up again.

And the key word here is "in memory". Our engine operates in memory.

If you are looking to address this high memory consumption, I would suggest reviewing Optimizing Performance for Qlik Sense Enterprise. For another walkthrough on how memory is used, you can look at this video (I forgot to link to it earlier): Understanding Qlik Sense Performance.

To follow up on Rockabs' comment: An upgrade is also recommended. Simply since we have done quite a bit of optimization on how our engine behaves over the years.

 

All the best,
Sonja 

altanem
Contributor
Contributor

Hello,

We have faced similar issue about that. "Qlik Sense Engine Service"  running but when we check event logs we see error log within every few minutes. We have tried many ways. But ıt is still same. You can see error log below. Do you have any idea ? What should we do ?

altanem_1-1674821391729.png

 

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @altanem 

This could have several root causes. I assume this is not a rim node where the engine is not meant to be used but is installed anyway? If it is, check Qlik Sense: Windows service Qlik Engine cannot be started on a node where Engine service is disabled....

Overall I would suggest reviewing the Qlik Sense log files directly rather than only relying on the Windows Event output.

For guidance on how to troubleshoot Qlik Sense engine-related issues, see:

STT - Troubleshooting Qlik Sense Engine 
Qlik Sense - How to troubleshoot Engine related issue 

If you need more direct help, I suggest posting about your issue and your findings in our Qlik Sense Management forum, where our active engineers and community members can better assist you. When posting there, make sure to give as much detail as you can, such as what versions you are running, the architecture (multi node, single node, etc), as well as errors you have located.

All the best,
Sonja  

BTIZAG_OA
Creator
Creator

Hello @Sonja_Bauernfeind 

we have same this behaviour happening on our environment. 

Qlik Sense Service is running and Engine.exe process in shown in taskmgr as running but on QMC its seems Engine is stopped and there is no CPU activity on Engine.exe its %0. But RAM usage is about %10 and its not heavliy used as you mentioned on this topic. Also Event Viewer throws away below log entry.

 

StdServer: Fiber loop (1f79b222c20) stall detected: last fiber loop iteration started 308047 ms ago.

 

How can i prevent this happening on servers. We have to restart production site on nodes whenever this happens. Which log should i check for more detail infor about this?

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @BTIZAG_OA 

I would recommend the same resources as I recommended to altanem above. However, in your case, I want to also highlight the video shown here: How to start investigating Qlik Sense Performance and address high RAM usage, as your description may indicate that you may be experiencing resource issues (probably prior to when you see the engine is stopping). 

For guidance on how to troubleshoot Qlik Sense engine-related issues, see:

STT - Troubleshooting Qlik Sense Engine 
Qlik Sense - How to troubleshoot Engine related issue 

If you need more direct help, I suggest posting about your issue and your findings in our Qlik Sense Management forum, where our active engineers and community members can better assist you. When posting there, make sure to give as much detail as you can, such as what versions you are running, the architecture (multi node, single node, etc), as well as errors you have located.

All the best,
Sonja 

mgranillo
Specialist
Specialist

@Sonja_Bauernfeind We had a case of high RAM usage and the engine came down (as indicated in the QMC) and restarted on it's own.  We monitor the engine service in Windows but it was up the whole time so we never knew about the outage.  Do you know a way to track this type of outage? How does the engine come down but the service never stops? 

Version history
Last update:
‎2023-10-18 08:09 AM
Updated by: