[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

I have an application running on port 8080. I want to check if the port is open and the application is successfully…

Read more

When you interrupt yum installation and try to reinstall the package again , you are likely to get a transaction lock.…

Read more

Why should you learn Linux?Linux is an awesome OS to work with. It is very malleable and it is really really fun to…

Read more

Internet is huge! Help us find great content

About

The Best Tutorials & Tips to Speedup Your DevOps Workflow.

Created by Bibin Wilson.