##[error]We stopped hearing from agent Azure Pipelines 4. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error..

Ranjan, Rajeev (KT) 50 Reputation points
2023-02-09T16:54:37.3366667+00:00
##[error]We stopped hearing from agent Azure Pipelines 4. Verify the agent machine is running and 
	  has a healthy network connection. 
	  Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. 
	  For more information, see: https://go.microsoft.com/fwlink/?linkid=846610

      This job was abandoned. We have detected that logs from the agent may have not finished uploading. 
	  We have included our in-memory record of all log lines uploaded before we lost contact with the agent.
Community Center | Not monitored
{count} votes

2 answers

Sort by: Most helpful
  1. Jayesh Patel 10 Reputation points
    2023-03-20T10:52:50.0366667+00:00

    Hi guys, im getting the same issue using a hotst agent, tried windows 2022 and windows latest same result. the pipeline is only running for 1hrs, i can see the job is actual complete but it fails with this error:

    This job was abandoned. We have detected that logs from the agent may have not finished uploading. We have included our in-memory record of all log lines uploaded before we lost contact with the agent:


  2. Diego Rafael O. Souza 0 Reputation points
    2025-05-05T08:20:06.6666667+00:00

    I had the same issue few months ago while using Linux self hosted agents. For that particular case, it turned up that there was a OS firmware update process running for my agent host that was killing the azdo agent process, as you can see in the journal logs:

    fwupd[2844]: 18:47:15.266 FuMain               Received SIGTERM
    systemd[1]: Stopping fwupd.service - Firmware update daemon...
    systemd[1]: Stopping multipathd.service - Device-Mapper Multipath Device Controller...
    multipathd[198]: multipathd: shut down
    systemd[1]: Stopping packagekit.service - PackageKit Daemon...
    python3[904]: 2024-11-14T18:47:15.271871Z INFO Daemon Daemon Agent WALinuxAgent-2.9.1.1 forwarding signal 15 to WALinuxAgent-2.12.0.2
    systemd[1]: Stopping walinuxagent.service - Azure Linux Agent...
    systemd[1]: multipathd.service: Deactivated successfully.
    systemd[1]: Stopped multipathd.service - Device-Mapper Multipath Device Controller.
    systemd[1]: packagekit.service: Deactivated successfully.
    systemd[1]: Stopped packagekit.service - PackageKit Daemon.
    runuser[2772]: pam_unix(runuser:session): session closed for user AzDevOps
    sudo[2769]: pam_unix(sudo:session): session closed for user root
    systemd[1]: Starting multipathd.service - Device-Mapper Multipath Device Controller...
    systemd[1]: Starting packagekit.service - PackageKit Daemon...
    systemd[1]: fwupd.service: Deactivated successfully.
    systemd[1]: Stopped fwupd.service - Firmware update daemon.
    systemd[1]: fwupd.service: Consumed 1.013s CPU time, 143.6M memory peak, 0B memory swap peak.
    PackageKit[5707]: daemon start
    systemd[1]: Starting fwupd.service - Firmware update daemon...
    multipathd[5710]: multipathd v0.9.4: start up
    multipathd[5710]: reconfigure: setting up paths and maps
    

    What solved the issue for us was turn off the service that performs that OS update and was triggering the SIGTERM for the AZDO agent:

    sudo systemctl disable apt-daily.timer
    sudo systemctl disable apt-daily-upgrade.timer
    sudo systemctl stop apt-daily.timer
    sudo systemctl stop apt-daily-upgrade.timer
    

    You can find more info at the github issue related: https://github.com/microsoft/azure-pipelines-agent/issues/4313#issuecomment-2501564255

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.