#prometheus (2022-08)

prometheus

Archive: https://archive.sweetops.com/prometheus/

2022-08-14

Niv Weiss avatar
Niv Weiss

Hey all, I been trying to install prometheus (prometheus-community/prometheus) on EKS fargate (serverless) with AMP (amazon managed prometheus) and I’m getting this error: Readiness probe failed: Get "<http://10.0.xx.xxx:9090/-/ready>": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Liveness probe failed: Get "<http://10.0.xx.xxx:9090/-/healthy>": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Failed to create pod sandbox: rpc error: code = Unavailable desc = error reading from server: read unix @->/run/containerd/containerd.sock: read: connection reset by peer Status: terminated - OOMKilled (exit code: 255) This is the command that I’m running when I’m installing prometheus: helm install -n prometheus prometheus -f prometheus-variables.yml prometheus-community/prometheus prometheus-variables.yml:

nodeExporter:
    enabled: false

alertmanager:
    enabled: false

serviceAccounts:
  server:
    name: amp-iamproxy-ingest-service-account
    annotations: 
      eks.amazonaws.com/role-arn: "arn:aws:iam::xxxxxxxxxx:role/amp-iamproxy-ingest-role"

server:
  persistentVolume:
    enabled: false
  remoteWrite:
    - url: <https://aps-workspaces.us-east-1.amazonaws.com/workspaces/xxxxxxxxxxxxx/api/v1/remote_write>
      sigv4:
        region: us-east-1
      queue_config:
        max_samples_per_send: 1000
        max_shards: 200
        capacity: 2500
  

Can someone help me understand what can be the problem?

Balazs Varga avatar
Balazs Varga

In status it shows oomkill. Did you give enough memory?

    keyboard_arrow_up