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