[JIRA] (JENKINS-58627) jenkins agent getting terminated with version 2.176.2
Title: Message Title Chethan Mahabaleswara commented on JENKINS-58627 Re: jenkins agent getting terminated with version 2.176.2 Hello Oleg, I see the fix is released as part of jenskins V 2.181, for Component remoting [15489]. But when i tried with jenkins version 2.187, observed the same issue/ error I had also tried jenkins version 2.176.2, but I see fix is not released in this version. 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.200795.1563941135000.5683.1564680540233%40Atlassian.JIRA.
[JIRA] (JENKINS-58627) jenkins agent getting terminated with version 2.176.2
Title: Message Title Chethan Mahabaleswara updated an issue Jenkins / JENKINS-58627 jenkins agent getting terminated with version 2.176.2 More information about the issue - I'm having an issue while using Networl Connection Emulator that it just terminates the jenkins agent process as explained below: Scenario 1 - I have jenkins agent set up in Windows 2012 machine where connection emulator is installed. I run a python script through jenkins pipeline to set the latency and open the connection emulator using python function "subprocess.Popen(["schtasks","/Run","/TN","StartNetworkEmulator"]) ", which opens emulator from windows task scheduler as a last step. Once the connection emulator is opened, it interferes with the jenkins agent process and terminates the jenkins agent and master communication. I have to close the emulator and restart the jenkins agent windows service to make agent communicate with jenkins master Scenario 2 - There are no jenkins jobs or pipeline running. Jenkins agent is active and connected to Master. When I open and run Connection emulator manually by going C:\Program Files, the jenkins agent and master communication is broken. Sometimes I see Linkage error and few times "Error while determining if vetoers exist" The error log observed in build and slave are attached. Note - Same job or pipeline works with no issues with old jenkins version 2.76 having remoting version 3.11. But we want to upgrade to new windows server where I installed latest jenkins version. Is this a bug with latest version of jenkins ? Appreciate any help in fixing this issue Thanks, Chethan Change By: Chethan Mahabaleswara Attachment: Error log_in Build.txt Attachment: Agent Log_V1.txt Add Comment
[JIRA] (JENKINS-58627) jenkins agent getting terminated with version 2.176.2
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-58627 jenkins agent getting terminated with version 2.176.2 Change By: Alex Earl Summary: jenkins slave agent getting terminated with version 2.176.2 Hi,Jenkins slave agent is geting terminated with new version 2.176.2 as explained below OS - windows 2012 R2 (both Master and Slave agent )Java - 1.8.0_211 (both Mater and Salve slave )Jenkins Version - 2.176.2Launch Method - Java Web start, JNLP(Launch by connecting it to the Master) Issue - I have a project in Jenkins which fails mainly because the slave agent terminates after 'Starting ServiceWrapper in the CLI mode' during execution.Finds a child process conhost.exe and failed due to Killing as fallback.This is happening only for a project/ pipeline, where I have python script which pings a internal URL (https://URL/ping), invokes the network emulator tool installed, adjust the network latency and also write to a file/ push to ELK. I have a internet proxy set up using .pac file. It completes all the steps in project, at the end the slave agent terminates, marking the build as failure Note - We also have another old version of jenkins 2.76 installed where the same project/ pipeline works with out any issue. Now we want to upgrade to latest jenkins we are seeing issue with slave agent getting terminated. I now have to close the network emulator tool every time and restart the jenkins service to bring it back online. Error as obsreved in Jenkins-slave.wrapper.log:-2019-07-24 03:51:59,751 INFO - Stopping jenkinsslave-e__jenkins2019-07-24 03:51:59,751 DEBUG - ProcessKill 68722019-07-24 03:51:59,860 INFO - Found child process: 6408 Name: conhost.exe2019-07-24 03:51:59,892 INFO - Stopping process 64082019-07-24 03:51:59,907 INFO - Send SIGINT 64082019-07-24 03:51:59,907 WARN - SIGINT to 6408 failed - Killing as fallback2019-07-24 03:51:59,907 INFO - Stopping process 68722019-07-24 03:51:59,907 INFO - Send SIGINT 68722019-07-24 03:51:59,907 WARN - SIGINT to 6872 failed - Killing as fallback2019-07-24 03:51:59,907 INFO - Finished jenkinsslave-e__jenkins2019-07-24 03:51:59,907 DEBUG - Completed. Exit code is 0 Error as obsreved in jenkins-slave.error.log:-Jul 24, 2019 3:57:23 AM hudson.remoting.jnlp.Main$CuiListener statusJul 24, 2019 3:57:23 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: TerminatedJul 24, 2019 3:57:23 AM hudson.util.ProcessTree getWARNING: Error while determining if vetoers existhudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException at hudson.remoting.Request.abort(Request.java:340) at hudson.remoting.Channel.terminate(Channel.java:1040) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:209) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvC
