Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Duplicate
-
Labels:None
-
Similar Issues:
Description
After having installed Jenkins Version 2.99, none of my slaves did connect to the server anymore. Even a restart of the java script on the slave did not help.
Workaround: Update Remoting on the agent side to 3.15
Attachments
Issue Links
- is related to
-
JENKINS-48766 Jenkins Core should provide info about minimum supported Remoting version in API/REST API/logs
-
- Resolved
-
-
JENKINS-48761 Jenkins Slaves do not connect after update from version 2.95 to version 2.99 and jobs fail
-
- Resolved
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Oleg Nenashev [ oleg_nenashev ] |
Component/s | core [ 15593 ] | |
Component/s | remoting [ 15489 ] | |
Component/s | slave-utilization [ 17575 ] |
Priority | Major [ 3 ] | Blocker [ 1 ] |
Attachment | support_2018-01-02_17.45.19.zip [ 41006 ] |
Attachment | master-logs.txt [ 41007 ] |
Attachment | support_2018-01-02_18.01.52.zip [ 41008 ] |
Attachment | support_2018-01-02_19.58.29.zip [ 41010 ] |
Environment |
Windows 7, Jenkins 2.95 -> 2.99 I have about 5-7 Slaves connecting to the Jenkins server (using JNLP 1 - since I am in a safe business intranet area) |
Windows 7, Jenkins 2.95 -> 2.99 I have about 5-7 Slaves connecting to the Jenkins server (using JNLP 1 - since I am in a safe business intranet area) CentOS root, macOS Agents connecting to the root node with JNLP4. |
Link |
This issue is related to |
Environment |
Windows 7, Jenkins 2.95 -> 2.99 I have about 5-7 Slaves connecting to the Jenkins server (using JNLP 1 - since I am in a safe business intranet area) CentOS root, macOS Agents connecting to the root node with JNLP4. |
Windows 7, Jenkins 2.95 -> 2.99 I have about 5-7 Slaves connecting to the Jenkins server (using JNLP 1 - since I am in a safe business intranet area) CentOS root, macOS Agents connecting to the root node with JNLP4. Workaround: Update Remoting on the agent side to 3.15 |
Description | After having installed Jenkins Version 2.99, none of my slaves did connect to the server anymore. Even a restart of the java script on the slave did not help. |
After having installed Jenkins Version 2.99, none of my slaves did connect to the server anymore. Even a restart of the java script on the slave did not help. *Workaround*: Update Remoting on the agent side to 3.15 |
Link |
This issue is related to |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Remote Link | This issue links to "Retrospective thread (Web Link)" [ 19711 ] |
Resolution | Duplicate [ 3 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Hi,
I've exactly the same problem.
Agent log :
janv. 02, 2018 3:05:49 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up slave: Windows Slave
janv. 02, 2018 3:05:49 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using D:\Jenkins\remoting as a remoting work directory
Both error and output logs will be printed to D:\Jenkins\remoting
janv. 02, 2018 3:05:49 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
janv. 02, 2018 3:06:00 PM hudson.remoting.jnlp.GuiListener$1 run
INFO: Connecting to ciserver:8081 (retrying:2)
java.io.IOException: Failed to connect to ciserver:8081
{{ at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:242)}}
{{ at hudson.remoting.Engine.connect(Engine.java:686)}}
{{ at hudson.remoting.Engine.innerRun(Engine.java:547)}}
{{ at hudson.remoting.Engine.run(Engine.java:469)}}
Caused by: java.net.ConnectException: Connection refused: connect
{{ at sun.nio.ch.Net.connect0(Native Method)}}
{{ at sun.nio.ch.Net.connect(Unknown Source)}}
{{ at sun.nio.ch.Net.connect(Unknown Source)}}
{{ at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)}}
{{ at java.nio.channels.SocketChannel.open(Unknown Source)}}
{{ at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:203)}}
{{ ... 3 more}}
And in master log nothing appears...
Regards,
Bruno.