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

Getting ERROR Could not get bootstrap info from the Collector: collector's OpAMP client never connected to the Supervisor #33129

Closed
Thejas-I opened this issue May 20, 2024 · 3 comments

Comments

@Thejas-I
Copy link

Component(s)

cmd/opampsupervisor

Describe the issue you're reporting

I have followed the steps as mentioned at https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/16f401b82d3f3d54a5bc3eda17610a3a98cb11ba/cmd/opampsupervisor/README.md
But I am getting the error as "ERROR opampsupervisor/main.go:24 could not get bootstrap info from the Collector: collector's OpAMP client never connected to the Supervisor"

Below is my supervisor_linux.yaml

server:
  endpoint: wss://127.0.0.1:4320/v1/opamp
  tls:
    # Disable verification to test locally.
    # Don't do this in production.
    insecure_skip_verify: true
    # For more TLS settings see config/configtls.ClientConfig

capabilities:
  reports_effective_config: true
  reports_own_metrics: true
  reports_health: true
  accepts_remote_config: true
  reports_remote_config: true

agent:
  executable: /root/Test/test-master/cmd/otelcol/test-collector

Below is my test-collector's config.yml

extensions:
  opamp:
    server:
      ws:
        endpoint: ws://127.0.0.1:4320/v1/opamp
        tls:
          insecure_skip_verify: true # Set to true if you're using self-signed certificates

service:
  extensions: [opamp]
@Thejas-I Thejas-I added the needs triage New item requiring triage label May 20, 2024
Copy link
Contributor

Pinging code owners:

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

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

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

Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant