[JIRA] (JENKINS-52690) Agent failing after start FileSystemException Operation not permitted

1,230 views
Skip to first unread message

royal-dutch@ya.ru (JIRA)

unread,
Jul 23, 2018, 2:27:02 AM7/23/18
to jenkinsc...@googlegroups.com
Sergey Troizkiy created an issue
 
Jenkins / Bug JENKINS-52690
Agent failing after start FileSystemException Operation not permitted
Issue Type: Bug Bug
Assignee: Unassigned
Components: slave-status-plugin
Created: 2018-07-23 06:25
Priority: Minor Minor
Reporter: Sergey Troizkiy
 
 
Jul 23, 2018 9:04:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [https://sbt-jenkins.ca.sbrf.ru/jenkins/]
Jul 23, 2018 9:04:33 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, CLI2-connect, JNLP-connect, Ping, CLI-connect, JNLP2-connect]
Jul 23, 2018 9:04:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: sbt-jenkins.ca.sbrf.ru
  Agent port:    8181
  Identity:      ba:bd:6b:f0:59:5f:c4:b8:26:2a:c0:5d:18:d0:9d:e9
Jul 23, 2018 9:04:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jul 23, 2018 9:04:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to sbt-jenkins.ca.sbrf.ru:8181
Jul 23, 2018 9:04:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jul 23, 2018 9:04:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: ba:bd:6b:f0:59:5f:c4:b8:26:2a:c0:5d:18:d0:9d:e9
Jul 23, 2018 9:04:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Jul 23, 2018 9:04:33 AM hudson.remoting.ResourceImageBoth initiateJarRetrieval
WARNING: Failed to initiate retrieval
java.nio.file.FileSystemException: /u01/jenkins_slave/remoting/jarCache/16/8FC5C92395145F086E628C17BAC144.jar: Operation not permitted
                at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91)
                at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
                at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
                at sun.nio.fs.UnixFileAttributeViews$Basic.setTimes(UnixFileAttributeViews.java:109)
                at java.nio.file.Files.setLastModifiedTime(Files.java:2306)
                at hudson.remoting.FileSystemJarCache.lookInCache(FileSystemJarCache.java:77)
                at hudson.remoting.JarCacheSupport.resolve(JarCacheSupport.java:46)
                at hudson.remoting.ResourceImageBoth.initiateJarRetrieval(ResourceImageBoth.java:50)
                at hudson.remoting.ResourceImageBoth.resolve(ResourceImageBoth.java:23)
                at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:304)
                at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
                at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
                at java.lang.Class.forName0(Native Method)
                at java.lang.Class.forName(Class.java:348)
                at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:128)
                at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1866)
                at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1749)
                at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2040)
                at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1571)
                at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431)
                at hudson.remoting.UserRequest.deserialize(UserRequest.java:277)
                at hudson.remoting.UserRequest.perform(UserRequest.java:188)
                at hudson.remoting.UserRequest.perform(UserRequest.java:53)
                at hudson.remoting.Request$2.run(Request.java:364)
                at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
                at java.util.concurrent.FutureTask.run(FutureTask.java:266)
                at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
                at hudson.remoting.Engine$1$1.run(Engine.java:94)
                at java.lang.Thread.run(Thread.java:748)
 
Jul 23, 2018 9:04:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 23, 2018, 3:57:02 AM7/23/18
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 23, 2018, 3:57:02 AM7/23/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Component/s: remoting
Component/s: slave-status-plugin

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 23, 2018, 3:57:02 AM7/23/18
to jenkinsc...@googlegroups.com
Oleg Nenashev commented on Bug JENKINS-52690
 
Re: Agent failing after start FileSystemException Operation not permitted

Most likely the file is owned by another user so that the agent process has no permissions to edit that

royal-dutch@ya.ru (JIRA)

unread,
Jul 23, 2018, 4:59:02 AM7/23/18
to jenkinsc...@googlegroups.com

below how server side look at this issue 

java.nio.channels.ClosedChannelException        at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208)        at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)        at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)        at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)        at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181)        at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283)        at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503)        at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)        at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)        at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213)        at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800)        at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173)        at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:313)        at hudson.remoting.Channel.close(Channel.java:1446)        at hudson.remoting.Channel.close(Channel.java:1399)        at jenkins.slaves.DefaultJnlpSlaveReceiver.afterChannel(DefaultJnlpSlaveReceiver.java:173)        at org.jenkinsci.remoting.engine.JnlpConnectionState$4.invoke(JnlpConnectionState.java:421)        at org.jenkinsci.remoting.engine.JnlpConnectionState.fire(JnlpConnectionState.java:312)        at org.jenkinsci.remoting.engine.JnlpConnectionState.fireAfterChannel(JnlpConnectionState.java:418)        at org.jenkinsci.remoting.engine.JnlpProtocol4Handler$Handler$1.run(JnlpProtocol4Handler.java:334)        at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)        at java.lang.Thread.run(Thread.java:748) 

dbeck@cloudbees.com (JIRA)

unread,
Jul 24, 2018, 7:31:02 AM7/24/18
to jenkinsc...@googlegroups.com

/u01/jenkins_slave/remoting/ this could also be a shitty file system like NFS that doesn't support some operations.

jthompson@cloudbees.com (JIRA)

unread,
Oct 29, 2018, 5:07:02 PM10/29/18
to jenkinsc...@googlegroups.com

Sergey Troizkiy, I recommend you investigate your filesystem and other components of your environment. Daniel and Oleg have both suggested possible areas. There is no indication this is a general problem. There is insufficient information provided to reproduce.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jthompson@cloudbees.com (JIRA)

unread,
Dec 11, 2018, 2:11:03 PM12/11/18
to jenkinsc...@googlegroups.com
Jeff Thompson closed an issue as Cannot Reproduce
 

Closing for lack of sufficient diagnostics and information to reproduce after no response for quite a while.

Change By: Jeff Thompson
Status: Open Closed
Resolution: Cannot Reproduce
Reply all
Reply to author
Forward
0 new messages