[JIRA] (JENKINS-49730) JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER

[rexandre0802@gmail.com (JIRA)]

Rex Coronel created an issue

Jenkins / JENKINS-49730 JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER Issue Type: Bug Assignee: Giuseppe Landolfi Components: slave-setup-plugin, swarm-plugin Created: 2018-02-25 14:18 Environment: Jenkins ver. 2.73.3 Slave Java Version "1.8.0_151" Slave Java(TM_ SE RUNTIME ENVIRONMENT (build 1.8.0_151-b12) swarm-client-3.10.jar RHEL 3.10.0-693.11.1.el7.x86_64 EC2-Instance Priority: Critical Reporter: Rex Coronel On EC2-Instance (Jenkins Slave): INFO: Discovering Jenkins master SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Feb 25, 2018 10:09:29 PM hudson.plugins.swarm.Client run INFO: Attempting to connect to http://jenkins.x.x/ 5c53e911-2091-4f8e-8122-abb162ac8a06 with ID 056b83d1 Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: dev-clone-056b83d1 Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Feb 25, 2018 10:09:29 PM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /root/.jenkins/cache/jars Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://jenkins.x.x/ Feb 25, 2018 10:09:29 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, JNLP-connect, Ping, JNLP2-connect] Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: 10.X.X.X Agent port: 50000 Identity: 57:fc:12:6c:27:a9:60:fe:18:5b:b7:ee:38:46:26:e7 Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to 10.X.X.X:50000 Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Feb 25, 2018 10:09:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Remote identity confirmed: 57:fc:12:6c:27:a9:60:fe:18:5b:b7:ee:38:46:26:e7 Feb 25, 2018 10:09:30 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected The logs on the ec2-slave shows a Connected status but on the Jenkins Server (Master), it shows an OFFLINE status. How is this? I need to get through this. Thanks Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev commented on JENKINS-49730

Re: JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER Is it indicated as "offline" or "temporary offline"? In the latter case there may be a monitor which puts the agent temporary offline without disconnecting it

Add Comment

[rexandre0802@gmail.com (JIRA)]

Rex Coronel commented on JENKINS-49730

Re: JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER

Hi Oleg Nenashev, It is indicated as "Offline" and not temporary. I don't really know what caused the issue since the logs that is shown in the Jenkins Node only says "JNLP Connected...." and the loading symbol. Also, the the swarm-client.jar that I'm using has been working for more or less a month now and on different ec2-instances but it suddenly stopped working. I've tried using a different version of the jar file (which I got from the artifact repository of repo.jenkins...) again on different ec2-instances and I ended up with the same result.

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev commented on JENKINS-49730

Re: JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER

Would be great to also get Master logs. No idea what's going on so far, which Swarm client version were you using before the upgrade?

Add Comment

[rexandre0802@gmail.com (JIRA)]

Rex Coronel commented on JENKINS-49730

Re: JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER

I was using the swarm-client-3.10.jar previously when I got the error. I've tried downgrading to ver. 3.3 but to no avail.   Below is the logs of the build slave on the Jenkins Master: JNLP agent connected from ip-10-xx-xx-1.xx-southeast-1.compute.internal/10.xx.x.1   NOTE: It stays like this with the loading symbol but no progress. I'll try connecting to the build slave via SSH and see if I experience the same issues.

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev assigned an issue to Unassigned

Jenkins / JENKINS-49730

JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER

Change By: Oleg Nenashev Assignee: Giuseppe Landolfi

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-49730 JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER

Change By: Oleg Nenashev Component/s: slave-setup-plugin

Add Comment

[me@basilcrow.com (JIRA)]

Basil Crow updated an issue

Jenkins / JENKINS-49730 JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER

Change By: Basil Crow Priority: Critical Minor

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)