Task has not started

[keyframe]

I'm hoping that i'm missing something obvious so please don't hesitate to point and laugh at me.

I submitted a job which simply sits there saying: ERROR: Task is not started.
The hostmask seems legit, the capacity seems fine, the service is available on the targeted nodes, but for some reason it's not being dispatched.

Is there anywhere else I might look for a clue as to why it's not dispatching?

G

[timurhai]

Hi.

It can be also stopped when:
- zero max run tasks, max run tasks per host, priority
- hosts can be NIMBY/Paused, has zero max tasks, priority
And same parameters for a job user.

If you are using a new pre-release version with branches, you should also check job branch parameters.

You should always specify version and OS.
You can write in your signature.

[keyframe]

Thanks Timur.

Sadly, it appears that all the suggested parameters are set as expected. Other jobs submitted from the same DCC are running -- but one will not. Must be a ghost in the machine -- or I pushed some bullshit code to the floor

Thanks for following up. I'll post if I ever get to the bottom of this.

G

ps: added sig as per your suggestion.

[timurhai]

Hi.
If some is running and some one does not, try to find the difference between them.

Sure, please post if you will find the reason.

[giel_4321]

you probably might have found the solution already for this. But I was having the same issue while updating cgru.As for future reference I am adding my solution. I found that services was having conflict while submitting the job. Removing services from af.block will take the generic service and will start the task.

if it was something like

block = af.block('Name of the job', 'some Service')

It should be:
block = af.block('Name of the job')

Timur Knows the best, but just adding what I found helpful.

[Khiladi]

Thanks!!!

Man your'e on fire