I just wanted to add my findings in case somebody else is looking for a
solution to a similar problem.
It turned out that we have a second jenkins job running on the same
machine, mostly unrelated to
the first job that was getting killed. The second job wants to start a
process which can only w
Thanks for the hint. That's sure something we can look into. I would have
guessed
that a lost connection would show up in the system log but it might not. At
least
I can try to improve the situation now.
Thanks again
On Friday, July 3, 2020 at 9:51:23 AM UTC+2, Gianluca wrote:
>
> Hi,
> what yo
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 u
