-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error starting build pod java.io.IOException: Pipe not connected #206
Comments
this is a dump of the recent jenkins server logs
|
@iocanel I don't suppose this means anything to you does it? We've started running lots of PR builds and we can have 5 running concurrently on a three node GKE cluster, which has plenty of space resources. Roughly every 12 hours we start seeing these errors and I can only bounce the jenkins master to recover. Any clues how to investigate what's going on? |
Interesting comment from
|
I faced this issue on AWS also. |
@vikasjio could you elaborate? How are your resources set now to resolve the issue? |
Hi, For me, things were working initially; but started failing once I increased loads/applications in my cluster. So, I just added 2 more VMs in my cluster, which already had 4 worker VMs of the same size.
From: tettaji [mailto:notifications@github.com]
Sent: 25 July 2017 16:17
To: fabric8io/fabric8-pipeline-library
Cc: Vikas Chander; Mention
Subject: Re: [fabric8io/fabric8-pipeline-library] error starting build pod java.io.IOException: Pipe not connected (#206)
@vikasjio<https://github.com/vikasjio> could you elaborate? How are your resources set now to resolve the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#206 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AURkBK8Ht_1GM4eVykNXtxmKLBQwHBHwks5sRceYgaJpZM4NAcbE>.
"Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s).
are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any
review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is
strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email.
and delete this message and any attachments from your system.
Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email.
The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."
|
This is fixed in the kubernetes-plugin jenkinsci/kubernetes-plugin#182, just need to release a new Jenkins image with the fix included and update the pipeline library to work with 0.13-SNAPSHOT as there seems to be some breaking change with the way env vars are added to pods. I will hopefully have this done in the next day or two. |
@rawlingsj is this fixed in the newest release ? just experienced it on my setup:
|
@marvinosswald I'm not involved in the fabric8 project anymore I'm afraid so not sure where things are. From memory however I think the latest kubernetes-plugin did include a number if fixes to avoid this so I think it should be fixed. |
Seems to happen when there's low resources or multiple jobs running. This has been seen on OSO and GKE.
The text was updated successfully, but these errors were encountered: