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

I have a problem with a target (connection reset by peer) #3079

Closed
YraganTron opened this Issue Aug 15, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@YraganTron
Copy link

YraganTron commented Aug 15, 2017

I launch prometheus as a Docker image. Connection is not establishing with one of the targets (but it's good with the others). Here are a config and the error.

global:
  scrape_interval: 25s
  evaluation_interval: 25s
  scrape_timeout: 20s

  external_labels:
    monitor: 'mobil-med-monitor'

rule_files:
  - '/etc/prometheus/cadvisor.rules'
  - '/etc/prometheus/nodes.rules'
  - '/etc/prometheus/alert.rules'

scrape_configs:
  - job_name: 'ansible'
    metrics_path: '/ansible_manager_metrics'
    bearer_token: '123123'
    static_configs:
      - targets: ['some.service.stud.consul:443']
    scheme: https
    tls_config:
       ca_file: /tmp/rootCA.crt
#      insecure_skip_verify: true
Get https://some.service.stud.consul:443/ansible_manager_metrics: read tcp 172.17.0.23:33290->192.168.4.152:443: read: connection reset by peer

There is no problem with the target itself, if I try to watch metrics manually it's working.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Aug 17, 2017

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.