Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Streamlining user types in Qlik Cloud capacity-based subscriptions: Read the Details
cancel
Showing results for 
Search instead for 
Did you mean: 
jpjust
Specialist
Specialist

Failure log

All,

I have a reload task that runs every 1 hr from QMC in Qliksense.  In the past 6 hrs or so, the task failed once and remaining were successful.

I can see that only the last 4 logs are saved in the Archived folder. How can I go back further and see for failed log?

Thanks

1 Solution

Accepted Solutions
Bastien_Laugiero

Hi, 

Apologize I completely forgot that setting...

Regarding your last question, when running a task from QMC, the script log is first generated in C:\ProgramData\Qlik\Sense\Log\Script and then moved to the archived logs folder. Sometimes it happens that this operation failed and the script does not get transferred. This is a post reload operation initiated by the scheduler.  

When the reload task is launched from the HUB, then the script is generated in C:\ProgramData\Qlik\Sense\Log\Script and never move to the archived logs folder. I believe the reason is because this file transfer operation is managed by the scheduler and when running reload from the HUB, the scheduler service is not involved. 

 

 

Bastien Laugiero
If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.

View solution in original post

4 Replies
Bastien_Laugiero

Hello!

There are no process in Qlik Sense cleaning up the logs. If you have not implement any cleanup script/program I would suggest to check the places:

  • \\Server\QlikShare\ArchivedLogs\Server\Script 

*Server correspond to any Scheduler nodes in the environment 

  • C:\Programdata\Qlik\Sense\Log\Script (on every Scheduler nodes)

The last think that comes to mind is that there is a difference between a task failing with "Error" and "Failed" Status

The status "Failed" will appear when the reload task failed during the script execution. You will normally, in this case, get a script log.

The status "Error" means that the reload task failed before execution. For example if you have an issue with the scheduler or the engine. In this case you won't get any script logs and probably need to look at the scheduler and engine logs to get more info. 

Hope this helps!

 

Bastien Laugiero
If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.
jpjust
Specialist
Specialist
Author

Thank you Bastien for the comments.

According to the link below, there is an setting to control "MinNumberOfExecutionResultsToKeepPerTask"  avaialble in  Repository.exe.config file.

https://community.qlik.com/t5/Knowledge-Base/Qlik-Sense-Script-logs-are-deleted-from-ArchivedLogs-lo...

Further, what I understood from the link is any task executed from the HUB is kept here 

C:\ProgramData\Qlik\Sense\Log\Script

And any tasks executed from QMC is kept under Archived (4 script logs per task)

 \\SERVICECLUSTER-SHARE\ArchivedLogs\NodeName\Script

One thing still not clear is, does the script log executed from QMC goes to C:\ProgramData\Qlik\Sense\Log\Script and then gets transferred to Archived Log folder? OR script log executed from QMC goes directly to Archived folder. And only script log executed from Hib stays in C:\ProgramData\Qlik\Sense\Log\Script?

Reference Lionk : https://community.qlik.com/t5/Knowledge-Base/Qlik-Sense-Script-Log-Will-Not-Transferred-To-Archived-...

Thanks

 

Bastien_Laugiero

Hi, 

Apologize I completely forgot that setting...

Regarding your last question, when running a task from QMC, the script log is first generated in C:\ProgramData\Qlik\Sense\Log\Script and then moved to the archived logs folder. Sometimes it happens that this operation failed and the script does not get transferred. This is a post reload operation initiated by the scheduler.  

When the reload task is launched from the HUB, then the script is generated in C:\ProgramData\Qlik\Sense\Log\Script and never move to the archived logs folder. I believe the reason is because this file transfer operation is managed by the scheduler and when running reload from the HUB, the scheduler service is not involved. 

 

 

Bastien Laugiero
If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.
jpjust
Specialist
Specialist
Author