Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
memstrack failed with the followings errors,
$ journalctl -b0
memstrack-start[1909]: memstrack - will report kernel module memory usage summary and top allocation stack
memstrack-start[1920]: Tracing memory allocations, Press ^C to interrupt ...
memstrack-start[1920]: Error calling perf_event_open: Too many open files
memstrack-start[1920]: Failed initializing perf events
systemd[1]: Started Memstrack Anylazing Service.
systemd[1]: memstrack.service: Main process exited, code=exited, status=24/n/a
systemd[1]: memstrack.service: Failed with result 'exit-code'.
systemd[1]: Starting dracut cmdline hook...
Version-Release number of selected component (if applicable):
memstrack-0.2.4-2.el8
RHEL-8.8.0-20230126.17 on hpe-apache-cn99xx-08.khw4.lab.eng.bos.redhat.com
How reproducible:
always
Steps to Reproduce:
1. grubby --args=rd.memdebug=5 --update-kernel=DEFAULT
2. reboot
Actual results:
memstrack failed to report kernel module memory usage.
Expected results:
memstrack should report kernel module memory usage.
Additional info:
1. This issue can be both observed on both the latest kernel 4.18.0-452.el8.aarch64 as of writing and 4.18.0-372.12.1.el8_6.aarch64 which was released about half a year ago
2. This bug can also be reproduced on aarch64 RHEL9
3. memstrack works well in kdump kernel
4. memstrack works fine in other architectures like x86 and s390
This is a much easier way to reproduce this issue,
[root@hpe-apache-cn99xx-08 ~]# memstrack --report module_summary,module_top --notui
Tracing memory allocations, Press ^C to interrupt ...
Error calling perf_event_open: Too many open files
Failed initializing perf events
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 (memstrack bug fix and enhancement update), 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-2023:7156
Description of problem: memstrack failed with the followings errors, $ journalctl -b0 memstrack-start[1909]: memstrack - will report kernel module memory usage summary and top allocation stack memstrack-start[1920]: Tracing memory allocations, Press ^C to interrupt ... memstrack-start[1920]: Error calling perf_event_open: Too many open files memstrack-start[1920]: Failed initializing perf events systemd[1]: Started Memstrack Anylazing Service. systemd[1]: memstrack.service: Main process exited, code=exited, status=24/n/a systemd[1]: memstrack.service: Failed with result 'exit-code'. systemd[1]: Starting dracut cmdline hook... Version-Release number of selected component (if applicable): memstrack-0.2.4-2.el8 RHEL-8.8.0-20230126.17 on hpe-apache-cn99xx-08.khw4.lab.eng.bos.redhat.com How reproducible: always Steps to Reproduce: 1. grubby --args=rd.memdebug=5 --update-kernel=DEFAULT 2. reboot Actual results: memstrack failed to report kernel module memory usage. Expected results: memstrack should report kernel module memory usage. Additional info: 1. This issue can be both observed on both the latest kernel 4.18.0-452.el8.aarch64 as of writing and 4.18.0-372.12.1.el8_6.aarch64 which was released about half a year ago 2. This bug can also be reproduced on aarch64 RHEL9 3. memstrack works well in kdump kernel 4. memstrack works fine in other architectures like x86 and s390