Fatal error when running Bamboo Remote Agent as Service

Question

Running Bamboo 5.9.1 on Windows 7/x64

Executing jobs on a remote Bamboo agent (starting from the CLI) is working without problems.

After installing the Bamboo agent as a service (using InstallBambooAgent-NT.bat and StartBambooAgent-NT.bat as administrator) the following errors are produced when starting a build:

18-Aug-2015 10:07:35Starting task 'Checkout Default Repository' of type 'com.atlassian.bamboo.plugins.vcs:task.vcs.checkout'18-Aug-2015 10:07:35Updating source code to revision: 2092046078a1e95ff4427733910c2c35ab6f318818-Aug-2015 10:07:35C:\Users\bu62ein\AppData\Local\Programs\Git\cmd\git.exe version18-Aug-2015 10:07:35C:\Users\bu62ein\AppData\Local\Programs\Git\cmd\git.exe log -1 --encoding=UTF-8 --format=%H HEAD18-Aug-2015 10:07:36C:\Users\bu62ein\AppData\Local\Programs\Git\cmd\git.exe ls-remote ssh://996b848f-72e6-4fd4-bb8c-301e0ea08cb4@127.0.0.1:59838/ac/ipipe.git18-Aug-2015 10:07:36Cannot fetch branch '(unresolved) master' from 'ssh://git@EINAPPL32:7999/ac/ipipe.git' to source directory 'D:\GIT\bamboo\build\_git-repositories-cache\1bf8fe6b220021b84b29bfe98989b7a6fed81ba6'. com.atlassian.bamboo.plugins.git.GitCommandException: command C:\Users\bu62ein\AppData\Local\Programs\Git\cmd\git.exe ls-remote ssh://996b848f-72e6-4fd4-bb8c-301e0ea08cb4@127.0.0.1:59838/ac/ipipe.git failed with code 128. Working directory was [D:\GIT\bamboo\build\_git-repositories-cache\1bf8fe6b220021b84b29bfe98989b7a6fed81ba6]., stderr:[error: cannot spawn C:\Windows\system32\config\systemprofile\AppData\Local\Temp\bamboo-ssh.41538fd5.bat: No such file or directory, fatal: unable to fork]

When running the command from the CLI the following error is returned:

D: 	mp>C:\Users\bu62ein\AppData\Local\Programs\Git\cmd\git.exe ls-remote ssh://4
b709691-51a4-4bbb-a2db-2e577f651948@127.0.0.1:59838/ac/ipipe.git
ssh: connect to host 127.0.0.1 port 59838: Bad file number
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

What can be the problem? I would like start using the Service so I am not depending on starting batch files to keep the bamboo agent up and running.

rsperafico · Answer

Hello Michal, Issue stderr:[error: cannot spawn C:\Windows\system32\config\systemprofile\AppData\Local\Temp\bamboo-ssh.41538fd5.bat: No such file or directory, fatal: unable to fork] The issue relates to Bamboo not being able to write to the temporary directory. In this case, please: Bamboo Server If running builds against the Bamboo server and/or Bamboo Local Agent(s) * stop Bamboo (bring the instance down) * edit /bin/setenv.sh (Linux/MacOS), setenv.bat (Win) and append the following property to JVM_SUPPORT_RECOMMENDED_ARGS= # on Linux/MacOS -Djava.io.tmpdir=/opt/temp # on Windows -Djava.io.tmpdir=C: emp * start Bamboo Bamboo Remote Agent * stop Bamboo Remote Agent (bring the agent down) * edit /conf/wrapper.conf and add the following: # on LinuxMacOS wrapper.java.additional.X=-Djava.io.tmpdir=/opt/temp # on Windows wrapper.java.additional.X=-Djava.io.tmpdir=C: emp Where X is the next number in sequence * start Bamboo Remote Agent Bamboo as Windows Service * Identify the name of the service that Bamboo is installed as by going to "Control Panel >> Administrative Tools >> Services". * Right click on the Bamboo service and select "Properties" * The name of the service is shown after "Service name" * Open the command window from "Start >> Run >> type in 'cmd' >> Enter" * In this command window, cd to the \bin directory. * Run tomcat7w //ES//%SERVICENAME% (prior Bamboo v5.10.0). Run tomcat8w //ES//%SERVICENAME% (Bamboo v5.10.0 and above) * Click on the Java tab and add these to the list of current startup options: -Djava.io.tmpdir=C: emp Note: Each option must be on its own line. * Apply the changes and restart the Bamboo service for those to take effect. Notes Please, make sure the directory provided as temporary directory exists and the user running Bamboo has full permissions against it. — Kind regards, Rafael P. Sperafico

Michal Machniak · Answer

I have randomly the same problem on Windows 2012 R2, is there solution on this error.