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

Unable to access hawkular-metric API #25260

Closed
prashansahans opened this issue Jul 9, 2020 · 4 comments
Closed

Unable to access hawkular-metric API #25260

prashansahans opened this issue Jul 9, 2020 · 4 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@prashansahans
Copy link

[provide a description of the issue]
Deploy hawkular metric using playbooks
ansible-playbook [-i </path/to/inventory>] <OPENSHIFT_ANSIBLE_DIR>/playbooks/openshift-metrics/config.yml \ -e openshift_metrics_install_metrics=True \ -e openshift_metrics_hawkular_hostname=hawkular-metrics.xxxxxx.nip.io
But metric console is unavailable
[root@master master]# oc get pods
NAME READY STATUS RESTARTS AGE
hawkular-cassandra-1-ddt5v 1/1 Running 0 3d
hawkular-metrics-schema-khqt2 0/1 Completed 0 3d
hawkular-metrics-zkq9f 1/1 Running 0 3d
heapster-sbrnn 1/1 Running 0 3d

oc get --raw="/api/v1/namespaces/openshift-infra/services/https:heapster:/proxy/api/v1/model/metrics"
[
"cpu/request",
"cpu/limit",
"memory/request",
"memory/limit",
"cpu/usage_rate",
"memory/usage"
]

Issue:-
**curl http://hawkular-metrics.xxxxxx.nip.io/ -vv

  • About to connect() to hawkular-metrics.xxxxx.nip.io port 80 (#0)
  • Trying 10.136.53.196...
  • Connection refused
  • Failed connect to hawkular-metrics.xxxxxxx.nip.io; Connection refused
  • Closing connection 0
    curl: (7) Failed connect to hawkular-metrics.xxxxxx.nip.io; Connection refused**
Version

oc v3.11.0+62803d0-1
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

openshift v3.11.0+88feed3-432
kubernetes v1.11.0+d4cacc0

Current Result

curl: (7) Failed connect to hawkular-metrics.xxxxxx.nip.io; Connection refused**

Additional Information

logs of metrics

2020-07-09 05:00:45,583 INFO [org.hawkular.metrics.core.jobs.TempDataCompressor] (RxIoScheduler-87) Starting to process temp table for starting time of 2020-07-09T02:00:00.000Z
2020-07-09 05:00:54,058 INFO [org.hawkular.metrics.core.jobs.TempDataCompressor] (RxComputationScheduler-2) Finished processing data in 8474 ms
2020-07-09 07:00:45,584 INFO [org.hawkular.metrics.core.jobs.TempDataCompressor] (RxIoScheduler-89) Starting to process temp table for starting time of 2020-07-09T04:00:00.000Z
2020-07-09 07:00:52,762 INFO [org.hawkular.metrics.core.jobs.TempDataCompressor] (RxComputationScheduler-4) Finished processing data in 7179 ms
2020-07-09 09:00:45,589 INFO [org.hawkular.metrics.core.jobs.TempDataCompressor] (RxIoScheduler-91) Starting to process temp table for starting time of 2020-07-09T06:00:00.000Z
2020-07-09 09:00:52,708 INFO [org.hawkular.metrics.core.jobs.TempDataCompressor] (RxComputationScheduler-3) Finished processing data in 7120 ms

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 26, 2020
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 25, 2020
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants