I had aborted a job by clicking the [x] button next to it's name in the Build Executor Status panel of Jenkins, yet the job is still present and waiting.
Even when I restart Jenkins it will resume building. When I take a look at the console I see:
Sending interrupt signal to process Click here to forcibly terminate
running steps java.io.IOException: Aborting build at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
Source) at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Source) at java.lang.reflect.Constructor.newInstance(Unknown Source)
at
org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
at
org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:247)
at Script1.run(Script1.groovy:1) at
groovy.lang.GroovyShell.evaluate(GroovyShell.java:585) [SNIP]
Finished: ABORTED Resuming build at Tue Oct 25 14:56:36 CDT 2016 after
Jenkins restart
I believe this version of my Pipeline script also included an "Input" block, it's possible the job was aborted as it was waiting for Input if that makes a difference
I clean these up by going Manage Jenkins -> Script Console and then putting in code like this:
Jenkins.instance.getItemByFullName(
"tpr-ereg")
.getBuildByNumber(24).
finish(hudson.model.Result.ABORTED,
new java.io.IOException("Aborting build"));
NOTE: the above may need to be all on one line in the Script Console
Related
I am having an issue with a Jenkins agent not being able to connect with the Controller when a specific job ends. All other jobs are completed without any issues.
Basically, the job runs on the agent without any issues and gives out the expected result but, fails when it is time to hand over the job to the Jenkins master.
Both Controller and Agent are windows server VMs.
I saw multiple questions about this issue in multiple forums and Jenkins support but none of the suggested solutions is able to solve my issue.
The error message is:
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection to hostname/IP:16076
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1797)
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
at hudson.remoting.Channel.call(Channel.java:1001)
at hudson.FilePath.act(FilePath.java:1166)
at hudson.FilePath.act(FilePath.java:1155)
at hudson.FilePath.copyTo(FilePath.java:2493)
at hudson.FilePath.copyTo(FilePath.java:2448)
at hudson.plugins.logparser.LogParserStatusComputer.computeStatusMatches(LogParserStatusComputer.java:88)
at hudson.plugins.logparser.LogParserStatusComputer.access$000(LogParserStatusComputer.java:22)
at hudson.plugins.logparser.LogParserStatusComputer$1.call(LogParserStatusComputer.java:54)
at hudson.plugins.logparser.LogParserStatusComputer$1.call(LogParserStatusComputer.java:47)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:376)
at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:122)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from hostname/IP:50925
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1797)
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
at hudson.remoting.Channel.call(Channel.java:1001)
at hudson.plugins.logparser.LogParserStatusComputer.computeStatusMatches(LogParserStatusComputer.java:47)
at hudson.plugins.logparser.LogParserStatusComputer.<init>(LogParserStatusComputer.java:36)
at hudson.plugins.logparser.LogParserParser.parseLogBody(LogParserParser.java:355)
at hudson.plugins.logparser.LogParserParser.parseLog(LogParserParser.java:165)
at hudson.plugins.logparser.LogParserPublisher.perform(LogParserPublisher.java:119)
at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:806)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:755)
at hudson.model.Build$BuildExecution.post2(Build.java:178)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:699)
at hudson.model.Run.execute(Run.java:1913)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:99)
at hudson.model.Executor.run(Executor.java:431)
java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 3
e:\jenkbuilds\(.+)\builds/[0-9]+(/.*)?
^
at java.util.regex.Pattern.error(Unknown Source)
at java.util.regex.Pattern.escape(Unknown Source)
at java.util.regex.Pattern.atom(Unknown Source)
at java.util.regex.Pattern.sequence(Unknown Source)
at java.util.regex.Pattern.expr(Unknown Source)
at java.util.regex.Pattern.compile(Unknown Source)
at java.util.regex.Pattern.<init>(Unknown Source)
at java.util.regex.Pattern.compile(Unknown Source)
at jenkins.security.s2m.RunningBuildFilePathFilter.op(RunningBuildFilePathFilter.java:91)
at jenkins.ReflectiveFilePathFilter.read(ReflectiveFilePathFilter.java:21)
at jenkins.FilePathFilterAggregator.read(FilePathFilterAggregator.java:75)
at jenkins.SoloFilePathFilter.read(SoloFilePathFilter.java:66)
at hudson.FilePath.reading(FilePath.java:3497)
at hudson.FilePath.access$300(FilePath.java:213)
at hudson.FilePath$CopyTo.invoke(FilePath.java:2507)
at hudson.FilePath$CopyTo.invoke(FilePath.java:2499)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3338)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:376)
at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18)
at hudson.remoting.CallableDecoratorList.lambda$applyDecorator$0(CallableDecoratorList.java:19)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:80)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Build step 'Console output (build log) parsing' marked build as failure
Archiving artifacts
Recording test results
Finished: FAILURE```
Please let me know if you would like to have more information.
Any help will be greatly appriciated.
Illegal/unsupported escape sequence near index 3 e:\jenkbuilds\(.+)\builds/[0-9]+(/.*)?
Build step 'Console output (build log) parsing' marked build as failure
Archiving artifacts
It would seem it's interpreting your path regex as an escape character "\j*". Wherever that regex is, try double slash, "e:\\jenbuilds", or try chage to unix style "/".
It's either the ArchiveArtifacts step or right before that. Show your config steps?
I managed to resolve the issue using #Ian W comment. When diving into the 'Log Parser' plugin's settings, I found that my last update to Jenkins plugins reset its settings.
I wasn't aware that there is a modified rule in Jenkins for this plugin.
To be more specific:
To find the list of rules:
Manage Jenkins - > Configure System -> Multi-job Retry Rule -> Log Parser Rules
To update the job:
Job -> Configure -> Post-Build Actions -> Use Project Rule -> paste rule
I hope this will turn to be useful for someone as this was quite of a challenge to find and fix.
I have a multijob which has 6 child job. During test, I found that the multijob always show failed even all sub jobs succeed. The error message is:
Finished Build : 1.0.0.1 of Job : Sub_Job_6 with status : SUCCESS
FATAL: Channel "unknown": Remote call on JNLP4-connect connection from build_machine/10.224.113.202:51903 failed. The channel is closing down or has closed down
java.nio.channels.ClosedChannelException
at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:789)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from build_machine/10.224.113.202:51903 failed. The channel is closing down or has closed down
at hudson.remoting.Channel.call(Channel.java:945)
at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1078)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:510)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:148)
at hudson.model.Run.execute(Run.java:1727)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:76)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Finished: FAILURE
I found the root cause. One of my sub job is to power off, power on the build machine( a reboot actually). After reboot, Jenkins client will re-connect to Jenkins server. The server may think it's a new conversation, the old one has stopped with some exception. So the final result will show failed.
After I removed this sub job, the multijob showed success finally.
I have inherited Jenkins form a previous co-worker. Unfortunately, he did this without bringing anyone else on it, so my knowledge of Jenkins is nothing more than writing scripts and throwing them up in the dashboard. I apologize upfront for missing something if I did.
I noticed this week that a couple of reports weren't coming in. When I jumped on the Jenkins dashboard, it shows that the slave is offline. I logged into the Windows server where the Jenkins slave is installed, I tried to run the exe, and get this error:
Unable to Run Jenkins-Slave.exe
So that's when I checked out the services, and found out that the Jenkins service wasn't running. I tried to run it, and I get this error:
Unable to Run Jenkins Slave Service
Because I don't really understand the ins and outs of this, I'm not too sure how to fix it. I tried restarting the server where the slave is located as well as restarting the master, but I don't get any change.
Again, I'm not too savvy with this, so any help would be greatly appreciated!
Edit: Requested by commentors, this is the information I am seeing from the logs. Looking at the slave.out.log, all I am seeing is this repeating:
Both error and output logs will be printed to C:\Temp\JenkinsSlave\remoting
I am seeing this in the slave.err.log. These are the last entries in there. They are the exact same logs that were in the log file located at C:\Temp\JenkinsSlave\remoting:
Jul 28, 2018 7:01:46 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkinsmaster:61069
Jul 28, 2018 7:01:46 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP4-plaintext not supported, skipping
Jul 28, 2018 7:01:46 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP3-connect not supported, skipping
Jul 28, 2018 7:01:46 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP2-connect not supported, skipping
Jul 28, 2018 7:01:46 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP-connect not supported, skipping
Jul 28, 2018 7:01:46 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: The server rejected the connection: None of the protocols were accepted
java.lang.Exception: The server rejected the connection: None of the protocols were accepted
at hudson.remoting.Engine.onConnectionRejected(Engine.java:655)
at hudson.remoting.Engine.innerRun(Engine.java:619)
at hudson.remoting.Engine.run(Engine.java:455)
Edit 1: So I was able to bring the slave back online thanks to #MichaelPowers. This was done by performing step 4 in this documentation: How to Setup a node. This worked to bring the slave back online, but I am still unable to run jobs tied to the slave. In the logs, I am seeing this:
`
Aug 06, 2018 1:20:43 PM hudson.remoting.UserRequest perform
WARNING: LinkageError while performing UserRequest:hudson.util.RemotingDiagnostics$GetThreadDump#df9d05
java.lang.LinkageError: Failed to load hudson.init.InitMilestone
at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:389)
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:307)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at hudson.util.RemotingDiagnostics$GetThreadDump.call(RemotingDiagnostics.java:98)
at hudson.util.RemotingDiagnostics$GetThreadDump.call(RemotingDiagnostics.java:95)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoClassDefFoundError: org/jvnet/hudson/reactor/Milestone
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.lang.ClassLoader.defineClass(Unknown Source)
at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:383)
... 14 more
Caused by: java.lang.ClassNotFoundException: org.jvnet.hudson.reactor.Milestone
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:317)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 18 more
Caused by: java.nio.file.AccessDeniedException: C:\Temp\JenkinsSlave\remoting\jarCache\1D\802F741B5EFFEF0E027F560ADF37AB.jar
at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsFileAttributeViews$Basic.setFileTimes(Unknown Source)
at sun.nio.fs.WindowsFileAttributeViews$Basic.setTimes(Unknown Source)
at java.nio.file.Files.setLastModifiedTime(Unknown Source)
at hudson.remoting.FileSystemJarCache.lookInCache(FileSystemJarCache.java:77)
at hudson.remoting.JarCacheSupport.resolve(JarCacheSupport.java:46)
at hudson.remoting.ResourceImageInJar._resolveJarURL(ResourceImageInJar.java:90)
at hudson.remoting.ResourceImageInJar.resolve(ResourceImageInJar.java:43)
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:304)
... 20 more`
Is there another way to update the slave?
I am also getting this in an email from the failed jobs:
`java.lang.ClassNotFoundException: org.jenkinsci.plugins.gitclient.Git$1
at java.net.URLClassLoader.findClass(Unknown Source)
at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at com.sun.jnlp.JNLPClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at java.io.ObjectInputStream.resolveClass(Unknown Source)
at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:134)
at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at hudson.remoting.UserRequest.deserialize(UserRequest.java:291)
at hudson.remoting.UserRequest.perform(UserRequest.java:190)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from fhiscripts1.fhi.com/10.1.1.126:62844
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
at hudson.remoting.Channel.call(Channel.java:955)
at hudson.FilePath.act(FilePath.java:1036)
at hudson.FilePath.act(FilePath.java:1025)
at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:137)
at hudson.plugins.git.GitSCM.createClient(GitSCM.java:821)
at hudson.plugins.git.GitSCM.createClient(GitSCM.java:812)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1180)
at hudson.scm.SCM.checkout(SCM.java:504)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1798)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Caused: java.lang.ClassNotFoundException: Failed to deserialize the Callable object. Perhaps you needed to implement DelegatingCallable?
at hudson.remoting.UserRequest.perform(UserRequest.java:192)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)
Caused: java.io.IOException: Remote call on JNLP4-connect connection from fhiscripts1.fhi.com/10.1.1.126:62844 failed
at hudson.remoting.Channel.call(Channel.java:959)
at hudson.FilePath.act(FilePath.java:1036)
at hudson.FilePath.act(FilePath.java:1025)
at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:137)
at hudson.plugins.git.GitSCM.createClient(GitSCM.java:821)
at hudson.plugins.git.GitSCM.createClient(GitSCM.java:812)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1180)
at hudson.scm.SCM.checkout(SCM.java:504)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1798)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)`
Final Edit:
Good news, I guess that once the was able to bring the slave back online, all I needed to do was to update the plugins. I went to Manage Jenkins > Manage Plugins and was able to update all of the plugins that were in need of it. After the restart, I was able to run jobs tied to the slave without issue.
Thanks again for the help!
This error occurs when your Jenkins master and slave disagree on which protocol to use. This generally happens when the server gets upgraded (either in version or security policy) and the slave isn't able to talk anymore because the master and server no longer speak any common dialects.
First thing to try is upgrading the Jenkins slave runner (see step 4).
If that doesn't resolve it the other option is to allow older dialects of the Jenkins protocol in your master. You can do this by going to Manage Jenkins -> Configure Global Security -> Agents -> Agent Protocols...
Simply check one of the protocols that the slave supports and the slave should be able to connect again. You may get security warnings in the Jenkins console though, since these protocols are typically disabled for a reason.
Every now and then all the Jenkins jobs that are currently running on some of my Jenkins slaves fail for the following reason:
java.nio.channels.ClosedChannelException
at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Issue happens only on some slaves, so it's not a problem with the master, I think...
In Jenkins slave log I got this one:
JNLP agent connected from xxxx
Slave.jar version: 3.7
This is a Windows agent
just before slave SLAVE01 gets online ...
executing prepare script ...
setting up slave SLAVE01 ...
slave setup done.
Agent successfully connected and online
ERROR: Connection terminated
[8mha:////4JmhQISHGLISGlsTHOZXEPbCK6pxtJiroBix+jLdfCfh/YKcSsnpDAAAAVx+LCAAAAAAAA98nsLuhNKKmjNKU4P08vOT+vODjuha&SHllHSE4tKMnMz/PLL0mV3NWzufebKBsTA0NFEYMUmgZnCA1SyAABjKpSSsdxNaiYAAAAA==[0mjava.nio.channels.ClosedChannelException
at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
In slave's windows event log I got the following records:
SLAVE01 7031 Error Microsoft-Windows-Service Control Manager System 27-03-2018 06:32:05 The Jenkins agent (jenkinsslave-c__jenkins) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.
SLAVE01 0 Warning jenkinsslave-c__jenkins Application 27-03-2018 06:32:05 Child process [596 - C:\Program Files\Java\jre1.8.0_162\bin\java.exe -Xrs -jar "c:\jenkins\slave.jar" -jnlpUrl http://master:1234/computer/SLAVE01/slave-agent.jnlp -secret 8b64b1c4c643a36587dfaa4bf106b9099ad1c5cd8f12333a4f2fa518363aa250] finished with -1
SLAVE01 0 Warning jenkinsslave-c__jenkins Application 27-03-2018 06:31:53 SIGINT to 3552 failed - Killing as fallback
SLAVE01 0 Warning jenkinsslave-c__jenkins Application 27-03-2018 06:31:52 SIGINT to 2308 failed - Killing as fallback
Any ideas what is going on?
I set up a Jenkins job to poll Perforce for changes in the depot every 15 minutes, however I am seeing the following error in the polling log:
Caught Exception communicating with perforce.P4 Where Parsing Error: //... and //some_depot/... filespecs are not allowed.
FATAL: Unable to communicate with perforce. Check log file for: P4 Where Parsing Error: //... and //some_depot/... filespecs are not allowed.
java.io.IOException: Unable to communicate with perforce. Check log file for: P4 Where Parsing Error: //... and //some_depot/... filespecs are not allowed.
at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1296)
at hudson.scm.SCM.poll(SCM.java:397)
at hudson.model.AbstractProject._poll(AbstractProject.java:1435)
at hudson.model.AbstractProject.poll(AbstractProject.java:1338)
at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544)
at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Done. Took 5.4 sec
No changes
Has anyone seen this before? Polling seemed to work perfectly a few hours ago, but now this error is appearing with each poll.
Perhaps your Perforce administrator just installed a new trigger, one which
generates the error message
//... and //some_depot/... filespecs are not allowed.
if it sees a client workspace spec with an unacceptable view map.
If that's indeed your problem, then you either have to specify a narrower (more precise) view map for the client workspace that your Jenkins build is using, or get your administrator to give you an exception in the trigger.