| Summary: | Many "couldn't get SNTP reply" errors in node-exporter container logs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> | ||||
| Component: | Monitoring | Assignee: | Frederic Branczyk <fbranczy> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.1.0 | CC: | anpicker, erooth, mloibl, pkrupa, surbania | ||||
| Target Milestone: | --- | Keywords: | Regression | ||||
| Target Release: | 4.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-06-04 10:47:47 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
PR opened to fix this https://github.com/openshift/cluster-monitoring-operator/pull/334 The PR has merged. issue is fixed payload: 4.1.0-0.nightly-2019-04-25-121505 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758 |
Created attachment 1556342 [details] node-exporter container logs Description of problem: Many "couldn't get SNTP reply" errors in node-exporter container logs eg: $ oc -n openshift-monitoring logs node-exporter-spc65 -c node-exporter time="2019-04-19T02:00:05Z" level=error msg="ERROR: ntp collector failed after 0.000279s: couldn't get SNTP reply: read udp 127.0.0.1:60401->127.0.0.1:123: read: connection refused" source="collector.go:132" time="2019-04-19T02:00:05Z" level=error msg="ERROR: ntp collector failed after 0.002058s: couldn't get SNTP reply: read udp 127.0.0.1:58233->127.0.0.1:123: read: connection refused" source="collector.go:132" time="2019-04-19T02:00:35Z" level=error msg="ERROR: ntp collector failed after 0.005542s: couldn't get SNTP reply: read udp 127.0.0.1:47830->127.0.0.1:123: read: connection refused" source="collector.go:132" time="2019-04-19T02:00:35Z" level=error msg="ERROR: ntp collector failed after 0.000153s: couldn't get SNTP reply: read udp 127.0.0.1:45740->127.0.0.1:123: read: connection refused" source="collector.go:132 details see the attached logs file, it seems it does not affect the function Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-04-18-190537 How reproducible: Always Steps to Reproduce: 1. Check node-exporter container logs 2. 3. Actual results: Many "couldn't get SNTP reply" errors in node-exporter container logs Expected results: Should not have this error Additional info: