"pending - waiting for next executor" message occurs while executing the job in Jenkins

17 views
Skip to first unread message

Poonkuzhali Muthiah

unread,
Oct 19, 2021, 6:45:17 AM10/19/21
to jenkins...@googlegroups.com
Hi,

I am unable to execute any jobs in Jenkins.When I run the job,I am getting the following error message 
"pending - waiting for next executor".How can I solve this issue.


Thanks,
Poo

selva vignesh

unread,
Oct 19, 2021, 6:52:18 AM10/19/21
to jenkins...@googlegroups.com
Hi,
All executors are running other Jobs. So, you are getting this error. Once,  any one of the executors gets available, it will take care your Queued job 
Or, increase the executors count in Manage Jenkins -> Configure System 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAJ5r41VdF3NeWkSanqewTzmfT8RZUVJYr0PO%3DE5Ni6Hvp6PDLA%40mail.gmail.com.

Dirk Heinrichs

unread,
Oct 19, 2021, 6:58:17 AM10/19/21
to jenkins...@googlegroups.com
Am Dienstag, dem 19.10.2021 um 16:21 +0530 schrieb selva vignesh:

So, you are getting this error.

No, this is not an error, just an informative message.

Bye...

Dirk
-- 
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.
signature.asc

Björn Pedersen

unread,
Oct 19, 2021, 7:55:05 AM10/19/21
to Jenkins Users
Some more reason why you could get this message:

 - no executors with the requested label up and running
 - on-demand executors not starting or with a long delay or only scheduled for e.g. out-of-office times

So check the job which executor it expects and then compare this to the available ones.
 

Thanks,
Poo

Poonkuzhali Muthiah

unread,
Oct 19, 2021, 2:14:52 PM10/19/21
to jenkins...@googlegroups.com
I have no jobs available in the queue.I increased the executor counter,still got the same message.

Thanks,
Poo

Björn Pedersen

unread,
Oct 20, 2021, 4:27:08 AM10/20/21
to Jenkins Users
kuzh...@gmail.com schrieb am Dienstag, 19. Oktober 2021 um 20:14:52 UTC+2:
I have no jobs available in the queue.I increased the executor counter,still got the same message.


Hard to tell without more information...
 * what kind of job:  pipeline , freestyle, ???
 * configured labels for nodes
* if pipeline: the pipeline code
 * ....

Poonkuzhali Muthiah

unread,
Oct 20, 2021, 10:26:15 AM10/20/21
to jenkins...@googlegroups.com
It's a freestyle job.This job is to connect to  Virtual machine over ssh.It was working fine.I am getting this response since yesterday . whenever I try to run any job,it says build is in queue. Attached the screenshot for reference.

Thanks,
Poo


IMG_20211020_194645~2.jpg

Dirk Heinrichs

unread,
Oct 21, 2021, 2:43:36 AM10/21/21
to jenkins...@googlegroups.com
Am Mittwoch, dem 20.10.2021 um 19:56 +0530 schrieb Poonkuzhali Muthiah:

It's a freestyle job.This job is to connect to  Virtual machine over ssh.It was working fine.I am getting this response since yesterday . whenever I try to run any job,it says build is in queue. Attached the screenshot for reference.

I only see one node there, I guess that's master. Is the VM you mentioned considered to be always up or is it started on demand? If the first, then it should likely also show up with its executors below your master executors. So you should check why that VM isn't running (or isn't started if should be starting on demand). Also check the configuration of your job as to whether the "Restrict where this job can be run" setting matches the name/label of your VM and fix it if needed.

HTH...
signature.asc
Reply all
Reply to author
Forward
0 new messages