master to agent connection keeps breaking every 3-4 hours

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

master to agent connection keeps breaking every 3-4 hours

Ashish Sharma-2

Hi Team, We are using JNLP to connect Mac agent to Linux master node.

Jenkins agent keeps disconnecting frequently, and we are getting below logs in master.

Can you please suggest how to resolve this? What are the steps to further triage the same.

Some of the questions we are trying to answer is:

  • What is EOFException?
  • Why does agent tries to connect to master when its already connected?
  • Why does eventually the ping / connection fails? 

We keep seeing this pattern in logs too often and too frequently. Any help would be appreciated.

Results are same even if we try any of the below options:

  • Connected using Launch agent from Browser
  • Connected by starting automator in Mac which runs shell/zsh to run agent.jar
  • Connected by running plist in Mac

 Jenkins environment:

  • Jenkins: 2.249.1
  • Master Node: Linux RHEL 8.1
  • Master Java Version: 1.8.0_242
  • Slave System: macOS Catalina, Version 10.15.6
  • Slave Java Version: 1.8.0_261
Connection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:21 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler run Accepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57215 Sep 29, 2020 2:45:21 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer on Recv[JNLP4-connect connection from x.x.x.x/x.x.x.x:57215] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:31 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler runConnection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:31 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler runAccepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57218 Sep 29, 2020 2:45:32 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv[JNLP4-connect connection from x.x.x.x/x.x.x.x] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:32 AM INFO hudson.slaves.ChannelPinger$1 onDeadPing failed. Terminating the channel JNLP4-connect connection from x.x.x.x/x.x.x.x:57015. java.util.concurrent.TimeoutException: Ping started at 1601318492966 hasn't completed by 1601318732966        at hudson.remoting.PingThread.ping(PingThread.java:134)        at hudson.remoting.PingThread.run(PingThread.java:90)

 

TIA

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6be77200-35d8-42a3-91ff-cf1e3df208aan%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: master to agent connection keeps breaking every 3-4 hours

jeremy mordkoff
We have a similar issue that only seems to occur during long running jobs (over 5 hours). The traceback is different but we also see the EOF exception. My client is Ubuntu linux 

I tried to trace the issue by running tcpdumps at both ends on the ssh session from the master to the slave but I saw nothing amiss. I suspect that there is a connection inside the ssh session but that will be hard to catch using tcpdump. 

I wonder if I need to enable some kind of keep alives.....


On Tuesday, September 29, 2020 at 4:47:22 AM UTC-4 [hidden email] wrote:

Hi Team, We are using JNLP to connect Mac agent to Linux master node.

Jenkins agent keeps disconnecting frequently, and we are getting below logs in master.

Can you please suggest how to resolve this? What are the steps to further triage the same.

Some of the questions we are trying to answer is:

  • What is EOFException?
  • Why does agent tries to connect to master when its already connected?
  • Why does eventually the ping / connection fails? 

We keep seeing this pattern in logs too often and too frequently. Any help would be appreciated.

Results are same even if we try any of the below options:

  • Connected using Launch agent from Browser
  • Connected by starting automator in Mac which runs shell/zsh to run agent.jar
  • Connected by running plist in Mac

 Jenkins environment:

  • Jenkins: 2.249.1
  • Master Node: Linux RHEL 8.1
  • Master Java Version: 1.8.0_242
  • Slave System: macOS Catalina, Version 10.15.6
  • Slave Java Version: 1.8.0_261
Connection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:21 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler run Accepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57215 Sep 29, 2020 2:45:21 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer on Recv[JNLP4-connect connection from x.x.x.x/x.x.x.x:57215] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:31 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler runConnection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:31 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler runAccepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57218 Sep 29, 2020 2:45:32 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv[JNLP4-connect connection from x.x.x.x/x.x.x.x] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:32 AM INFO hudson.slaves.ChannelPinger$1 onDeadPing failed. Terminating the channel JNLP4-connect connection from x.x.x.x/x.x.x.x:57015. java.util.concurrent.TimeoutException: Ping started at 1601318492966 hasn't completed by 1601318732966        at hudson.remoting.PingThread.ping(PingThread.java:134)        at hudson.remoting.PingThread.run(PingThread.java:90)

 

TIA

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2eeea79b-b0bb-40cb-9181-94ca2361182bn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: master to agent connection keeps breaking every 3-4 hours

kuisathaverat
In reply to this post by Ashish Sharma-2
  • Why does agent tries to connect to master when its already connected?
That suggests half-closed connections, it means that the agent loses the connection with the Jenkins instance but the FIN notification never arrived to the Jenkins instance so the connection is open in the Jenkins instance side. It could be related to networks equipment and the policies that have for open connections, the recommendation is to tune the TCP stack to keep those connections open with traffic see https://support.cloudbees.com/hc/en-us/articles/115001416548#7tcpretransmissiontimeoutossperhapsincrease

