Reason for uma agent - ATTACH_FAILED 150 ERROR
search cancel

Reason for uma agent - ATTACH_FAILED 150 ERROR

book

Article ID: 412211

calendar_today

Updated On:

Products

DX Application Performance Management

Issue/Introduction

While trying  to auto attach uma sidecar t with simple java app found the below  message 

[INFO] [I.UMAControllerAutoAttachDataClient] agentHost::xxxxagentProcess::yyyy.sysagentName::Kubernetes

Agentaction::ADDEDtype::WHITELISTmessageagent_host: "xxxx"
agent_process: "yyyyyyy"
agent_name: "Kubernetes Agent"
app {
  container_id: "<container id>"
  pod_name: "<pod_name>"
  namespace_name: "<namespace>"
  owner_name: "<owner>"
  owner: DEPLOYMENT
  configuration {
    configuration {
      key: "abc.company.com/autoattach.enabled"
      value: "true"
    }
    configuration {
      key: "abc.company.com/autoattach.java.attach.overrides"
      value: "autoattach.java.agent.sidecar.enabled=true"
    }
  }
  status: ATTACH_FAILED
  detailed_message: "ProbeAnnotateResponse{statusCode=\'150\', message=\'Internal Response\', error=\'Service Error\'}"
}

 

Environment

UMA version 24.2 

Resolution

We generally get this error for several reasons as  below 

1:If the certs being used by probe auto attach and pod monitor container, when a api request made the probe auto attach will return the  error.

2: If there is any issues with the container that we request might have exited.