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:
On RHEL-9 (tested on RHEL-9.0.0-20220102.3 with trace-cmd-2.9.2-8.el9.x86_64) 'trace-cmd report' is giving this error message:
"No such file or directory
Error: expected type 4 but read 5"
Reproducer:
trace-cmd record -e sched:sched_wakeup sleep 1
CPU0 data recorded at offset=0x6c9000
4096 bytes in size
trace-cmd report > trace-cmd.report
trace-cmd: No such file or directory
Error: expected type 4 but read 5
The report is created and seems to be complete. Also, the return status is 0. It looks that the reported error is not critical.
On RHEL-8, no such error is reported.
On Fedora 34, I'm getting the same error as in RHEL-9.
Version-Release number of selected component (if applicable):
trace-cmd-2.9.2-8.el9.x86_64
How reproducible:
Always.
Steps to Reproduce:
1.trace-cmd record -e sched:sched_wakeup sleep 1
2.trace-cmd report > trace-cmd.report
3.
Actual results:
trace-cmd: No such file or directory
Error: expected type 4 but read 5
Expected results:
The same behavior as on RHEL-8: no error reported.
Additional info:
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 (new packages: libtraceevent), 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:4031
Description of problem: On RHEL-9 (tested on RHEL-9.0.0-20220102.3 with trace-cmd-2.9.2-8.el9.x86_64) 'trace-cmd report' is giving this error message: "No such file or directory Error: expected type 4 but read 5" Reproducer: trace-cmd record -e sched:sched_wakeup sleep 1 CPU0 data recorded at offset=0x6c9000 4096 bytes in size trace-cmd report > trace-cmd.report trace-cmd: No such file or directory Error: expected type 4 but read 5 The report is created and seems to be complete. Also, the return status is 0. It looks that the reported error is not critical. On RHEL-8, no such error is reported. On Fedora 34, I'm getting the same error as in RHEL-9. Version-Release number of selected component (if applicable): trace-cmd-2.9.2-8.el9.x86_64 How reproducible: Always. Steps to Reproduce: 1.trace-cmd record -e sched:sched_wakeup sleep 1 2.trace-cmd report > trace-cmd.report 3. Actual results: trace-cmd: No such file or directory Error: expected type 4 but read 5 Expected results: The same behavior as on RHEL-8: no error reported. Additional info: