Debian Codegraph @

man/error::pass5.7stap

raw
1 .\" t
2 .TH ERROR::PASS5 7stap
3 .SH NAME
4 error::pass5 \- systemtap pass-5 errors
5
6 .SH DESCRIPTION
7 Errors that occur during pass 5 (execution) can have a variety of causes.
8
9 .TP
10 exceptional events during script execution
11 The systemtap translator and runtime include numerous error checks
12 that aim to protect the systems and the users from mistakes or
13 transient conditions. The script may deliberately call the
14 .IR error()
15 tapset function to signal a problem. Some memory needed for
16 accessing
17 .IR $context
18 variables may be temporarily unavailable. Consider using the
19 .IR try / catch
20 construct to wrap script fragments in exception-handling code.
21 Consider using the
22 .IR "stap --suppress-handler-errors"
23 or
24 .IR "stap --skip-badvars"
25 option.
26
27 .TP
28 resource exhaustion
29 One of several types of space or time resource limits may be
30 exceeded by the script, including system overload, too many tuples
31 to be stored in an array, etc. Some of the error messages identify
32 the constraint by macro name, which may be individually raised.
33 Consider using the
34 .IR "stap --suppress-handler-errors"
35 and/or
36 .IR "stap -g --suppress-time-limits"
37 options. Extend or disable individual resource limits using the
38 .IR "stap -DSOME_LIMIT=NNNN"
39 option. The
40 .IR "stap -t"
41 option may identify those probes that are taking too long.
42 .\" the systemtap/wiki/TipExhaustedResourceErrors should be transcribed here
43
44 .TP
45 remote execution server problems
46 If you use the
47 .IR "stap --remote"
48 option to direct a systemtap script to be executed somewhere else,
49 ensure that an SSH connection may be made to the remote host, and
50 that it has the current systemtap runtime installed & available.
51
52 .TP
53 kernel version incompatibility
54 If you see a "Couldn't insert module ..." error message when running
55 the script, the version of the kernel development tree selected by
56 stap (or the user via the \fI\-r\fP option) may not have matched that
57 of the actual running kernel. This can happen more easily if you run
58 handbuilt kernels. Check \fBdmesg\fP output for hints.
59
60 .TP
61 installation/permission problems
62 It is possible that your copy of systemtap was not correctly
63 installed. For example, the
64 .IR /usr/bin/staprun
65 program may lack the necessary setuid permissions, or your invoking
66 userid might not have sufficient privileges (root, or
67 .IR stapusr
68 and related group memberships). Environment
69 variables may interfere with locating
70 .IR /usr/libexec/.../stapio "."
71
72 .TP
73 security configuration
74 SecureBoot or other module signing machinery may be in effect,
75 preventing \fB.ko\fR module loading. A local or remote
76 .IR stap-server
77 service would be necessary to securely manage keys. This situation
78 is detected automatically on most kernels, but on some, the
79 .IR SYSTEMTAP_SIGN
80 environment varible may have to be set to trigger this extra
81 signing-related processing. Check \fBdmesg\fP output for hints.
82
83 The normal kernel-module based systemtap backend may be more than
84 your script requires. Try
85 .nh
86 .IR "stap\ --runtime=bpf " and/or " stap\ --runtime=dyninst"
87 .hy
88 backends. Though they have inherent limitations, they operate
89 with lesser privileges and perceived risks.
90
91 It may be possible to disable secure/lockdown measures temporarily
92 with the SysRQ+x keystroke, or permanently with
93 .nh
94 .IR "sudo\ mokutil\ --disable-validation"
95 .hy
96 and a reboot.
97
98 .TP
99 errors from target program
100 The program invoked by the
101 .IR "stap -c CMD"
102 option may exit with a non-zero code.
103
104 .TP
105 uncaught exceptions in the target program
106 When using
107 .IR --runtime=dyninst
108 you may encounter an issue where the target program aborts with a
109 message like "terminate called after throwing an instance
110 of 'foo_exception'". This is unfortunately a limitation of Dyninst,
111 which sometimes prevents exceptions from properly unwinding through
112 instrumented code.
113
114
115 .SH GATHERING MORE INFORMATION
116 Increasing the verbosity of pass-5
117 with an option such as
118 .IR "--vp 00001"
119 can help pinpoint the problem. See also:
120 .IR "dmesg"
121 on the relevant machines.
122
123
124 .SH SEE ALSO
125 .nh
126 .nf
127 .IR stap (1),
128 .IR http://sourceware.org/systemtap/wiki/TipExhaustedResourceErrors ,
129 .IR error::fault (7stap),
130 .IR error::reporting (7stap)
131 .IR warning::pass5 (7stap)