I'm getting a uname: command not found error from Bamboo

[Jira Admin]

Bamboo task failed with error "/usr/local/git/libexec/git-core/git-sh-setup: line 235: uname: command not found". The command is present on the server, i can also ran every command from Bamboo task on the server without any problem or errors. Bamboo uses the same user credentials but trows the error above and exits with "Result: exit code = 255" 

How can i solve this problem.

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

If it is the same user, try running the commands from the same working directory.

[Jira Admin]

I did but still same problem.

The Bamboo task looks like this.

cd /var/www/html/my-site
git checkout Acceptance
git fetch --all --recurse-submodules=on-demand -v
git reset --hard Acceptance
git pull
git submodule sync
git submodule update --init --recursive --force

All the commands can be executed in same order (1 by 1 ) on the server without any problem. 

[Jobin Kuruvilla [Adaptavist]]

1. Are you sure you are running as the same user?
2. Is it running on the same agent?

[Jira Admin]

1. Yes, i'm sure Bamboo uses the user
2. How do you mean the same agent?

[Jobin Kuruvilla [Adaptavist]]

Bamboo can have several remote agents and the actual script will be running in an agent (default, local or remote). You can find the agent from the build logs.

[Jira Admin]

These were the info i could find about the instance in the log:

simple	21-Jan-2016 14:15:26	Build GGD Zuid Limburg - ggdzl.acceptance.netcreators.nl - Default Job #17 (GGDZLB-GGDZLAC-JOB1-17) started building on agent Elastic Agent on i-0f7ca4365351a4ce6
simple	21-Jan-2016 14:15:26	Elastic agent on instance i-0f7ca4365351a4ce6

If i'm not mistaken it's a remote instance. Bamboo will start a instance when ever there's a task to be executed.

[Jobin Kuruvilla [Adaptavist]]

Looks like you have to fix the permissions on that instance!

[Jira Admin]

How can i fix the permission because Bamboo will create a new instance when needed.
So i could fix it on a instance but when this instance is no longer required (has gone into idle state for a  long period) Bamboo will terminate it. And when there is a new task to be executed Bamboo will create a new instance.

[Jobin Kuruvilla [Adaptavist]]

How is Bamboo creating the new instance? If it is an elastic agent, fix it on the image itself!

[Jira Admin]

I've checked the elastic user permission (on the elastic server self) and they seems to be alright. Can you tell me which permission i need to fix?

[Jobin Kuruvilla [Adaptavist]]

It is complining about "uname not found". Either it is not installed or not available to the user running the build!

[Jira Admin]

I've tried both.

On the actual server where the repo files are stored. I can execute uname in any directory including the ones from Bamboo task job.
Also on the elastic server i could execute the uname command without any problem.

On other servers i don't get this uname error, the task commands are the same (only the ip-address and username are different).  

[Jira Admin]

Jobin, do you have any idea how i can solve this problem?

[Jobin Kuruvilla [Adaptavist]]

No idea to be frank. You need some server admins to dive in with you on this issue. Builds only get executed on the elastic agents and so you need to debug on them.

[Nilesh Choundikar]

This is because PATH variable does not contain path for /bin from where all sh commands can be run. Correct the PATH variable and everything should be fine. If you want to see what is there current PATH, you can write echo $PATH >> testfile in bamboo.