El martes, 29 de septiembre de 2020 a las 10:47:22 UTC+2, [hidden email] escribió:

Hi Team, We are using JNLP to connect Mac agent to Linux master node.

Jenkins agent keeps disconnecting frequently, and we are getting below logs in master.

Can you please suggest how to resolve this? What are the steps to further triage the same.

Some of the questions we are trying to answer is:

  • What is EOFException?
  • Why does agent tries to connect to master when its already connected?
  • Why does eventually the ping / connection fails? 

We keep seeing this pattern in logs too often and too frequently. Any help would be appreciated.

Results are same even if we try any of the below options:

  • Connected using Launch agent from Browser
  • Connected by starting automator in Mac which runs shell/zsh to run agent.jar
  • Connected by running plist in Mac

 Jenkins environment:

  • Jenkins: 2.249.1
  • Master Node: Linux RHEL 8.1
  • Master Java Version: 1.8.0_242
  • Slave System: macOS Catalina, Version 10.15.6
  • Slave Java Version: 1.8.0_261
Connection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:21 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler run Accepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57215 Sep 29, 2020 2:45:21 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer on Recv[JNLP4-connect connection from x.x.x.x/x.x.x.x:57215] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:31 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler runConnection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:31 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler runAccepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57218 Sep 29, 2020 2:45:32 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv[JNLP4-connect connection from x.x.x.x/x.x.x.x] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:32 AM INFO hudson.slaves.ChannelPinger$1 onDeadPing failed. Terminating the channel JNLP4-connect connection from x.x.x.x/x.x.x.x:57015. java.util.concurrent.TimeoutException: Ping started at 1601318492966 hasn't completed by 1601318732966        at hudson.remoting.PingThread.ping(PingThread.java:134)        at hudson.remoting.PingThread.run(PingThread.java:90)

 

TIA

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1e7bdce3-dbb1-47c8-9d2a-0257496388een%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: master to agent connection keeps breaking every 3-4 hours

Ashish Sharma-2
Thanks, are these setting to be applied on master side or slave or both?

On Wednesday, September 30, 2020 at 12:15:23 AM UTC+8 [hidden email] wrote:
  • Why does agent tries to connect to master when its already connected?
That suggests half-closed connections, it means that the agent loses the connection with the Jenkins instance but the FIN notification never arrived to the Jenkins instance so the connection is open in the Jenkins instance side. It could be related to networks equipment and the policies that have for open connections, the recommendation is to tune the TCP stack to keep those connections open with traffic see https://support.cloudbees.com/hc/en-us/articles/115001416548#7tcpretransmissiontimeoutossperhapsincrease

El martes, 29 de septiembre de 2020 a las 10:47:22 UTC+2, [hidden email] escribió:

Hi Team, We are using JNLP to connect Mac agent to Linux master node.

Jenkins agent keeps disconnecting frequently, and we are getting below logs in master.

Can you please suggest how to resolve this? What are the steps to further triage the same.

Some of the questions we are trying to answer is:

  • What is EOFException?
  • Why does agent tries to connect to master when its already connected?
  • Why does eventually the ping / connection fails? 

We keep seeing this pattern in logs too often and too frequently. Any help would be appreciated.

Results are same even if we try any of the below options:

  • Connected using Launch agent from Browser
  • Connected by starting automator in Mac which runs shell/zsh to run agent.jar
  • Connected by running plist in Mac

 Jenkins environment:

  • Jenkins: 2.249.1
  • Master Node: Linux RHEL 8.1
  • Master Java Version: 1.8.0_242
  • Slave System: macOS Catalina, Version 10.15.6
  • Slave Java Version: 1.8.0_261
Connection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:21 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler run Accepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57215 Sep 29, 2020 2:45:21 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer on Recv[JNLP4-connect connection from x.x.x.x/x.x.x.x:57215] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:31 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler runConnection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:31 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler runAccepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57218 Sep 29, 2020 2:45:32 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv[JNLP4-connect connection from x.x.x.x/x.x.x.x] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:32 AM INFO hudson.slaves.ChannelPinger$1 onDeadPing failed. Terminating the channel JNLP4-connect connection from x.x.x.x/x.x.x.x:57015. java.util.concurrent.TimeoutException: Ping started at 1601318492966 hasn't completed by 1601318732966        at hudson.remoting.PingThread.ping(PingThread.java:134)        at hudson.remoting.PingThread.run(PingThread.java:90)

 

TIA

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f81d4870-df94-4bb9-8087-e882ad27a6fcn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: master to agent connection keeps breaking every 3-4 hours

kuisathaverat
ideally, on both sides, make it on one side usually is enough.

