[JIRA] [master-slave] (JENKINS-22722) Master doesn't show connected slave
Gergely Nagy commented on JENKINS-22722 Master doesnt show connected slave We have the same issue with every Windows versions (XP, Vista, Win7, Win8, Win8.1) from local virtual machine slaves and even from Azure. For the first time the slaves can connect, but after they disconnect, they can't connect back again (this bug happens). Only restarting the jenkins server helps. Reverting to 1.559 works for me too. I only tried direct connection with JNLP agents. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
[JIRA] [master-slave] (JENKINS-22722) Master doesn't show connected slave
Gergely Nagy updated JENKINS-22722 Master doesnt show connected slave Change By: Gergely Nagy (10/Jun/14 4:44 PM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
[JIRA] [master-slave] (JENKINS-22722) Master doesn't show connected slave
Ryan Croom commented on JENKINS-22722 Master doesnt show connected slave We experienced the exact same issue with the same log information that Michaël commented with. A master restart would bring things back to normal until we restarted the slave and then subsequent connections would fail until the master was restarted again. Reverting to 1.559 fixed the issue. Our Jenkins machine is running on ArchLinux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
[JIRA] [master-slave] (JENKINS-22722) Master doesn't show connected slave
Michaël Burtin commented on JENKINS-22722 Master doesnt show connected slave I experience the same issue with Jenkins 1.563. Slaves are started via Amazon EC2 plugin, using Spot instance, and connect to master via JNLP. Sometimes master refuse to show slave as online, node logs only show: JNLP agent connected from /172.x.x.x Usually a master restart bring back everything to normal. Node logs show: JNLP agent connected from /172.x.x.x ===[JENKINS REMOTING CAPACITY]===Slave.jar version: 2.41 This is a Unix slave Slave successfully connected and online ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
[JIRA] [master-slave] (JENKINS-22722) Master doesn't show connected slave
Gregory Fernandez created JENKINS-22722 Master doesnt show connected slave Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: master-slave Created: 22/Apr/14 7:51 PM Description: When updating slave.jar on slave with version shipped with Jenkins 1.560, slave show a message "connected" but master does not show the slave online. Reverting to the slave.jar in 1.533 or 1.559 make it work as usual. Tried with direct connection or via Apache reverse proxy. Environment: Master: debian wheezy (jenkins installed by apt) Slave: Windows 7 (x64) Project: Jenkins Priority: Minor Reporter: Gregory Fernandez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
