Bug 2045948
| Summary: | openstack-collectd:16.2.1 - error message "procs_running not found" | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | XinhuaLi <xili> |
| Component: | collectd | Assignee: | Matthias Runge <mrunge> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 16.2 (Train) | CC: | cmuresan, jbadiapa, lars, lmadsen, m.andre, mmagr, mrunge, rmccabe, spower |
| Target Milestone: | z2 | Keywords: | Triaged, ZStream |
| Target Release: | 16.2 (Train on RHEL 8.4) | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | collectd-5.11.0-9.el8ost | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-23 22:13:07 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: | |||
The upstream commit is this here: https://github.com/collectd/collectd/commit/f4349080e721fab3deb0e0fee58b1028c2ff3f68 and it is included in collectd-5.12. This seems to be a duplicate to 1976786, which is for 16.1 This is targeted to z3 for 16.2, we are not in exception process for this so I'm removing the exception flag There is also the chance of misconfiguring the plugin, the documentation for the plugin can be found here: https://github.com/collectd/collectd/blob/main/src/collectd.conf.pod#plugin-processes tested on 16.2.2 Was unable to reproduce. No procs_running not found messages were seen. 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 (Release of components for Red Hat OpenStack Platform 16.2.2), 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-2022:1001 |
Description of problem: We can see many "procs_running not found" in collectd logs. --------------------------------------------------------- [2022-01-25 11:14:38] procs_running not found [2022-01-25 11:14:43] procs_running not found [2022-01-25 11:14:48] procs_running not found [2022-01-25 11:14:53] procs_running not found [2022-01-25 11:14:58] procs_running not found [2022-01-25 11:15:03] procs_running not found [2022-01-25 11:15:08] procs_running not found [2022-01-25 11:15:13] procs_running not found [2022-01-25 11:15:18] procs_running not found [2022-01-25 11:15:23] procs_running not found [2022-01-25 11:15:28] procs_running not found [2022-01-25 11:15:33] procs_running not found [2022-01-25 11:15:38] procs_running not found ----------------------------------------------------------- Version-Release number of selected component (if applicable): Image : registry.redhat.io/rhosp-rhel8/openstack-collectd:16.2.1 How reproducible: deploy STF and check collectd logs. Steps to Reproduce: 1. 2. 3. Actual results: error show Expected results: No error Additional info: Please help to check if we should merge the fix from upsteam. ------------------------------------------------------ --- collectd-5.11.0.orig/src/processes.c +++ collectd-5.11.0/src/processes.c @@ -1429,7 +1429,7 @@ static int ps_read_process(long pid, pro } /* int ps_read_process (...) */ static int procs_running(void) { - char buffer[4096] = {}; + char buffer[65536] = {}; char id[] = "procs_running "; /* white space terminated */ char *running; char *endptr = NULL; -------------------------------------------------- Regards Sam