[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title Dzianis Mazuronak commented on JENKINS-59094 Re: Agent tunnel connection issues after ugrading Jenkins to 2.191 Update to Jenkins version 2.194 was successful. Thank you very much for this fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.62.1568032200508%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title
Dzianis Mazuronak edited a comment on JENKINS-59094
Re: Agent tunnel connection issues after ugrading Jenkins to 2.191
Here is the jenkins-slave.xml file from my windows slave xx05ws016:{code:xml} jenkinsslave-C__projects_jenkins Jenkins agent (jenkinsslave-C__projects_jenkins) This service runs an agent for Jenkins automation server. C:\Program Files (x86)\AdoptOpenJDK\jre-8.0.222.10-hotspot\bin\java.exe -Xrs -jar "%BASE%\slave.jar" -jnlpUrl https://tools.x.local/devjenkins/computer/x05ws016/slave-agent.jnlp -secret XXX -noCertificateCheck rotate className="winsw.Plugins.RunawayProcessKiller.RunawayProcessKillerExtension" id="killOnStartup"> %BASE%\jenkins_agent.pid 5000 false {code} Unfortunately, I'll *not* be able to test your PR. Compiling Jenkins from the source code is not a easy task.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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 jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.3433.1567193100193%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Windows Agent connection issues after ugrading Jenkins to 2.191
Title: Message Title Dzianis Mazuronak commented on JENKINS-59094 Re: Windows Agent connection issues after ugrading Jenkins to 2.191 Here is the jenkins-slave.xml file from my windows slave xx05ws016: jenkinsslave-C__projects_jenkins Jenkins agent (jenkinsslave-C__projects_jenkins) This service runs an agent for Jenkins automation server. C:\Program Files (x86)\AdoptOpenJDK\jre-8.0.222.10-hotspot\bin\java.exe -Xrs -jar "%BASE%\slave.jar" -jnlpUrl https://tools.x.local/devjenkins/computer/x05ws016/slave-agent.jnlp -secret XXX -noCertificateCheck rotate "restart" /> "https://tools.x.local/devjenkins/jnlpJars/slave.jar" to="%BASE%\slave.jar"/> "true" className="winsw.Plugins.RunawayProcessKiller.RunawayProcessKillerExtension" id="killOnStartup"> %BASE%\jenkins_agent.pid 5000 false I'll be able to test your PR. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.1525.1566971460375%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Windows Agent connection issues after ugrading Jenkins to 2.191
Title: Message Title Dzianis Mazuronak commented on JENKINS-59094 Re: Windows Agent connection issues after ugrading Jenkins to 2.191 Hello Jeff Thompson, here is my configuration: Jenkins is running on the host J (x.x.3.9). The Jenkins web interface is available over reverse proxy running on the different host P (x.x.3.2). There are DNS alias tools.x.local, pointing to the host P. Jenkins windows slave runs on the host x05ws016 (x.x.13.82) as Windows Service, initially installed over Java Web Start. Here are some interesting sections from Jenkins Global Security Configuration page: Agents: TCP port for inbound agents:Random Agent protocols:Java-Web-Start-Agent protocol Version 4 (TLS-encryption) SSH Server: SSHD Port: Deactivated And here are part of the windows agent log, after Jenkins was restored to the version 2.190: Aug 27, 2019 8:43:45 AM hudson.remoting.jnlp.Main createEngine INFORMATION: Setting up agent: x05ws016 Aug 27, 2019 8:43:45 AM hudson.remoting.jnlp.Main$CuiListener INFORMATION: Jenkins agent is running in headless mode. Aug 27, 2019 8:43:45 AM hudson.remoting.jnlp.Main createEngine WARNUNG: Certificate validation for HTTPs endpoints is disabled Aug 27, 2019 8:43:45 AM hudson.remoting.Engine startEngine INFORMATION: Using Remoting version: 3.33 Aug 27, 2019 8:43:45 AM hudson.remoting.Engine startEngine WARNUNG: No Working Directory. Using the legacy JAR Cache location: C:\Windows\system32\config\systemprofile\.jenkins\cache\jars Aug 27, 2019 8:43:45 AM hudson.remoting.jnlp.Main$CuiListener status INFORMATION: Locating server among [https://tools.xxx.local/devjenkins/] Aug 27, 2019 8:43:45 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver openURLConnection WARNUNG: HTTPs certificate check is disabled for the endpoint. Aug 27, 2019 8:43:45 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFORMATION: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Aug 27, 2019 8:43:45 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFORMATION: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check Aug 27, 2019 8:43:45 AM hudson.remoting.jnlp.Main$CuiListener status INFORMATION: Agent discovery successful Agent address: x.x.3.9 Agent port:33773 Identity: f8:2a:3d:5a:d4:22:f4:a0:89:26:4a:a1:34:20:c3:11 Aug 27, 2019 8:43:45 AM hudson.remoting.jnlp.Main$CuiListener status INFORMATION: Handshaking Aug 27, 2019 8:43:45 AM hudson.remoting.jnlp.Main$CuiListener status INFORMATION: Connecting to x.x.3.9:33773 Aug 27, 2019 8:43:45 AM hudson.remoting.jnlp.Main$CuiListener status INFORMATION: Trying protocol: JNLP4-connect Aug 27, 2019 8:43:46 AM hudson.remoting.jnlp.Main$CuiListener status INFORMATION: Remote identity confirmed: f8:2a:3d:5a:d4:22:f4:a0:89:26:4a:a1:34:20:c3:11 Aug 27, 2019 8:43:48 AM hudson.remoting.jnlp.Main$CuiListener status INFORMATION: Connected
[JIRA] (JENKINS-59094) Windows Agent connection issues after ugrading Jenkins to 2.191
Title: Message Title
Dzianis Mazuronak updated an issue
Jenkins / JENKINS-59094
Windows Agent connection issues after ugrading Jenkins to 2.191
Change By:
Dzianis Mazuronak
After updating Jenkins master to 2.191 windows slave thows following exception: {code:java}Aug 27, 2019 8:41:10 AM hudson.remoting.jnlp.Main createEngineINFORMATION: Setting up agent: spsde05ws016Aug 27, 2019 8:41:10 AM hudson.remoting.jnlp.Main$CuiListener INFORMATION: Jenkins agent is running in headless mode.Aug 27, 2019 8:41:11 AM hudson.remoting.jnlp.Main createEngineWARNUNG: Certificate validation for HTTPs endpoints is disabledAug 27, 2019 8:41:11 AM hudson.remoting.Engine startEngineINFORMATION: Using Remoting version: 3.34Aug 27, 2019 8:41:11 AM hudson.remoting.Engine startEngineWARNUNG: No Working Directory. Using the legacy JAR Cache location: C:\Windows\system32\config\systemprofile\.jenkins\cache\jarsAug 27, 2019 8:41:11 AM hudson.remoting.jnlp.Main$CuiListener statusINFORMATION: Locating server among [https://tools. spsde x .local/devjenkins/]Aug 27, 2019 8:41:11 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver openURLConnectionWARNUNG: HTTPs certificate check is disabled for the endpoint.Aug 27, 2019 8:41:11 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFORMATION: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Aug 27, 2019 8:41:11 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFORMATION: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkAug 27, 2019 8:41:11 AM hudson.remoting.jnlp.Main$CuiListener errorSCHWERWIEGEND: For input string: ""java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:592) at java.lang.Integer.parseInt(Integer.java:615) at org.jenkinsci.remoting.engine.HostPort.splitHostPort(HostPort.java:25) at org.jenkinsci.remoting.engine.HostPort.(HostPort.java:8) at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:329) at hudson.remoting.Engine.innerRun(Engine.java:529) at hudson.remoting.Engine.run(Engine.java:490){code}
Add Comment
[JIRA] (JENKINS-59094) Windows Slave connection issues after ugrading Jenkins to 2.191
Title: Message Title Dzianis Mazuronak created an issue Jenkins / JENKINS-59094 Windows Slave connection issues after ugrading Jenkins to 2.191 Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2019-08-27 06:57 Environment: Windows 7 Oracle JRE jre1.8.0_171 AdoptOpenJDK jre-8.0.222.10-hotspot Priority: Major Reporter: Dzianis Mazuronak After updating Jenkins master to 2.191 windows slave thows following exception: Aug 27, 2019 8:41:10 AM hudson.remoting.jnlp.Main createEngine INFORMATION: Setting up agent: spsde05ws016 Aug 27, 2019 8:41:10 AM hudson.remoting.jnlp.Main$CuiListener INFORMATION: Jenkins agent is running in headless mode. Aug 27, 2019 8:41:11 AM hudson.remoting.jnlp.Main createEngine WARNUNG: Certificate validation for HTTPs endpoints is disabled Aug 27, 2019 8:41:11 AM hudson.remoting.Engine startEngine INFORMATION: Using Remoting version: 3.34 Aug 27, 2019 8:41:11 AM hudson.remoting.Engine startEngine WARNUNG: No Working Directory. Using the legacy JAR Cache location: C:\Windows\system32\config\systemprofile\.jenkins\cache\jars Aug 27, 2019 8:41:11 AM hudson.remoting.jnlp.Main$CuiListener status INFORMATION: Locating server among [https://tools.spsde.local/devjenkins/] Aug 27, 2019 8:41:11 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver openURLConnection WARNUNG: HTTPs certificate check is disabled for the endpoint. Aug 27, 2019 8:41:11 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFORMATION: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Aug 27, 2019 8:41:11 AM
[JIRA] (JENKINS-36491) Jenkins uses wrong JDK for Maven build step
Title: Message Title Dzianis Mazuronak updated an issue Jenkins / JENKINS-36491 Jenkins uses wrong JDK for Maven build step Change By: Dzianis Mazuronak Environment: Solaris 10 x86, Jenkins 2.11 , Linux x86_64 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36491) Jenkins uses wrong JDK for Maven build step
Title: Message Title Dzianis Mazuronak updated an issue Jenkins / JENKINS-36491 Jenkins uses wrong JDK for Maven build step Change By: Dzianis Mazuronak Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36491) Jenkins uses wrong JDK for Maven build step
Title: Message Title Dzianis Mazuronak commented on JENKINS-36491 Re: Jenkins uses wrong JDK for Maven build step I've checked our other jenkins instance. It seens to be a problem espacially with multiconfigurations project. This Jenkins use wrong 1.8 JDK instead of single jdk 1.7 configured in. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36491) Jenkins uses wrong JDK for Maven build step
Title: Message Title Dzianis Mazuronak updated an issue Jenkins / JENKINS-36491 Jenkins uses wrong JDK for Maven build step Change By: Dzianis Mazuronak Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36491) Jenkins uses wrong JDK for Maven build step
Title: Message Title Dzianis Mazuronak created an issue Jenkins / JENKINS-36491 Jenkins uses wrong JDK for Maven build step Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Jul/07 8:01 AM Environment: Solaris 10 x86, Jenkins 2.11 Priority: Minor Reporter: Dzianis Mazuronak Job is configured as multiconfiguration project. There are 2 build slaves solaris/sparc and solaris/x86. A jdk 1.7 installed at /usr/jdk/jdk1.7.0_80 is configured and assigned to the job. The maven build step on solaris/x86 failed with the error: Error: JAVA_HOME is not defined correctly. We cannot execute /usr/jdk/jdk1.6.0_111/bin/java Add Comment
