Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

health_check extension: liveliness is failing, not sure. #24655

Closed
Ishmeet opened this issue Jul 28, 2023 · 5 comments
Closed

health_check extension: liveliness is failing, not sure. #24655

Ishmeet opened this issue Jul 28, 2023 · 5 comments
Labels
bug Something isn't working extension/healthcheck Health Check Extension Stale waiting for author

Comments

@Ishmeet
Copy link
Contributor

Ishmeet commented Jul 28, 2023

Component(s)

extension/healthcheck

What happened?

Description

Getting this error

Liveness probe failed: Get "http://10.85.3.47:13133/": dial tcp 10.85.3.47:13133: connect: connection refused 

But when I exec into the pod and do curl localhost:13133 it gives 200 ok. I am not sure, If I am missing something.

Otel config:

    extensions:
      health_check:
        check_collector_pipeline:
          enabled: true
          exporter_failure_threshold: 5
          interval: 5m
        endpoint: localhost:13133 // tried with 0.0.0.0:13133 -> same error   

I am using open telemetry-operator to create a statefulset pod of collector config.

curl from other pod to port 13133 is not working

# curl test-collector.default:13133
curl: (7) Failed to connect to test-collector.default port 13133 after 1 ms: Couldn't connect to server 

But I have pprof also configured at port 1777. That is working

# curl test-collector.default:1777
404 page not found

Steps to Reproduce

Use health check extension

Expected Result

Healthcheck should have worked.

Actual Result

Liveness probe failed: Get "http://10.85.3.47:13133/": dial tcp 10.85.3.47:13133: connect: connection refused 

Collector version

v0.79.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

extensions:
      health_check:
        check_collector_pipeline:
          enabled: true
          exporter_failure_threshold: 5
          interval: 5m
        endpoint: localhost:13133 // tried with 0.0.0.0:13133 -> same error

Log output

No response

Additional context

No response

@Ishmeet Ishmeet added bug Something isn't working needs triage New item requiring triage labels Jul 28, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the extension/healthcheck Health Check Extension label Jul 28, 2023
@jpkrohling
Copy link
Member

Can you share the entire collector logs? Using 0.0.0.0:13133 in the endpoint should have made it work.

@DewaldDeJager
Copy link
Contributor

Did you enable the health check extension in the services section of the collector config?

service:
  extensions: [pprof, health_check]

@crobert-1
Copy link
Member

/label waiting-for-author

@atoulme atoulme removed the needs triage New item requiring triage label Dec 6, 2023
@atoulme
Copy link
Contributor

atoulme commented Dec 6, 2023

This bug has been waiting for author for a little while. Closing. Please reopen if more discussion is needed.

@atoulme atoulme closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working extension/healthcheck Health Check Extension Stale waiting for author
Projects
None yet
Development

No branches or pull requests

5 participants