Back with an update. Had a discussion with Qlik on the issue I reported to get better understanding.
As per Qlik, we can go ahead and disable the Qlik Engine Service over Proxy node if that is creating an issue and not starting up on it's own.
If the service is disabled in the QMC, the Central Node Repository Service understands this service is not needed and will not be contacted. Otherwise we would see other issues in the QMC like the node still showing 5 of 5 services running when Engine or another service is disabled. That is not the case here.
There is no requirement for all services to run on a Rim node, if not all services are selected in QMC. Furthermore, in previous versions you would choose the type of Rim that you wish to install and some of the services would be left out and never installed to begin with. This installer model has changed, yet the requirement for services to run remains the same: only if enabled in the QMC, this governs all Central Node communication patters with the Rim nodes.
Nevertheless, since this change was not known nor documented in the Release Notes, Support Team has raised the issue with R&D under ID QB-2562 and they will get back to us once they have some feedback on this report.
But in the meantime, rest assured there is no impact to environment if this service is not running.
We upgraded from April-2020 SR3 to Sept-2020 SR2 tonight, and this immediately started happening.
My initial thought is that this is NOT required to run unless otherwise specified in the QMC that the Proxy should act as an Engine, however it makes me a little uneasy as this service has always ran in the past.
Qlik Sense Proxy Service service won't start Old topic, the solution given was to increase the time-out windows assigned to start a service from 30 seconds to 2 minutes. If you review the Events log the messages could lead you into this solution.
Thanks much for your detailed analysis and suggestions as always. 🙂
All looks good from port and Platform perspective, did a quick check. Also, we have not done any recent changes on Platform except Upgrade to Sept 2020.
To start the service, as a workaround, I enable the engine under proxy node and then start the service over server. Once service is running fine, I disable the engine under proxy again ( not sure if we keep it enable, will there be any issues ?) Also, I remember it never happened with any release earlier though, but happening now every time server reboot is happening.
As per my understanding, Engine should not run over Proxy node, but since this issue never happened earlier, a bit stuck at this point.
Also, as per the article did a quick check on the setting we have currently-
Thanks for sharing the article. I did checked the current setting over our Proxy server and found as below-
Just wanted to check if you had faced the same issue in Sept 2020 Qlik Release and this setting change has fixed the issue? I cannot test this over any test server and need to directly implement it in production, if this is the fix. Before doing that, wanna make sure no adverse impact of it.