[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Nathan Neulinger commented on JENKINS-59169 Re: JNLP4 Connect Error - Connection closed before acknowledgement sent I realize this has already been closed - but just had to go through a big diag effort on my site with a bunch of windows JNLP agents that stopped working sometime in past few days. After a long set of rabbit trails - what I found in my case – the problem wound up being reverse DNS resolution stopped working (unrelated local problem – "It's always DNS", right?) - but that inability to reverse resolve the connecting client (windows box) was causing the JNLP server side to drop the connection. Just wanted to add this here in case it helps anyone else with future similar issues if it happens to be related. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201606.1567306209000.11610.1575418440300%40Atlassian.JIRA.
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Pedro Salomao resolved as Not A Defect Jenkins / JENKINS-59169 JNLP4 Connect Error - Connection closed before acknowledgement sent Change By: Pedro Salomao Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201606.1567306209000.6819.1567629360122%40Atlassian.JIRA.
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Pedro Salomao updated an issue Jenkins / JENKINS-59169 JNLP4 Connect Error - Connection closed before acknowledgement sent Solution to this problem: tunnel through the ELB as to get slave/master connected. How to do this? Go to Jenkins Master → Nodes → → Advanced → Tunnel: ernal-aef67c013ca2d11e9b6ab02485d01370-111334679.us-west-1.elb.amazonaws.com:5 (Above takes for granted that security group/inbound has also been properly configured) This assumes that you have already configured agent port static to 5 - how? Jenkins -> global security -> Agents -> TCP port for inbound agents -> Fixed: 5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201606.1567306209000.6818.1567629180065%40Atlassian.JIRA.
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Pedro Salomao updated an issue Jenkins / JENKINS-59169 JNLP4 Connect Error - Connection closed before acknowledgement sent Change By: Pedro Salomao Component/s: remoting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201606.1567306209000.6743.1567617960071%40Atlassian.JIRA.
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Pedro Salomao updated an issue Jenkins / JENKINS-59169 JNLP4 Connect Error - Connection closed before acknowledgement sent Change By: Pedro Salomao Component/s: core Component/s: oauth-credentials-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201606.1567306209000.6742.1567617780088%40Atlassian.JIRA.
[JIRA] (JENKINS-59169) JNLP4 Connect Error - Connection closed before acknowledgement sent
Title: Message Title Pedro Salomao created an issue Jenkins / JENKINS-59169 JNLP4 Connect Error - Connection closed before acknowledgement sent Issue Type: Bug Assignee: Unassigned Components: oauth-credentials-plugin Created: 2019-09-01 02:50 Environment: Agent: OSX Mojave 10.14.5 Jenkins: Linux (Jenkins LTS 2.176.3) Java on agent: OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_212-b03) OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.212-b03, mixed mode) Java on master: java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_222-b10 java.version 1.8.0_222 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM Priority: Blocker Reporter: Pedro Salomao This seems very similar to a recently closed #57143. We have spent quite a bit of time troubleshooting it though not able to find the root case. We had nginx and replace that by elb and both cases leads to same problem below. Please let me know what additional logs/info are needed and will provide. Any help/support/guidance is appreciated. netcat from slave towards master. $ nc -z jenkins.infrastructure.X.care 5 Connection to jenkins.infrastructure.X.care port 5 [tcp/*] succeeded! #ELB kubectl -n infrastructure get svc infrastructure-nginx-ingress-internal-controller LoadBalancer 100.66.210.45 internal-ab39ee254472111e9aa5b0a4f0f93d47-951468028.us-east-1.elb.amazonaws.com 80:30664/TCP,443:30937/TCP,5:32123/TCP 166d Logs
