-
Bug
-
Resolution: Fixed
-
Low
-
5.7.2, 5.9.4, 5.12.2.1, 6.4.2
-
Severity 3 - Minor
-
3
-
Summary
If Bamboo hit into UnresolvedAddressException for a lot of time when accessing Stash, it may hit into "Too many open files" error later
Steps to Reproduce
- Set the hostname test.atlassian.com to Stash (can use /etc/hosts)
- Create Application Link between Stash and Bamboo
- Make sure that the repository is added successfully into Bamboo
- Delete the hostname test.atlassian.com
- Build a Plan in Bamboo that uses Stash repository
- Wait for it to fail
- Check open files with the commands "lsof -p <BAMBOO_PID>"
- Repeat step 5-7 for a lot of time
Expected Results
The open files that connect to Stash should be released after the failure
Actual Results
The open files keep on increasing
Notes
If there are a lot of Repositories in Bamboo connecting to Stash, the open files will keep on increasing until it hit into "Too many open files" error
Workaround
Assuming that the address reported in the UnresolvedAddressException is incorrect because you've migrated Bitbucket to a new address, you can replace the URL Bamboo is using to access Bitbucket using these steps:
- Shutdown Bamboo
- Backup database for rollback purposes
- Run the following SQL to change the hostname:
UPDATE VCS_LOCATION SET XML_DEFINITION_DATA=REPLACE(XML_DEFINITION_DATA,"old_hostname","new_hostname");
- Restart Bamboo
Alternatively, if the address is correct and still can't be resolved – you'll need to investigate why your DNS infrastructure does not correctly resolve the address.
- is related to
-
BAM-18555 ssh process is not killed on git command timeout
- Long Term Backlog
- relates to
-
BAM-15278 Bamboo is leaking tcp sockets to the proxy
- Closed
- was cloned as
-
BDEV-10016 Loading...