0

remote file operation failed due to channel closed down

Hi ,
Am facing the following error,
 
ERROR: Issue with creating launcher for agent <agent_lable_name>. The agent has not been fully initialized yet
ERROR: Issue with creating launcher for agent <agent_lable_name>. The agent has not been fully initialized yet
remote file operation failed: /home/jenkins/workspace/<project_name> at hudson.remoting.Channel@4f7b2455:<agent_lable_name>: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on <agent_lable_name> failed. The channel is closing down or has closed down
 
Due to this some pipeline builds are aborted by throwing the above error I cannot continue my job execution till the end.

Thank in advance

1 comment

  • 1
    Avatar
    Ryan Campbell

    Basically, the agent has become unexpectedly disconnected. The best approach is to search through the Jenkins logs for the name of the agent to build a timeline of the connection/disconnection events. You will also want to connect the logs from the agent's workspace/logs directory. In this way, you can compare the timeline from the master POV and the agent's POV.

    What kind of agent is this? SSH or JNLP?

    JNLP Agent Diagnostic guide

    SSH Agent Diagnostic Guide

    There are several common causes of this kind of problem:

    * JNLP agent connection is going through some kind of load balancer which has incorrect timeouts set.

    * OOME or GC thrashing on master or agent.

    * Based on the messages, there may be some problem launching the agent. I've seen this with SSH agents that have some post connection initalization that takes longer than expected.

Please sign in to leave a comment.