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?.

[Michael_Tarallo]

Hi Alex, et al - is there a support ticket open on this issue?

[stefan87]

Hi Michael,

we face a similar problem since upgrading to QV 12.20 and opened a case in Qlik Support platform several weeks ago (see latest posts below from my colleague Rumen and me). The supporters couldn't help us in finding the source of the problem so now we are planning to roll back to 12.10 because all of our applications were working properly before the update.

BR,

Stefan

[korsikov]

Thanks for your attention to this case. We planned change license mode from Tokens to QAP. If after that problem  will not solved, I will open a new case on support portal.

[stefan87]

Opening a case is a good idea and indicates that the error seems to be a common problem which affects several customers. Please let us know if changing license mode can do the trick.

Thanks,

Stefan

[Emmanuelle__Bustos]

Hi Rumen,

We have a Test Environment with 1 QVS and 1 QDS Node (Publisher) and the issue comes when testing a large and very complex qvw, I think the QIX has issues (bug??) whit this kind of qvw's due several users has the same problem.

[vasilev]

Hi Emmanuelle,

Do you have already any plan / approach how to resolve this problem? It is maybe we have the same configuration setting in our environments which cause this faulty behavior. If we don't find any solution in the next days we have to downgrade to QV 12.1.

BR,

Rumen

[Emmanuelle__Bustos]

Right know we are working on tuning the QVW because the BD relations are so complex.

[npapapicco]

Hello,

did changing license mode fixed the issue? We are on QAP license  mode with 6 cores and suffering the same problems with QS September. We have to restart services one or more times a day because the server becomes un-responsive.

We have a support ticket open and hope to receive insights for a solution.

Nicola 

[s_kabir_rab]

One of our client is experiencing the similar issue from the last few days. This is causing the server going down. We also experienced some issue with the PostgreSQL when this appeared in the log... I am going to open a ticket as i cant find the root cause, server was working with no issues till few days ago.

[npapapicco]

We fixed the issue starting with a fresh virtual machine and installing November 2018 SR2 version.

The error is not showing anymore, also when allocated RAM is at 70% (total RAM 224GB) and more.

The old virtual machine had the following upgrade path

June2017 -> February2018 ->April2018 -> September2018 -> November2018

We saw the error the first time with version February2018, maybe before the server was not so overloaded with a lot of concurrent users.  

However now performance have raised up and we don't see fiber loop error registered.

Nicola