Hi, what you describe seems something we experienced. The issue in our case was that the Jenkins agents were VMs running on an overloaded host with network issues. A combination of network errors, agents not responding and IP exhaustion made Jenkins terminating the jobs with SIGTERM when it was uncapable to restore connection with the agent. It was hard to find because the host running the VMs was overloaded when the agents were doing something so it was something like: agent was ok -> agent started to build a job -> job was spawning other VMs for testing -> host got overloaded -> agent could run properly -> Jenkins lost connection with agent -> job got terminated -> host not anymore in overload -> agent ok again -> jenkins restored connection with agent.
On Friday, 3 July 2020 08:19:22 UTC+1, fabian wrote: > > Hi > > We've been using Jenkins for years now. Recently a problem has > come up that I can't explain. Jobs started to get terminated with > no apparent reason. With a signal handler I found that it's > apparently the Jenkins user that is sending the SIGTERM to > the running process. > > What are reasons for Jenkins to stop a job? > > There is no second build being started and it's throttled anyway. > The build timeout plugin is installed but this is a pipeline job > where it doesn't work. And I don't use the timeout options in > the pipeline. > I don't see anything in the jenkins log at that time. > > How can I find out why the job is killed? > > Thanks > > bye Fabi > > -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-users/813456d7-1d87-4a40-b954-ddfd6c431c86o%40googlegroups.com.
