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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to