"Broken pipe (Write failed)" on uploading some Jenkins jobs

[Snorre Selmer]

I know.. Me again. ;)

When we run some of our Jenkins jobs, they fail on Publish with an error jike this:

* What went wrong:

09:44:22 Execution failed for task ':publishMavenJavaPublicationToMavenRepository'.
09:44:22 > Failed to publish publication 'mavenJava' to repository 'maven'
09:44:22    > Could not write to resource 'https://nexus.domain.somewhere/repository/dev-snapshots/a/b/c/d/e/filename.jar'.
09:44:22       > Broken pipe (Write failed)

 

Is there some form of logging we can turn on to help diagnose this?

I found references to broken pipes when searching, and it said to add certain useragents to a form of exception ("nexus.view.exhaustForAgents=Apache-Maven.*"), but I don't know what agents are being used in these jobs.

Any help is appreciated!

Snorre

[Snorre Selmer]

OK, after a bit of rummaging around, I found the requests.log and got the user-agent (Gradle.*).

Added the user-agent to the exception (ref this article: https://support.sonatype.com/hc/en-us/articles/115009807628-Inspecting-Inbound-Request-Headers-in-Nexus-Repository-Manager), rebooted Nexus, no more broken pipes (got a 401 instead)!

From there we found an issue in our scripts regarding authentication (single- vs double-quotes), so things are now flowing nicely. 

[rajnish...@gmail.com]

Hi,

while uploading file from jenkin to Nexus getting error failed to upload file error broken pipe.

Can you please advise on this. 

[smural...@matterport.com]

Hi Snorre

I have the same problem.

With this:

nexus.view.exhaustForAgents=Apache-Maven.*|Apache Ivy.*|curl.*

AM getting a timeout from curl and 401 from maven.

Any clues?

Thanks

Satya