Job are still running, however the on demand docker cloud agents are
terminated. I posted the error, which I received as job aborted due to
agent disconnected in the middle.



On Wed, 5 Mar, 2025, 4:48 pm 'Björn Pedersen' via Jenkins Users, <
jenkinsci-users@googlegroups.com> wrote:

>
>
> ravibabys...@gmail.com schrieb am Mittwoch, 5. März 2025 um 11:59:16
> UTC+1:
>
> Hi all,
>
> We have upgraded our Jenkins instance and installed all the required
> plugins, including the Docker plugin.
>
> After setting up Docker Cloud and configuring the template, we observed
> that new agents created from the Docker plugin are getting terminated after
> running for *20-25 minutes*.
>
> We would appreciate any help in resolving this issue.
>
> *Error details:*
>
> Also: hudson.model.Computer$TerminationRequest: Termination requested at
> Wed Mar 05 04:28:03 IST 2025 by Thread[DockerContainerWatchdog Asynchronous
> Periodic Work thread,5,main] [id=31721] at
> hudson.model.Computer.recordTermination(Computer.java:242) at
> jenkins.model.Nodes$5.run(Nodes.java:283) at
> hudson.model.Queue._withLock(Queue.java:1409) at
> hudson.model.Queue.withLock(Queue.java:1283) at
> jenkins.model.Nodes.removeNode(Nodes.java:278) at
> jenkins.model.Jenkins.removeNode(Jenkins.java:2257) at PluginClassLoader
> for
> docker-plugin//com.nirima.jenkins.plugins.docker.DockerContainerWatchdog.removeNode(DockerContainerWatchdog.java:97)
> at PluginClassLoader for
> docker-plugin//com.nirima.jenkins.plugins.docker.DockerContainerWatchdog.cleanUpSuperfluousComputer(DockerContainerWatchdog.java:564)
> at PluginClassLoader for
> docker-plugin//com.nirima.jenkins.plugins.docker.DockerContainerWatchdog.execute(DockerContainerWatchdog.java:158)
> at
> hudson.model.AsyncPeriodicWork.lambda$doRun$0(AsyncPeriodicWork.java:102)
> Also: hudson.model.Computer$TerminationRequest: Termination requested at
> Wed Mar 05 04:28:03 IST 2025 by Thread[DockerContainerWatchdog Asynchronous
> Periodic Work thread,5,main] [id=31721] at
> hudson.model.Computer.recordTermination(Computer.java:242) at
> hudson.model.Computer.disconnect(Computer.java:512) at
> hudson.slaves.SlaveComputer.disconnect(SlaveComputer.java:816) at
> jenkins.model.Nodes$5.run(Nodes.java:284) at
> hudson.model.Queue._withLock(Queue.java:1409) at
> hudson.model.Queue.withLock(Queue.java:1283) at
> jenkins.model.Nodes.removeNode(Nodes.java:278) at
> jenkins.model.Jenkins.removeNode(Jenkins.java:2257) at PluginClassLoader
> for
> docker-plugin//com.nirima.jenkins.plugins.docker.DockerContainerWatchdog.removeNode(DockerContainerWatchdog.java:97)
> at PluginClassLoader for
> docker-plugin//com.nirima.jenkins.plugins.docker.DockerContainerWatchdog.cleanUpSuperfluousComputer(DockerContainerWatchdog.java:564)
> at PluginClassLoader for
> docker-plugin//com.nirima.jenkins.plugins.docker.DockerContainerWatchdog.execute(DockerContainerWatchdog.java:158)
> at hudson.model.AsyncPeriodicWork.lambda$doRun$0(AsyncPeriodicWork.java:102)
>
>
>
>
> This normal behaviour, the docker agents are on-demand and if not used for
> some time, they get cleaned up.  They should spin up again if a job request
> them.
>
>
>
>
>
> Any insights or suggestions would be highly appreciated.
>
> --
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/jenkinsci-users/c28ec06b-fece-4fa4-a860-137f8d0d8908n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/c28ec06b-fece-4fa4-a860-137f8d0d8908n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAGLba%3DRHrS4OCUgh41G_ntpW_o%2Bi%2BjU6t9zoL_gKo8bKRYO5Mw%40mail.gmail.com.

Reply via email to