[JIRA] (JENKINS-7641) Slaves hang when archiving artifacts

[josephpatt...@gmail.com (JIRA)]

Title: Message Title

Joseph John commented on JENKINS-7641   Re: Slaves hang when archiving artifacts We were hitting with this issue but atleast in our case I was able to get a work around as below and with my limited experience I doubt the actual problem is with the Jenkins code interaction with DNS. In my case the Jenkins Master and the slave where I had the Artifact hanging was in different network domain. Example a simple ping command for me from jenkins master ping windows_machine_with_problem PING windows_machine_with_problem.DOMAIN1 (172.23.136.85) 56(84) bytes of data. 64 bytes from windows_machine_with_problem.DOMAIN1 (172.23.136.85): icmp_seq=1 ttl=127 time=0.287 ms 64 bytes from windows_machine_with_problem.DOMAIN1 (172.23.136.85): icmp_seq=2 ttl=127 time=0.335 ms 64 bytes from windows_machine_with_problem.DOMAIN1 (172.23.136.85): icmp_seq=3 ttl=127 time=0.377 ms ping windows_machine_with_noproblem PING windows_machine_with_noproblem.DOMAIN2 (172.28.8.87) 56(84) bytes of data. 64 bytes from 172.28.8.87: icmp_seq=1 ttl=128 time=0.379 ms 64 bytes from 172.28.8.87: icmp_seq=2 ttl=128 time=0.519 ms 64 bytes from 172.28.8.87: icmp_seq=3 ttl=128 time=0.400 ms This indicated any traffic which goes from the master to windows_machine_with_problem passes through some networking entities. To avoid any DNS from equation I just replaced the "hostname" in slave configuration directly with IP address and the artifact hanging disappeared. So to summarize when I used ip-address instead of DNS name , atleast in my case artifact hanging issue was resolved. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.