topic Re: StdServer: Fiber loop (12d32620) stall detected: last fiber loop iteration started 32672 ms ago. in Management & Governance

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

Wed, 26 Aug 2015 22:41:32 GMT

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

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

Anonymous — Thu, 29 Dec 2016 05:57:08 GMT

Hi sreelakki1‌,

Were you able to get this resolved ? We are seeing the same issue on Qlik Sense 3.1. Could you please help us to understand anything about the above mentioned issue ?

Many thanks in advance.

Hardik

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

francesco_menin — Thu, 06 Apr 2017 07:55:38 GMT

Hi,

did you find any solution to the problem? I experienced the same error:

"The description for Event ID 300 from source Engine cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

StdServer: Fiber loop (a82808da20) stall detected: last fiber loop iteration started 61281 ms ago"

but with a 3.0.1 server version.

Thanks

Francesco

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

amonjaras — Thu, 07 Dec 2017 01:22:21 GMT

Hello! Did you get this solved?

I have the same issue on QS Desktop Nov 2017 patch 1

Thanks!

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

madhur_cargotec — Thu, 15 Feb 2018 09:41:31 GMT

Hello ,

Did you get the solution on this. We are facing the same issue in QV 12.20 November 2017 SR1

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

navpinto — Fri, 16 Mar 2018 16:49:57 GMT

Hello,

We have the same issue on QV 12.20 November 2017 SR3.

Someone have the solution? Or some clue?

Thanks.

Regards,

Nuno

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

Ricardo_Gerhard — Thu, 29 Mar 2018 17:37:24 GMT

I´ve a customer with the same issue and I opened a case on Qlik.

If you have a possibility to remove ao shared objects or delete users objects in your current applications, you may find a solution.

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

navpinto — Wed, 04 Apr 2018 13:56:31 GMT

Hello,

We still facing this issue in the productive system.

Can you share the reponse from Qlik support?

Thanks.

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

amonjaras — Wed, 04 Apr 2018 16:20:39 GMT

I never got a response, but the problem disappeared when I upgraded to Feb 2018.

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

Ricardo_Gerhard — Wed, 04 Apr 2018 16:31:48 GMT

Dear Nuno Pinto,

We still have a ticket open in Qlik Support for analysis, no answers or solutions yet, but they are analysing the case. Do you have a support ticket open too?

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

navpinto — Thu, 05 Apr 2018 09:30:35 GMT

Hello,

We have a support ticket open, no solution yet.

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

korsikov — Fri, 04 May 2018 18:49:37 GMT

Have the same problem on Aprel 2018

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

felipe_dutra — Wed, 09 May 2018 13:10:03 GMT

Hi.

Qlik has published an article about it.

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.

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

Ricardo_Gerhard — Wed, 09 May 2018 15:27:05 GMT

It seems as a generic answer, but I really would like to know:

Why was this message not being displayed in older versions?

When this message is displayed, there are a performance problem or something wrong could happen in the environment?

Is there a Qlik Resource to find out which object or application made this behaviour?

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

korsikov — Tue, 15 May 2018 13:25:53 GMT

I'm totally agree with Ricardo.

Why was this problem not affected in previous versions?

it usually happens like this. After the error of Internal inconsistency, type F,, the Engine.exe process is dropped and then "Fiber loop" error cycles cyclically. with zero CPU utilization and very low server Qlik sense performance

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

maheshmantha — Tue, 15 May 2018 19:47:15 GMT

Are they not looking at porting the code to Linux. (Fibers (Windows)). it could be the reason why we're seeing this now.

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

korsikov — Tue, 22 May 2018 14:50:39 GMT

Write some script on powershell. Give all community "as is"

Create new Task every 10 min and go

$Date=(Get-Date).Addminutes(-10)

(Get-Eventlog -LogName Application -After $Date -EntryType "Error" -Source "Engine" | where {($_.message -match "Fiber") -or ($_.message -match "inconsistency")}) | FT -auto -wrap >> "c:\task\event.log"

[string]$Countstr=Get-Eventlog -LogName Application -After $Date -EntryType "Error" -Source "Engine" | where {($_.message -match "Fiber") -or ($_.message -match "inconsistency")} |Group-Object -Property "Source" | Format-Table Count -Auto -HideTableHeaders | Out-String

Write-Output "Countstr" $Countstr

if (-not[string]::IsNullOrEmpty($Countstr))

{

[int]$Count = [convert]::ToInt32($Countstr)

Write-Output $Count

if ($Count -gt 0 )

{

"===================" >> "c:\task\event.log"

Write-Output (Get-Date) "Engine has a problem. Restart needed" >> "c:\task\event.log"

Restart-Service -Name "QlikSenseEngineService"

Get-Process -Name Engine | Stop-Process -Force

}

} else {

Write-Output "No Engine Events. All system go!"

}

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

dailyfood — Sun, 27 May 2018 09:56:05 GMT

We are suffering the same issue on QVS November 2017 SR4. Have you got any response from Qlik regarding this?

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

Ricardo_Gerhard — Tue, 29 May 2018 16:32:31 GMT

Of course, the situation is a WAD (works as designed) based on application development. I think some bottlenecks was changed, identifying several sets of data being used incorrectly when the product was rebuilt.

We are working on qvw to release small applications without complexity.

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

achakilam1022 — Thu, 14 Jun 2018 21:26:36 GMT

Hi Alexander,

I'm having the same issue on April 2018 version. Were you able to get this resolved?

Thanks!