|
HTML rendering created 2025-09-06 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|
|
NAME | DESCRIPTION | GATHERING MORE INFORMATION | SEE ALSO | COLOPHON |
|
|
|
ERROR::PASS5(7stap) ERROR::PASS5(7stap)
error::pass5 - systemtap pass-5 errors
Errors that occur during pass 5 (execution) can have a variety of
causes.
exceptional events during script execution
The systemtap translator and runtime include numerous error
checks that aim to protect the systems and the users from
mistakes or transient conditions. The script may
deliberately call the error() tapset function to signal a
problem. Some memory needed for accessing $context
variables may be temporarily unavailable. Consider using
the try/catch construct to wrap script fragments in
exception-handling code. Consider using the stap
--suppress-handler-errors or stap --skip-badvars option.
resource exhaustion
One of several types of space or time resource limits may
be exceeded by the script, including system overload, too
many tuples to be stored in an array, etc. Some of the
error messages identify the constraint by macro name, which
may be individually raised. Consider using the stap
--suppress-handler-errors and/or stap -g --suppress-time-
limits options. Extend or disable individual resource
limits using the stap -DSOME_LIMIT=NNNN option. The stap
-t option may identify those probes that are taking too
long.
remote execution server problems
If you use the stap --remote option to direct a systemtap
script to be executed somewhere else, ensure that an SSH
connection may be made to the remote host, and that it has
the current systemtap runtime installed & available.
kernel version incompatibility
If you see a "Couldn't insert module ..." error message
when running the script, the version of the kernel
development tree selected by stap (or the user via the -r
option) may not have matched that of the actual running
kernel. This can happen more easily if you run handbuilt
kernels. Check dmesg output for hints.
installation/permission problems
It is possible that your copy of systemtap was not
correctly installed. For example, the /usr/bin/staprun
program may lack the necessary setuid permissions, or your
invoking userid might not have sufficient privileges (root,
or stapusr and related group memberships). Environment
variables may interfere with locating
/usr/libexec/.../stapio.
security configuration
SecureBoot or other module signing machinery may be in
effect, preventing .ko module loading. A local or remote
stap-server service would be necessary to securely manage
keys. This situation is detected automatically on most
kernels, but on some, the SYSTEMTAP_SIGN environment
varible may have to be set to trigger this extra signing-
related processing. Check dmesg output for hints.
The normal kernel-module based systemtap backend may be
more than your script requires. Try stap --runtime=bpf
and/or stap --runtime=dyninst backends. Though they have
inherent limitations, they operate with lesser privileges
and perceived risks.
It may be possible to disable secure/lockdown measures tem‐
porarily with the SysRQ+x keystroke, or permanently with
sudo mokutil --disable-validation and a reboot.
errors from target program
The program invoked by the stap -c CMD option may exit with
a non-zero code.
uncaught exceptions in the target program
When using --runtime=dyninst you may encounter an issue
where the target program aborts with a message like "termi‐
nate called after throwing an instance of 'foo_exception'".
This is unfortunately a limitation of Dyninst, which some‐
times prevents exceptions from properly unwinding through
instrumented code.
Increasing the verbosity of pass-5 with an option such as --vp
00001 can help pinpoint the problem. See also: dmesg on the rele‐
vant machines.
stap(1),
http://sourceware.org/systemtap/wiki/TipExhaustedResourceErrors ,
error::fault(7stap),
error::reporting(7stap)
warning::pass5(7stap)
This page is part of the systemtap (a tracing and live-system
analysis tool) project. Information about the project can be
found at ⟨https://sourceware.org/systemtap/⟩. If you have a bug
report for this manual page, send it to [email protected].
This page was obtained from the project's upstream Git repository
⟨git://sourceware.org/git/systemtap.git⟩ on 2025-08-11. (At that
time, the date of the most recent commit that was found in the
repository was 2025-07-24.) If you discover any rendering
problems in this HTML version of the page, or you believe there is
a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
[email protected]
ERROR::PASS5(7stap)
Pages that refer to this page: warning::pass5(7stap)
|
HTML rendering created 2025-09-06 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|