PR build crashed with error message "The channel is closing down or has closed down"

[Mads Mohr Christensen]

I've opened a PR which just includes a better error message.

The build completed very fast for Linux JDK 8+11 but for Windows it looks like the build has crashed. 

Error message:

Cannot contact EC2 (aws) - Windows 2019 (i-003aa1d3772d37d10): hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@2f7406ec:EC2 (aws) - Windows 2019 (i-003aa1d3772d37d10)": Remote call on EC2 (aws) - Windows 2019 (i-003aa1d3772d37d10) failed. The channel is closing down or has closed down

https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadoptopenjdk-plugin/detail/PR-12/1/pipeline/24/

Is there a way to cancel a running job and to start it again?

[Gavin Mogan]

Easiest way as a non admin:

Close the PR, wait a couple seconds, and reopen it.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALWGXhdA_t4SeTbXWW-8YaoyhZofHj_qsCnJwuyQJwP1AG5rZw%40mail.gmail.com.

[Mads Mohr Christensen]

Thanks Gavin, great tip!

Unfortunately it failed again with the same error message:

https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadoptopenjdk-plugin/detail/PR-12/2/pipeline/68

At time of writing this mail the job is still running but it will most likely timeout in an hour.

I can't remember seeing this error before and I really don't know how to deal with it. Does anyone have a tip on how I can debug this?

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duv%3DNYLpkfU9Nw5b%2BV6TfbbDWkCOmxtHZqJmU1KUBZXoiA%40mail.gmail.com.

[Mark Waite]

Unfortunately, there is not much that you can do to diagnose the issue.  There is some issue that causes the agents on AWS EC2 to be disconnected from the master on Azure.  We don't know if the issue is in the EC2 plugin, the communications between the Azure Jenkins master and AWS EC2 agent, the remoting code that carries the data, or something completely outside those items.

I've started a new copy of the job in hopes the connection between agent and master will last long enough to complete the job.

Mark Waite

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALWGXhfqWQO_wg-6sh8DJhsJBXPJ5biwiScdrEcZNH%3DOBqkRTA%40mail.gmail.com.

[Steve Carter]

I've experienced this error in my corporate network where the agent was just so busy with the Jenkins job that it didn't respond to monitoring and monitoring rebooted the machine. I don't know aws, but if it's easy to check it could be worth ruling out

[Mark Waite]

Thanks for the suggestion.  One of the ways that we reduced the impact of the disconnects was by clicking the "Relaunch agent" button every few minutes for agents that are disconnected.  We implemented that after observing that many times the agent will reconnect when the relaunch agent button is clicked by an administrator.  We can certainly double check that there is no async reboot of the agent, but I don't expect there to be one.

On Sat, Aug 8, 2020 at 5:28 AM Steve Carter <swe...@gmail.com> wrote:

I've experienced this error in my corporate network where the agent was just so busy with the Jenkins job that it didn't respond to monitoring and monitoring rebooted the machine. I don't know aws, but if it's easy to check it could be worth ruling out

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d2abc458-42a7-4e76-b919-04222bf49cc8o%40googlegroups.com.