You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
values. If "<a href="#nbthread">nbthread</a>" is forced to a higher value, thread-hard-limit wins,
8165
8193
and a warning is emitted in so that the configuration anomaly can be
8166
8194
fixed. By default there is no limit. See also "<a href="#nbthread">nbthread</a>".
8167
-
</pre><a class="anchor" name="trace"></a><a class="anchor" name="3-trace"></a><a class="anchor" name="3.1-trace"></a><a class="anchor" name="trace (Global parameters)"></a><a class="anchor" name="trace (Process management and security)"></a><div class="keyword"><b><a class="anchor" name="trace"></a><a href="#3.1-trace">trace</a></b> <span style="color: #080"><args...></span></div><pre class="text">This command configures one "<a href="#trace">trace</a>" subsystem statement. Each of them can be
8168
-
found in the management manual, and follow the exact same syntax. Only one
8169
-
statement per line is permitted (i.e. if some long trace configurations using
8170
-
semi-colons are to be imported, they must be placed one per line). Any output
8171
-
that the "<a href="#trace">trace</a>" command would produce will be emitted during the parsing
8172
-
step of the section. Most of the time these will be errors and warnings, but
8173
-
certain incomplete commands might list permissible choices. This command is
8174
-
not meant for regular use, it will generally only be suggested by developers
8175
-
along complex debugging sessions. For this reason it is internally marked as
8176
-
experimental, meaning that "<a href="#expose-experimental-directives">expose-experimental-directives</a>" must appear on a
8177
-
line before any "<a href="#trace">trace</a>" statement. Note that these directives are parsed on
8178
-
the fly, so referencing a ring buffer that is only declared further will not
8179
-
work. For such use cases it is suggested to place another "global" section
8180
-
with only the "<a href="#trace">trace</a>" statements after the declaration of that ring. It is
8181
-
important to keep in mind that depending on the trace level and details,
8182
-
enabling traces can severely degrade the global performance. Please refer to
8183
-
the management manual for the statements syntax.
8184
8195
</pre><a class="anchor" name="uid"></a><a class="anchor" name="3-uid"></a><a class="anchor" name="3.1-uid"></a><a class="anchor" name="uid (Global parameters)"></a><a class="anchor" name="uid (Process management and security)"></a><div class="keyword"><b><a class="anchor" name="uid"></a><a href="#3.1-uid">uid</a></b> <span style="color: #080"><number></span></div><pre class="text">Changes the process's user ID to <number>. It is recommended that the user ID
8185
8196
is dedicated to HAProxy or to a small set of similar daemons. HAProxy must
8186
8197
be started with superuser privileges in order to be able to switch to another
<div><pre class="text">For debugging purpose, it is possible to activate traces on an HAProxy's
9354
+
subsystem. This will dump debug messages about a specific subsystem. It is a
9355
+
very powerful tool to diagnose issues. Traces can be dynamically configured via
9356
+
the CLI. It is also possible to predefined some settings in the configuration
9357
+
file, in dedicated "<a href="#traces">traces</a>" sections. More details about traces can be found in
9358
+
the management guide. It remains a developper tools used during complex
9359
+
debugging sessions. It is pretty verbose and have a cost, so use it with
9360
+
caution. And because it is a developper tool, there is no warranty about the
9361
+
backward compatibility of this section.
9362
+
</pre><a class="anchor" name="traces"></a><a class="anchor" name="3-traces"></a><a class="anchor" name="3.3.1-traces"></a><a class="anchor" name="traces (Global parameters)"></a><a class="anchor" name="traces (Traces)"></a><div class="keyword"><b><a class="anchor" name="traces"></a><a href="#3.3.1-traces">traces</a></b></div><pre class="text">Starts a new traces section. One or multiple "<a href="#traces">traces</a>" section may be
9363
+
used. All direcitives are evaluated in the declararion order, the last ones
9364
+
overriding previous ones.
9365
+
</pre><a class="anchor" name="trace"></a><a class="anchor" name="3-trace"></a><a class="anchor" name="3.3.1-trace"></a><a class="anchor" name="trace (Global parameters)"></a><a class="anchor" name="trace (Traces)"></a><div class="keyword"><b><a class="anchor" name="trace"></a><a href="#3.3.1-trace">trace</a></b> <span style="color: #080"><source></span> <span style="color: #080"><args...></span></div><pre class="text">Configures on "<a href="#trace">trace</a>" subsystem. Each of them can be found in the management
9366
+
manual, and follow the exact same syntax. Any output that the "<a href="#trace">trace</a>"
9367
+
command would produce will be emitted during the parsing step of the
9368
+
section. Most of the time these will be errors and warnings, but certain
9369
+
incomplete commands might list permissible choices. This command is not meant
9370
+
for regular use, it will generally only be suggested by developers along
9371
+
complex debugging sessions. Note that these directives are parsed on the fly,
9372
+
so referencing a ring buffer that is only declared further will not work. It
9373
+
is important to keep in mind that depending on the trace level and details,
9374
+
enabling traces can severely degrade the global performance. Please refer to
9375
+
the management manual for the statements syntax.
9376
+
</pre><div class="separator">
9377
+
<span class="label label-success">Example:</span>
9378
+
<pre class="prettyprint">
9379
+
<code>ring buf1
9380
+
size 10485760 <span class="comment"># 10MB</span>
9381
+
format timed
9382
+
backing-file /tmp/h1.traces
9383
+
9384
+
ring buf2
9385
+
size 10485760 <span class="comment"># 10MB</span>
9386
+
format timed
9387
+
backing-file /tmp/h2.traces
9388
+
9389
+
traces
9390
+
trace h1 sink buf1 level developer verbosity complete start now
9391
+
trace h2 sink buf1 level developer verbosity complete start now
0 commit comments