Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49730

JENKINS_SLAVE shows connected status but appears offline on JENKINS_MASTER

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: swarm-plugin
    • Labels:
      None
    • 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
    • Similar Issues:

      Description

      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

        Attachments

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          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

          Show
          oleg_nenashev Oleg Nenashev added a comment - 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
          Hide
          rexandre07 Rex Coronel added a comment -

          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.

          Show
          rexandre07 Rex Coronel added a comment - 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.
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          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?

          Show
          oleg_nenashev Oleg Nenashev added a comment - 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?
          Hide
          rexandre07 Rex Coronel added a comment -

          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.

          Show
          rexandre07 Rex Coronel added a comment - 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.

            People

            • Assignee:
              Unassigned
              Reporter:
              rexandre07 Rex Coronel
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: