Bug 2074853

Summary:	Flood of "procs_running not found" messages in collectd.log
Product:	Red Hat OpenStack	Reporter:	Alex Stupnikov <astupnik>
Component:	collectd	Assignee:	Leonid Natapov <lnatapov>
Status:	CLOSED DUPLICATE	QA Contact:	Leonid Natapov <lnatapov>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.2 (Train)	CC:	csibbitt, jbadiapa, lars, lmadsen, mmagr, mrunge
Target Milestone:	z4	Keywords:	TestOnly, Triaged, ZStream
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-07 16:31:44 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:
Embargoed:

Description Alex Stupnikov 2022-04-13 09:17:35 UTC

Description of problem:

collectd logs are flooded with messages like [1]. I couldn't find related RHOSP bugs, but problems with similar symptoms were reported for other operating systems (like Debian).

stf.tar attached to support case contains sosreports and extra logs from controller nodes.

Version-Release number of selected component (if applicable):
RHOSP 16.2.1

[1]
[2022-04-11 00:00:50] procs_running not found
[2022-04-11 00:00:55] procs_running not found
[2022-04-11 00:01:00] procs_running not found

Comment 1 Chris Sibbitt 2022-04-13 15:23:05 UTC

Suspect this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1987244 and would like to retest with 16.2.2 and appropriate buffer settings

Comment 2 Alex Stupnikov 2022-04-13 15:26:21 UTC

I agree that it looks like a duplicate, although I am not sure how much time it would take for customer to test this. What do you think about closing this as duplicate and possibly re-opening if problem wouldn't be resolved?

Comment 9 Leif Madsen 2022-06-28 20:58:09 UTC

Related issue created at https://bugzilla.redhat.com/show_bug.cgi?id=2101944

Comment 10 Martin Magr 2022-09-07 16:31:44 UTC


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