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.
Cause
Probing a user-space application requires a uprobes kernel module.
The --remote option used the path to the uprobes kernel module
for the client rather than proper path on the remote machine.
Consequence
If a uprobes module was not already loaded on the remote machine,
the instrumentation would not start and an error message like the following
would be printed:
ERROR: Unable to canonicalize path [...]: No such file or directory
Fix
Systemtap now properly communicates which uprobe module to load.
Result
User-space application probing will work properly with --remote option
even if uprobe kernel module not currently loaded on remote machine.
Description of problem:
When using --remote $HOST with a script that requires uprobes, systemtap will transfer uprobes.ko to be loaded on the remote. However, the command to run attempts to use a full path on the client, rather than somewhere on the remote.
Version-Release number of selected component (if applicable):
systemtap-1.6-1.el6
How reproducible:
100%
Steps to Reproduce:
1. Need two similar machines, $CLIENT and $REMOTE
2. On $REMOTE, rmmod uprobes if it's already loaded
3. Run stap from the $CLIENT, something that needs uprobes, e.g.
stap -e 'probe process.mark("*") { println(pn()) }' -c 'stap -l begin' \
--remote $REMOTE
Actual results:
ERROR: Unable to canonicalize path [...]: No such file or directory
(where [...] is a temp path on the $CLIENT)
Expected results:
Successful run, and uprobes will be loaded on the $REMOTE afterward.
Additional info:
I already fixed it upstream:
http://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commit;h=18630fb81ed5433b31ae583694424cc0aed3123a
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause
Probing a user-space application requires a uprobes kernel module.
The --remote option used the path to the uprobes kernel module
for the client rather than proper path on the remote machine.
Consequence
If a uprobes module was not already loaded on the remote machine,
the instrumentation would not start and an error message like the following
would be printed:
ERROR: Unable to canonicalize path [...]: No such file or directory
Fix
Systemtap now properly communicates which uprobe module to load.
Result
User-space application probing will work properly with --remote option
even if uprobe kernel module not currently loaded on remote machine.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1517.html
Description of problem: When using --remote $HOST with a script that requires uprobes, systemtap will transfer uprobes.ko to be loaded on the remote. However, the command to run attempts to use a full path on the client, rather than somewhere on the remote. Version-Release number of selected component (if applicable): systemtap-1.6-1.el6 How reproducible: 100% Steps to Reproduce: 1. Need two similar machines, $CLIENT and $REMOTE 2. On $REMOTE, rmmod uprobes if it's already loaded 3. Run stap from the $CLIENT, something that needs uprobes, e.g. stap -e 'probe process.mark("*") { println(pn()) }' -c 'stap -l begin' \ --remote $REMOTE Actual results: ERROR: Unable to canonicalize path [...]: No such file or directory (where [...] is a temp path on the $CLIENT) Expected results: Successful run, and uprobes will be loaded on the $REMOTE afterward. Additional info: I already fixed it upstream: http://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commit;h=18630fb81ed5433b31ae583694424cc0aed3123a