Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1463146

Summary:	After first deployment of collectd write_http plugin can not connect to localhost on port 9880
Product:	[oVirt] ovirt-engine-metrics	Reporter:	Lukas Svaty <lsvaty>
Component:	Generic	Assignee:	Shirly Radco <sradco>
Status:	CLOSED DUPLICATE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.0.4.2	CC:	bugs, ylavi
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+ lsvaty: testing_ack+
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-17 18:08:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1464737
Bug Blocks:

Description Lukas Svaty 2017-06-20 08:51:21 UTC

Description of problem:
After running configure_ovirt_machines_for_metrics.sh collected service is running with some error messages:

Jun 19 16:27:39 ls-engine1.example.com collectd[12722]: write_http plugin: curl_easy_perform failed with status 7: Failed connect to localhost:9880; Connection refused


After restart of collectd service it seems to be working correctly

Version-Release number of selected component (if applicable):
ovirt-engine-metrics-1.0.4.2-1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Set up config.yml in /etc/ovirt-engine-metrics
2. run /usr/share/ovirt-engine-metrics/setup/ansible/configure_ovirt_machines_for_metrics.sh 
3. systemctl colelctd status

Actual results:
Jun 19 16:27:39 ls-engine1.example.com collectd[12722]: write_http plugin: curl_easy_perform failed with status 7: Failed connect to localhost:9880; Connection refused

Expected results:
all success

Additional info:
WA is to restart collectd service

Comment 1 Shirly Radco 2017-06-20 09:17:46 UTC

This happens since the fluentd was not yet running.
I think this is reasonable behavior.
I believe checking that fluentd is running before starting collectd will complicate this process.

Yaniv, should we make sure that fluentd is running before starting collectd?

Comment 2 Lukas Svaty 2017-06-20 09:47:15 UTC

we can't expect from user to check and debug it manually, can we add to playbook check for fluentd running and (re)starting collectd after that?

Comment 3 Yaniv Lavi 2017-06-26 19:28:47 UTC

(In reply to Lukas Svaty from comment #2)
> we can't expect from user to check and debug it manually, can we add to
> playbook check for fluentd running and (re)starting collectd after that?

Sound correct to me. Only start collectd once we know fluentd is running.

Comment 4 Shirly Radco 2017-07-17 18:08:42 UTC


*** This bug has been marked as a duplicate of bug 1464737 ***