[solved] Jenkins Intermittent “Slave went offline during the build”

Issue: I have my Jenkins master and slave setup on AWS instance. I am build i have a maven deploy task to upload a large artifact to nexus. During which the upload is getting timed out and i am getting “Slave went offline during the build” error. How do i solve this issue.

This issue is normally caused by kernel bug in you slave instances. There are many cases in ec2 instances like this. There could be other reasons as well. Here we will discussing a kernel issue that causes this problem.

The Problem

Normally this issue is caused when the TX (packets going outside) are dropped.

Run the following command on the slave machine.

If you get the following output, you can confirm that it’s a kernel bug.

The Solution

You can solve this issue by dropping all the packet segmentation. Execute the following command on your slave machine

The above command should solve the issue. Let us know in the comment section, if your issue has been solved or if there is some other solution to it. Your feedback might help others.

Related

Before understanding what hardlinks and softlinks are, you must have an idea about innodes in Linux Innode is related…

Read more
git ssh authentication

I want to setup ssh authentication keys for my GitHub and Bitbucket account. So that I can commit to those repositories…

  • GIT+1 more
  • 227
Read more

If you are running mission critical applications on servers, it is important to monitor and notify the administrators…

Read more
About

The Best Tutorials & Tips to Speedup Your DevOps Workflow.

Created by Bibin Wilson.