El miércoles, 30 de septiembre de 2020 a las 3:22:00 UTC+2, [hidden email] escribió:
Thanks, are these setting to be applied on master side or slave or both?

On Wednesday, September 30, 2020 at 12:15:23 AM UTC+8 [hidden email] wrote:
  • Why does agent tries to connect to master when its already connected?
That suggests half-closed connections, it means that the agent loses the connection with the Jenkins instance but the FIN notification never arrived to the Jenkins instance so the connection is open in the Jenkins instance side. It could be related to networks equipment and the policies that have for open connections, the recommendation is to tune the TCP stack to keep those connections open with traffic see https://support.cloudbees.com/hc/en-us/articles/115001416548#7tcpretransmissiontimeoutossperhapsincrease

El martes, 29 de septiembre de 2020 a las 10:47:22 UTC+2, [hidden email] escribió:

Hi Team, We are using JNLP to connect Mac agent to Linux master node.

Jenkins agent keeps disconnecting frequently, and we are getting below logs in master.

Can you please suggest how to resolve this? What are the steps to further triage the same.

Some of the questions we are trying to answer is:

  • What is EOFException?
  • Why does agent tries to connect to master when its already connected?
  • Why does eventually the ping / connection fails? 

We keep seeing this pattern in logs too often and too frequently. Any help would be appreciated.

Results are same even if we try any of the below options:

  • Connected using Launch agent from Browser
  • Connected by starting automator in Mac which runs shell/zsh to run agent.jar
  • Connected by running plist in Mac

 Jenkins environment:

  • Jenkins: 2.249.1
  • Master Node: Linux RHEL 8.1
  • Master Java Version: 1.8.0_242
  • Slave System: macOS Catalina, Version 10.15.6
  • Slave Java Version: 1.8.0_261
Connection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:21 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler run Accepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57215 Sep 29, 2020 2:45:21 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer on Recv[JNLP4-connect connection from x.x.x.x/x.x.x.x:57215] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:31 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler runConnection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:31 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler runAccepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57218 Sep 29, 2020 2:45:32 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv[JNLP4-connect connection from x.x.x.x/x.x.x.x] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:32 AM INFO hudson.slaves.ChannelPinger$1 onDeadPing failed. Terminating the channel JNLP4-connect connection from x.x.x.x/x.x.x.x:57015. java.util.concurrent.TimeoutException: Ping started at 1601318492966 hasn't completed by 1601318732966        at hudson.remoting.PingThread.ping(PingThread.java:134)        at hudson.remoting.PingThread.run(PingThread.java:90)

 

TIA

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c0005418-b120-4bb8-939f-f12f064847dbn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: master to agent connection keeps breaking every 3-4 hours

