QMC Task Error: "No slave scheduler found"

[daniel_dalnekoff]

Hi,

We are getting an error in the QMC when scheduled tasks are starting to queue up (waiting on what is executing to begin).  My timeout is set to 120 minutes, but these are immediately failing with the error above (No slave scheduler found).

We have a single scheduler node configured as Master and Slave, and the engine service is running on this node.  Confirmed QMC shows the service is running (and so does Windows).  Resources on the machine are not maxed out.  I am setup to allow 6 concurrent tasks to run (based on 8 cores).  It seems like as soon as several tasks start to get in the triggered or queued status this happens.

Does anyone have any thoughts on how to troubleshoot?

[plexpro52]

Hello Daniele et al.,

This behavior resurfaced this morning.  After the initial data load took place, of the five chained tasks, two ran, and three failed 11 seconds after being triggered -- all at the same second -- with the message "No slave scheduler found".

I reported this to Analytics8, our level 1 support contact.

René

[Daniele_Purrone]

Hi René,
sorry to read this! I have alerted my colleague in the US that previously worked with Analytics8 on your case, so he's ready for when the partner reaches out to us.

Take care,

Daniele

[plexpro52]

This morning the chained task ran fine.

So, while the modification that we made to the engine's .ini file does not completely resolve all issues, it apparently resolves most of what we experience, or at least mitigates it enough for the job usually not to fail.  One failure every two weeks is not too bad for some purposes.  However, still too much for others.

René

[tguaglia]

Hi Daniele,

I wanted to let you know that I put in a request to reopen the original case that references the issue reported by Rene Valencourt.

Thanks.

Tom Guagliardo

[Felipe_Violin]

Good Morning,

I have the same problem on my server.

Is there a definitive solution to this problem?

I'm waiting

Thank you

[peter_turner]

Hi Felipe,

No solution yet as far as i know.

I have also encountered this on another system, this time a new multinode installation.

Awaiting feedback from Qlik support.

[BeeGees]

@Daniele_Purrone

So, couple of weeks passed. Any news regarding?

[Daniele_Purrone]

Hi @BeeGees.
I'm afraid the problem investigation is still ongoing at R&D. Do you happen to have a support case open? If not, please open one (either with us if entitled, or with the responsible partner if you have one). The more data we can gather, the better it is.

[BeeGees]

Sorry to say so, but i guess i do not have time to babysit Qlik support anymore. Supports in general its just huge waste of my time. I can provide You some logs if You want tho.

[erprodsupport]

I have been experiencing this same issue on our production environment for the past few weeks.  It looks as if the scheduler service crashes and then immediately restarts.  While we can then restart the failed tasks, I've noticed that some of them will fail automatically again.  Our quick solution to this is to manually restart the Qlik Sense Scheduler Service, after which all failed tasks run fine.

I don't have any more details other than this as the server logs proved to be unhelpful in finding the cause of this.  I do think this issue is probably due to having a large number of tasks either running or in a pending status waiting to run.  Hopefully there's a fix incoming in a patch......