StdServer: Fiber loop (12d32620) stall detected: last fiber loop iteration started 32672 ms ago.

[#1]

Hello,

We are on Qlik Sense 1.1 in clustered environment.From time to time i'm seeing errors "StdServer:
Fiber loop (12d32620) stall detected: last fiber loop iteration started 32672
ms ago." in engine logs and also in Application event log logged by Qlik engine.Did any one ran in to this issue?.

[achakilam1022]

I upgraded to Jun 2018. Still facing this issue.

[Michael_Tarallo]

Hi Amuktha - I assume that this would happen - as this an issue with your environment (most likely) but as to why it did not occur with a previous release is probably the inclusion of different and additional services that are not part of the later release.

As per Felipe's reply:

Error: StdServer: Fiber Loop stall detected

Article Number:000016454 | Last Updated:17/04/2018

Cause

Fiber-loop stalls indicate a problem with a windows fiber (a kind of thread) that has taken too long to respond

Caused by a busy server, slow network performance particularly when working with large apps stored on network device or share.

Resolution

It would be more a case of investigating the overall server performance, size of the Apps (if these are very large and stored on a network device) perhaps there are issues with Network speed/performance.

Any performance issues should be investigated with their local IT team to help reduce the number of fiber loop errors reported.

Have you reviewed this and have you opened a support ticket with Qlik?

Regards,

Mike T

Qlik

[balabhaskarqlik]

I think so:

Some times, Missing error fetching causes an infinite loop in script / measure execution.

When script throwing an UN-handled error, this turns into an infinite loop, because the script fails to extract the error from the event.

So the loop continues, causes more network usage & app performance degrades.

Restart the service, debug the app.

[achakilam1022]

All our app reloads are successful

[achakilam1022]

We have 7 apps each one is around 1 GB and 3 around 0.5 GB and very small incremental/ transform load scripts (<250 kb)

Our server RAM is 120 GB

I've contacted our Qlik partner.

[vasilev]

Hello folks,

I have the same problem as described above. We upgraded from QV 12.1 to 12.2 SR5 two months ago and shortly thereafter got the problem with the "fiber loop error". Restart of the QV services fixes the error temporarily but the problem comes in a certain time again. We reported the problem to Qlik but they have not found any reason or solution yet. Downgrade to 12.1 is not a good solution because of the changes in QVPR in 12.2. In that case we have to restore our repository from the upgrade time and loose the changes which was done after the upgrade. We are very frustrated and desperate about this situation. We will appreciate it a lot if somebody can give us any idea what could we do to solve this problem.

Thanks

Rumen

[stefan87]

I'm working with Rumen and want to add some thing in order to narrow down the source of the problem:

Our Server architechture is distributed which means that our distibution service, webserver and 2 nodes with the QVS are all located on different (virtual) machines. As some of you experience the same problem: Who of those is also using a distributed architecture or even more important: Is someone also using 2 or more nodes for the QVS?

Thanks in advance,

Stefan

[Emmanuelle__Bustos]

Same issue with a QVS 12.2 SR7 New Installation, I don't think this is a environment issue becasue we have a QVS 11.0 Running the Apps fine (We know there are some problems with the Apps calculatons) but in the QVS 12.2 Test Server the Fiber loop error is happening with a few connected users and making the Server unresponsive. I think is a problem with the QIX Engine due I've read different persons posting the issue with Qlikview and Qlik Sense.

This is very frustrating because we need to restart the QV Server service so often.

BTW the fiber loop error usually comes with The "Warning WorkingSet: Virtual Memory is growing beyond parameters - ...... " so I think the issue is when the RAM resource has run out

[vasilev]

Hi Emmanuelle,

We have no issues with growing working set. It really seems to be a bug in the architecture. Do you have a distributed QVS environment with more as one node? We have also a one node test environment in our company and we have  never had the same issue with QV 12.2.

BR

Rumen

[korsikov]

Hi Michael.

Application and number of users not changed. Only when I was upgrade to QS April and faced with "fiber loop" problem