Remote agent disconnected due to heartbeat timeout
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
Remote agent disconnected due to heartbeat timeout.
The following appears in the remote agent atlassian-bamboo.log
1
2
2018-07-19 01:23:44,249 FATAL [scheduler_Worker-10] [AgentContext] Agent encountered a fatal error: 'The last successful transmission was 11 minutes ago, the heartbeat timeout is 10 minutes, terminating agent'. Exiting.
java.util.concurrent.TimeoutException: The last successful transmission was 11 minutes ago, the heartbeat timeout is 10 minutes, terminating agentDiagnosis
Check CPU and RAM usage in the machine hosting Bamboo server and remote/elastic agent.
Cause
Multiple or all agents disconnected at the same time
Bamboo server running OutOfMemory Errors on the Bamboo Server or Local Agent or CPU, causing it fail to connect to remote/elastic agents.
There is a remote/elastic agent producing huge build log which take a lot of Bamboo server resources to process it causing other remote/elastic agents to be disconnected.
Remote/elastic agent disconnected when running build - CPU or RAM usage too high in the machine hosting remote/elastic agent causing it fail to connect to Bamboo server.
Solution
Resolution
Multiple or all agents disconnected at the same time
Increase Configuring your system properties and make sure that machine specification meet Bamboo Best Practice - System Requirements.
Reduce the huge build log size for the related plan
Windows - Check huge build log size in the machine hosting Bamboo
<BAMBOO_HOME>\xml-data\builds\<plan-idNumber>\download-data\build_logsLinux - Run the following command in the machine hosting Bamboo:
1find <BAMBOO_HOME>/xml-data/builds -type f -name "*.log" -mtime -30 -exec du -h --time {} \; | sort -rh | head -50From the
idNumber, run the following SQL query to look for the related plan:1 2 3 4SELECT bd.BUILD_ID, pr.TITLE, bd.TITLE FROM BUILD bd JOIN PROJECT pr ON pr.PROJECT_ID = bd.PROJECT_ID WHERE BUILD_ID = <idNumber>;
Remote/elastic agent disconnected when running build - increase the machine specification of the remote/elastic agent so that CPU or RAM usage is not fully utilised in the build.
Was this helpful?