Qlik Community

Qlik Sense Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

navpinto
New Contributor

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

Hello,

We have a support ticket open, no solution yet.

Partner
Partner

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

Have the same problem on Aprel 2018

Partner
Partner

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

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.

Employee
Employee

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

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?

Ricardo Gerhard
OEM Solution Architect
LATAM
Partner
Partner

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

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

maheshmantha
New Contributor

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

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

Partner
Partner

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

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!"

}

Highlighted
dailyfood
New Contributor II

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

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

Employee
Employee

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

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.

Ricardo Gerhard
OEM Solution Architect
LATAM
achakilam1022
Contributor II

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

Hi Alexander,

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

Thanks!