Ashish Sharma-2
We have tried putting these on both side, but still facing same issue :( 

On Thursday, October 1, 2020 at 1:33:57 AM UTC+8 [hidden email] wrote:
ideally, on both sides, make it on one side usually is enough.

El miércoles, 30 de septiembre de 2020 a las 3:22:00 UTC+2, [hidden email] escribió:
Thanks, are these setting to be applied on master side or slave or both?

On Wednesday, September 30, 2020 at 12:15:23 AM UTC+8 [hidden email] wrote:
  • Why does agent tries to connect to master when its already connected?
That suggests half-closed connections, it means that the agent loses the connection with the Jenkins instance but the FIN notification never arrived to the Jenkins instance so the connection is open in the Jenkins instance side. It could be related to networks equipment and the policies that have for open connections, the recommendation is to tune the TCP stack to keep those connections open with traffic see https://support.cloudbees.com/hc/en-us/articles/115001416548#7tcpretransmissiontimeoutossperhapsincrease

El martes, 29 de septiembre de 2020 a las 10:47:22 UTC+2, [hidden email] escribió:

Hi Team, We are using JNLP to connect Mac agent to Linux master node.

Jenkins agent keeps disconnecting frequently, and we are getting below logs in master.

Can you please suggest how to resolve this? What are the steps to further triage the same.

Some of the questions we are trying to answer is:

  • What is EOFException?
  • Why does agent tries to connect to master when its already connected?
  • Why does eventually the ping / connection fails? 

We keep seeing this pattern in logs too often and too frequently. Any help would be appreciated.

Results are same even if we try any of the below options:

  • Connected using Launch agent from Browser
  • Connected by starting automator in Mac which runs shell/zsh to run agent.jar
  • Connected by running plist in Mac

 Jenkins environment:

  • Jenkins: 2.249.1
  • Master Node: Linux RHEL 8.1
  • Master Java Version: 1.8.0_242
  • Slave System: macOS Catalina, Version 10.15.6
  • Slave Java Version: 1.8.0_261
Connection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:21 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler run Accepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57215 Sep 29, 2020 2:45:21 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer on Recv[JNLP4-connect connection from x.x.x.x/x.x.x.x:57215] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:31 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler runConnection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:31 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler runAccepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57218 Sep 29, 2020 2:45:32 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv[JNLP4-connect connection from x.x.x.x/x.x.x.x] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:32 AM INFO hudson.slaves.ChannelPinger$1 onDeadPing failed. Terminating the channel JNLP4-connect connection from x.x.x.x/x.x.x.x:57015. java.util.concurrent.TimeoutException: Ping started at 1601318492966 hasn't completed by 1601318732966        at hudson.remoting.PingThread.ping(PingThread.java:134)        at hudson.remoting.PingThread.run(PingThread.java:90)

 

TIA

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c8522ac5-64f0-458f-b853-ac874d2ef6b6n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: master to agent connection keeps breaking every 3-4 hours

kuisathaverat
then the only thing you can do it is to enable the debug on the sshd server to see what happens with the connection (see https://en.wikibooks.org/wiki/OpenSSH/Logging_and_Troubleshooting), then open a regular ssh connection from the Jenkins instance to the Agent from command line and see what happens after 4 hours  

El mié., 4 nov. 2020 a las 4:03, Ashish Sharma (<[hidden email]>) escribió:
We have tried putting these on both side, but still facing same issue :( 

On Thursday, October 1, 2020 at 1:33:57 AM UTC+8 [hidden email] wrote:
ideally, on both sides, make it on one side usually is enough.

El miércoles, 30 de septiembre de 2020 a las 3:22:00 UTC+2, [hidden email] escribió:
Thanks, are these setting to be applied on master side or slave or both?

On Wednesday, September 30, 2020 at 12:15:23 AM UTC+8 [hidden email] wrote:
  • Why does agent tries to connect to master when its already connected?
That suggests half-closed connections, it means that the agent loses the connection with the Jenkins instance but the FIN notification never arrived to the Jenkins instance so the connection is open in the Jenkins instance side. It could be related to networks equipment and the policies that have for open connections, the recommendation is to tune the TCP stack to keep those connections open with traffic see https://support.cloudbees.com/hc/en-us/articles/115001416548#7tcpretransmissiontimeoutossperhapsincrease

El martes, 29 de septiembre de 2020 a las 10:47:22 UTC+2, [hidden email] escribió:

Hi Team, We are using JNLP to connect Mac agent to Linux master node.

Jenkins agent keeps disconnecting frequently, and we are getting below logs in master.

Can you please suggest how to resolve this? What are the steps to further triage the same.

Some of the questions we are trying to answer is:

  • What is EOFException?
  • Why does agent tries to connect to master when its already connected?
  • Why does eventually the ping / connection fails? 

We keep seeing this pattern in logs too often and too frequently. Any help would be appreciated.

Results are same even if we try any of the below options:

  • Connected using Launch agent from Browser
  • Connected by starting automator in Mac which runs shell/zsh to run agent.jar
  • Connected by running plist in Mac

 Jenkins environment:

  • Jenkins: 2.249.1
  • Master Node: Linux RHEL 8.1
  • Master Java Version: 1.8.0_242
  • Slave System: macOS Catalina, Version 10.15.6
  • Slave Java Version: 1.8.0_261
Connection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:21 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler run Accepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57215 Sep 29, 2020 2:45:21 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer on Recv[JNLP4-connect connection from x.x.x.x/x.x.x.x:57215] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:31 AM  INFO hudson.TcpSlaveAgentListener$ConnectionHandler runConnection #xxx failed: java.io.EOFException Sep 29, 2020 2:45:31 AM INFO hudson.TcpSlaveAgentListener$ConnectionHandler runAccepted JNLP4-connect connection #xxx from x.x.x.x/x.x.x.x:57218 Sep 29, 2020 2:45:32 AM  INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv[JNLP4-connect connection from x.x.x.x/x.x.x.x] Refusing headers from remote: <agent_name> is already connected to this master. Rejecting this connection.Sep 29, 2020 2:45:32 AM INFO hudson.slaves.ChannelPinger$1 onDeadPing failed. Terminating the channel JNLP4-connect connection from x.x.x.x/x.x.x.x:57015. java.util.concurrent.TimeoutException: Ping started at 1601318492966 hasn't completed by 1601318732966        at hudson.remoting.PingThread.ping(PingThread.java:134)        at hudson.remoting.PingThread.run(PingThread.java:90)

 

TIA

 

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/LiRA5m-zEP4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c8522ac5-64f0-458f-b853-ac874d2ef6b6n%40googlegroups.com.


--

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKo5QrosCksdRosvCze-S0cdxWJGXqyq5fFQsQK89WhoAqQNpA%40mail.gmail.com.