QVS crashes often with "Error Restart: Server aborted trying to recover by restart. Reason for restart: No document purger activity for 120 seconds"

[Anonymous]

Hello,

in the past couple of months, we experience QVS crashes with the log message "300 Error Restart: Server aborted trying to recover by restart. Reason for restart: No document purger activity for 120 seconds".

On bad days, it may happen 10 to 15 times. Sometimes the crashes are 7 minutes apart, up to 4 consecutive times.

Naturally, this causes a very bad user experience.

We optimized our document and monitored the server's memory, CPU and IO consumption - nothing out of the ordinary, plenty of resources available.

We tried to pinpoint with detailed audit log what's the trigger - found no clue yet.

Has anybody encountered this issue?

Can "120 seconds" be tuned - perhaps a larger value is required in our case?

Thanks!

Erez

[Bill_Britt]

Hi,

Most of the time this is outside of Qlik. If you are not using the performance monitor to look at your system, I would turn off the logging for it.

Bill

[Anonymous · Accepted solution]

A happy update:

Following troubleshooting sessions with Qlik, the problem was pinpointed to the layout-state-saving mechanism.

In our major document we have over 3,000 objects (). QV automatically saves and loads their layout state every reload.

When it takes longer that 2 minutes.... The Phoenix watchdog kicks in.

A special test build that allows disabling of this mechanism was created by Qlik and tested by us - seems to solve the problem and greatly improve the reload experience.

Since our users don't modify the layout anyway, this solution suits us.

Stay tuned for SR13 - we were told it is incorporated there in a parameter called EnableApplyLayoutState in Settings.ini, enabled by default (compatible with existing behavior), but can be set to 0.