Tasks fail to reload on rim node in cluster environments in Qlik Sense Enterprise
Article Number: 000033022 | Last Modified: 2018/06/12
The Issue can look like the one described below:
"We got a grant new environment Qlik Sense ver. 3.2 with 3 nodes installed on fresh Windows systems in Shared Persistence mode. Everything works fine so far, but Tasks fail to reload on QSReload rim node. We've checked the whole configuration I can't find any reason of these failures. The only thing I found is that scheduler log on rim node says: "App not found". Central node: QS Services: Repository, Engine, Printing, Proxy, Scheduler Scheduler Type: Master Rim node: QSReload Services: Repository, Engine, Scheduler Scheduler Type: Slave Service user on both servers is the same domain user (sense_system), added to local Administrators group. Firewall is now disabled on both servers. Load balancer on both servers have the same values: Central, Reload. I put both servers on White list. Root folder for Shared Persistence is hosted on a dedicated File Server and is accessible from both servers using service user (sense_system)."
When starting the services engine chooses default app folders and if the apps inside them happen to have connections to local resources that are not shared the reload tasks administered from the Central node will fail as the central node does not have access to the local paths.
1. Bug: QLIK-73792 - Engine picks default Apps folder instead of shared location if engine service starts before repository is running. Fixed in the upcoming Sense 4.0 release.
2. Check how the reload and the reloaded application is developed and set up. If you are reloading an application through a task on the rimnode that points to a local path on the central node then it will not run unless that folder on the central node is shared. Local paths are always for the specific machine. You can change the local path in the application or , you can create a reload task on the central node that will reload the application on the rim node that has a connection to a folder on the central node.