• Community
  • Products
  • Bamboo
  • Questions
  • Bamboo agent: java.io.IOException: Could not delete file bamboo-agent-home\classpath\winp.x64.dll' as instructed by the manifest

Bamboo agent: java.io.IOException: Could not delete file bamboo-agent-home\classpath\winp.x64.dll' as instructed by the manifest

gerardot March 22, 2016

This question is in reference to Atlassian Documentation: Troubleshooting Remote Agents

As soon as I start the remote agent I got the following error:

INFO | jvm 1 | 2016/03/21 16:01:51 | 2016-03-21 16:01:50,943 INFO [WrapperSimpleAppMain] [ClasspathBuilder] 322 file(s) currently in [C:\Users\mllapur\bamboo-agent-home\classpath]
INFO | jvm 1 | 2016/03/21 16:01:51 | Exiting due to fatal exception.
INFO | jvm 1 | 2016/03/21 16:01:51 | java.io.IOException: Could not delete file 'C:\Users\mllapur\bamboo-agent-home\classpath\winp.x64.dll' as instructed by the manifest
INFO | jvm 1 | 2016/03/21 16:01:51 | at com.atlassian.bamboo.agent.bootstrap.ClasspathBuilder.removeJarsAsDirectedByManifest(ClasspathBuilder.java:244)
INFO | jvm 1 | 2016/03/21 16:01:51 | at com.atlassian.bamboo.agent.bootstrap.ClasspathBuilder.extractZipFile(ClasspathBuilder.java:190)
INFO | jvm 1 | 2016/03/21 16:01:51 | at com.atlassian.bamboo.agent.bootstrap.ClasspathBuilder.getRemoteResources(ClasspathBuilder.java:133)
INFO | jvm 1 | 2016/03/21 16:01:51 | at com.atlassian.bamboo.agent.bootstrap.ClasspathBuilder.build(ClasspathBuilder.java:59)
INFO | jvm 1 | 2016/03/21 16:01:51 | at com.atlassian.bamboo.agent.bootstrap.AgentContext.newClassLoader(AgentContext.java:386)
INFO | jvm 1 | 2016/03/21 16:01:51 | at com.atlassian.bamboo.agent.bootstrap.AgentContext.run(AgentContext.java:98)
INFO | jvm 1 | 2016/03/21 16:01:51 | at com.atlassian.bamboo.agent.bootstrap.AgentBootstrap.run(AgentBootstrap.java:110)
INFO | jvm 1 | 2016/03/21 16:01:51 | at com.atlassian.bamboo.agent.bootstrap.AgentBootstrap.main(AgentBootstrap.java:45)
INFO | jvm 1 | 2016/03/21 16:01:51 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO | jvm 1 | 2016/03/21 16:01:51 | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
INFO | jvm 1 | 2016/03/21 16:01:51 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
INFO | jvm 1 | 2016/03/21 16:01:51 | at java.lang.reflect.Method.invoke(Unknown Source)
INFO | jvm 1 | 2016/03/21 16:01:51 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240)
INFO | jvm 1 | 2016/03/21 16:01:51 | at java.lang.Thread.run(Unknown Source)
INFO | jvm 1 | 2016/03/21 16:01:51 | 2016-03-21 16:01:51,754 FATAL [WrapperSimpleAppMain] [AgentBootstrap] Exiting due to fatal exception.

The wrapper starts again the agent and it falls again in the same error. It continues trying to start the Agent some times until it shows the following message:

 

ERROR | wrapper | 2016/03/21 16:47:00 | JVM exited unexpectedly.
FATAL | wrapper | 2016/03/21 16:47:00 | There were 5 failed launches in a row, each lasting less than 3 seconds. Giving up.
FATAL | wrapper | 2016/03/21 16:47:00 | There may be a configuration problem: please check the logs.
STATUS | wrapper | 2016/03/21 16:47:01 | <-- Wrapper Stopped
INFO | jvm 26 | 2016/03/21 16:50:06 | 2016-03-21 16:50:06,573 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...
INFO | jvm 26 | 2016/03/21 16:55:08 | 2016-03-21 16:55:08,372 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...
INFO | jvm 26 | 2016/03/21 17:00:10 | 2016-03-21 17:00:09,999 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...
INFO | jvm 26 | 2016/03/21 17:05:11 | 2016-03-21 17:05:11,571 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...
INFO | jvm 26 | 2016/03/21 17:10:13 | 2016-03-21 17:10:13,444 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...
INFO | jvm 26 | 2016/03/21 17:15:15 | 2016-03-21 17:15:15,401 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...
INFO | jvm 26 | 2016/03/21 17:20:16 | 2016-03-21 17:20:16,860 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...
INFO | jvm 26 | 2016/03/21 17:25:18 | 2016-03-21 17:25:18,689 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...
INFO | jvm 26 | 2016/03/21 17:30:20 | 2016-03-21 17:30:20,302 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...
INFO | jvm 26 | 2016/03/21 17:35:21 | 2016-03-21 17:35:21,808 INFO [0-BAM::Consbkp.csgalaxy.local::Agent:pool-3-thread-1] [BuildAgentControllerImpl] Agent 327681 checking build queue for executables...

 

Some cuestions that I couldnt response about this:

1) What is happening and how could I reolve this?

2)Why the Agent continues logging information even when it says "Wrapper Stopped"?

Some environment info:

Agent running on Windows 7 64 bits.
bamboo.agent.installer.version=1.2
C:\Users\mmacribosta>java -version
java version "1.8.0_73"
Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)

3 answers

2 votes
Samuel Langlois November 23, 2016

We had this issue when we were trying to start the Bamboo agent although it was already started on the machine.
We hadn't realised that the wrapper had started the agent again after we've killed it.
You need to kill both the wrapper and the java processes.

Hopefully this will help other people encountering this!

0 votes
Dhananjay Kale May 15, 2018

I killed the JAVA process and started it again. Worked successfully for me.

0 votes
Cale Bickler May 9, 2016

I had the same problem.

Why is bamboo agent so hard to set up?

Santosh Bhinge November 19, 2017

Have the same problem facing for file bamboo-additional-config.jar.

Anyone found any solution over this? Thanks.

Santosh Bhinge

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events