Hi Daniel, I have had a similar issue some weeks ago. The jobs tied to a specific got stuck for infinite time but the node was available. Also the configuration was fine. Actually did nothing change. I have been researching and troubleshooting quite a while and learned that deleting and recreating the node did solve the problem permanently. Another solution - if you're using windows - might be to empty the lists in the event viewer. Jenkins gets stuck if one of these lists are full. Depending on the list will the service start and instantly stop as it can't write to the system log and same is(/was) with the application log when you want to build nothing happens.
Might be worth a try for you. Take care Jan On Mar 20, 12:55 pm, Daniel Tkatch <daniel.tka...@smeet.com> wrote: > Now the stuck job got released when I deleted a job that was after it > in the queue. The jobs seem to get stuck in packs, never alone. > > On Mar 20, 12:45 pm, Daniel Tkatch <daniel.tka...@smeet.com> wrote: > > > > > > > > > Recently, I am experiencing a weird issue. > > > I have a job whose execution is restricted to a specific node. This > > job keeps waiting in the queue even though the node became active. It > > seems to be stuck in the queue for a while (several minutes) and gets > > released after some time. Hmm.. > > > Any idea what could be causing this? Where should I start looking?
