[JENKINS-69185] Jenkins slave goes offline in between the build

[jenkins-infra-bot]

Error when executing always post condition:16:08:48 org.jenkinsci.plugins.workflow.support.steps.AgentOfflineException: Unable to create live FilePath for EC2 (Builder) - UPC Jenkins Builder (i-0ccac0f5671d878e3)

My jenkins slave agent goes offline in between the build and shows above error.

********************
This is all what i tried: we had everything running when we had JDK 8 in both master and slave. So, we added code to have JDK 11 in both and I replaced ec2 of Jenkins with a new one with help of ASG. So, issue came, and we reverted, but still the issue was the same. So, I was just assuming by this warning in jenkins as it says moveto jdk 11,as there anything like deprecated...so, I was just checking also we can try this new version of Jenkins as well, what they have mentioned. -going to Jenkins 2.344 with jdk8 ,same issue, and also to different jenkins version didn't help and I lost hope. I have tried with a biggest ec2 type for slave --didn't help I checked htop in slave --didn't help. I tried restarting jenkins master --didn't help. I tried changing remote dir for slave as mentioned in stack overflow --didn't help. So, I have a thought, as Jenkins ec2 is terminated and new ec2 came up, so, things may get updated in jenkins by that...and also warning showing to have a new version of jenkins and jdk 11..so, that looked somewhat a hope to me. I tried by increasing tomeout 20 min in slave setup, didn't help. I tried adding this command :sudo yum -y update --security in init script of node of jenkins ec2 plgin-will not help. we have tried jdk 11 image, jdk8 image and new jdk8 jenkins version image, issue was same in all.

So, what finally solved the issue: that we moved to older version of jenkins: https://hub.docker.com/layers/jenkins/jenkins/jenkins/2.330-jdk8/images/sha256-97fcb[…]17da34f0d07c021ab57083ee8c77dc4b21281d3498137?context=explore
*******************
So, how can I get this resolved in newer versions, it was 2.334-lts, which we were using with jdk 11 had this issue.
As it is not safe to stick to older versions for long time.

---

Originally reported by rahulkamboj21, imported from: Jenkins slave goes offline in between the build

• assignee: peppe
• status: Open
• priority: Minor
• component(s): slave-setup-plugin
• resolution: Unresolved
• votes: 1
• watchers: 3
• imported: 20251216-225446

Raw content of original issue

Error when executing always post condition:16:08:48  org.jenkinsci.plugins.workflow.support.steps.AgentOfflineException: Unable to create live FilePath for EC2 (Builder) - UPC Jenkins Builder (i-0ccac0f5671d878e3)

My jenkins slave agent goes offline in between the build and shows above error.


********************
This is all what i tried: we had everything running when we had JDK 8 in both master and slave. So, we added code to have JDK 11 in both and I replaced ec2 of Jenkins with a new one with help of ASG. So, issue came, and we reverted, but still the issue was the same. So, I was just assuming by this warning in jenkins as it says moveto jdk 11,as there anything like deprecated...so, I was just checking also we can try this new version of Jenkins as well, what they have mentioned. -going to Jenkins 2.344 with jdk8 ,same issue, and also to different jenkins version didn't help and I lost hope. I have tried with a biggest ec2 type for slave --didn't help I checked htop in slave --didn't help. I tried restarting jenkins master --didn't help. I tried changing remote dir for slave as mentioned in stack overflow --didn't help. So, I have a thought, as Jenkins ec2 is terminated and new ec2 came up, so, things may get updated in jenkins by that...and also warning showing to have a new version of jenkins and jdk 11..so, that looked somewhat a hope to me. I tried by increasing tomeout 20 min in slave setup, didn't help. I tried adding this command :sudo yum -y update --security in init script of node of jenkins ec2 plgin-will not help. we have tried jdk 11 image, jdk8 image and new jdk8 jenkins version image, issue was same in all.

So, what finally solved the issue: that we moved to older version of jenkins: https://hub.docker.com/layers/jenkins/jenkins/jenkins/2.330-jdk8/images/sha256-97fcb[…]17da34f0d07c021ab57083ee8c77dc4b21281d3498137?context=explore
*******************
So, how can I get this resolved in newer versions, it was 2.334-lts, which we were using with jdk 11 had this issue.
As it is not safe to stick to older versions for long time.