High Problem
The Bamboo Agent and Bamboo Docker Agent bamboo-agent-base uses 100% CPU
The issue is due to a bug on Tanuki Service Wrapper 3.5.48 fixed on 3.5.49:
- https://wrapper.tanukisoftware.com/doc/english/release-notes.html#3.5.49
Version 3.5.49: Changes and bug fixes (2022-02-09)
Fix high CPU usage observed on certain Unix platforms when running as a console application. The Windows platform, as well as daemon installations on Unix are not affected. Since 3.5.47. Applications using version 3.5.48 that do not need to handle stdin may circumvent the issue by adding wrapper.disable_console_input=TRUE to their configuration file. This workaround is not recommended for 3.5.47 because of another issue (see below).
Environment
- Bamboo Agent (regular and Docker)
- Embedded Tanuki Service Wrapper 3.5.48
Steps to Reproduce
- Start the Remote Agent (9.0, 8.2.4) - Docker or regular
- Monitor the CPU and observe the wrapper process consuming 100% of it
Expected Results
The Bamboo docker agent should run normally and not consume all the CPU
Actual Results
wrapper process consumes 100% CPU
Workaround
On Docker Agent:
The following instructions will work on a fresh container where the wrapper.conf file doesn't exist. If you are using a docker volume or bind mount and want to fix an existing container, please modify the /var/atlassian/application-data/bamboo-agent/conf/wrapper.conf file manually as the container initialisation will not overwrite an already existing wrapper.conf
- Copy the original /opt/atlassian/etc/wrapper.conf.j2 file from the container to the host computer
- Append wrapper.disable_console_input=TRUE to the end of the file
- Either copy or mount the modified wrapper.conf.j2 to the container on /opt/atlassian/etc/
- Start the container
- Alternatively, add the property to your own version of the container
On a regular Agent:
- Append wrapper.disable_console_input=TRUE to the end of the <bamboo-agent-home>/conf/wrapper.conf file
- Restart the Agent
Hi,
This is also affecting Bamboo version 8.2.4