trAvis - MANAGER

Edit File: Tracing.html

<html>
<head>
<title>ProFTPD mini-HOWTO - ProFTPD Tracing</title>
</head>

<hr>
<center><h2>ProFTPD Tracing</h2></center>
<hr>

What is Tracing? 
"Tracing" is a new form of logging, introduced in the 1.3.1 ProFTPD release
series.

Trace logging has the concept of multiple logging channels, each of
which has its own log level. Layers and APIs within the ProFTPD source
will tend to use their own channels. There is no limit to the number of
different log channels that can be supported.

Within a channel, the assumption is that lower log levels indicate higher
priority or importance. Or to look at it another way, the higher the log
level for channel, the more noisy that log channel might be. The lowest log
level is 1; there is no upper log level limit.

Why have this new form of logging, in addition to all the other kinds of logs
(e.g. <code>SystemLog</code>, <code>ExtendedLog</code>, etc)
that a <code>proftpd</code> daemon can currently produce? The usual
<code>SystemLog</code> of proftpd debug logging, at a high
<code>DebugLevel</code>, was becoming unreadable; it is difficult to find the
tidbits of knowledge amidst the other messages in that file. By separating
log messages into channels and levels, tracing gives the administrator a much
finer-grained control over the logging, given them a way of focusing the
logging more narrowly, so only the area of code of interest is logged.

Support for tracing is enabled by default. Use the
<code>--disable-trace</code> configure option, when compiling ProFTPD, to
disable all tracing support. I recommend that high-traffic production sites,
which have no need for debug logging at this granularity, use the
<code>--disable-trace</code> option.

Configuration Directives 
There are two new configuration directives for tracing: <code>TraceLog</code>
and <code>Trace</code>. Note that for tracing to be effective, these
two directives, if used, must appear at the start of your
<code>proftpd.conf</code> file, before any other directives.

The <code>TraceLog</code> directive specifies a filename to which to write
the tracing log messages. For example:
<pre>
 TraceLog /var/ftpd/trace.log
</pre>
Without this directive, no trace logging will occur.

Once you have configured your <code>TraceLog</code>, you will use the
<code>Trace</code> directive to control the verbosity of that log:
<pre>
 Trace channel1:level1 channel2:level2 ...
</pre>
This directive lets you set each log channel and its level differently,
e.g.:
<pre>
 Trace command:5 response:8 timer:2 config:9
</pre>
There is also support for a special "DEFAULT" keyword:
<pre>
 Trace DEFAULT:10
</pre>
The following is the list of channels which are covered by the "DEFAULT"
keyword:
<ul>
 <li>auth
 <li>binding
 <li>command
 <li>config
 <li>ctrls
 <li>data
 <li>delay
 <li>dns
 <li>dso
 <li>encode
 <li>event
 <li>facl
 <li>fsio
 <li>ident
 <li>inet
 <li>lock
 <li>netacl
 <li>netio
 <li>pam
 <li>pool
 <li>regexp
 <li>response
 <li>scoreboard
 <li>signal
 <li>site
 <li>timer
 <li>var
</ul>
This means that if you use the following in your <code>proftpd.conf</code>
file, at the very top:
<pre>
 TraceLog /path/to/ftpd/trace.log
 Trace DEFAULT:10
</pre>
Then all of the above channels, up to log level 10, will have their
messages logged.

If you want to look at the default trace channels except for a
particular channel, use level 0 to effectively disable that channel.
For example, to exclude the "fsio" channel but see the rest of the default
channels, you would use:
<pre>
 Trace DEFAULT:10 fsio:0
</pre>

Note that there are trace channel names that are not part of the
"DEFAULT" channel name list (e.g. "class"); any custom channel names,
such as might be used by a third-party module, are also not covered in the
"DEFAULT" list. For example, the <code>mod_tls</code> module may log to a
"tls" channel. Any messages to that "tls" channel would not appear in the
<code>TraceLog</code> file, using the above configuration. Instead,
you would need to explicitly mention the "tls" channel, i.e.:
<pre>
 TraceLog /path/to/ftpd/trace.log
 Trace DEFAULT:10 tls:10
</pre>

Optional Trace Log Channels 
In addition to the default trace log channels listed above, there are
optional trace log channels:
<ul>
 <li><code>directory</code>
 
 The "directory" log channel is used when the core engine attempts
 to find the closest matching <code>&lt;Directory&gt;</code> section
 for a path.
 </li>

<li><code>fileperms</code>
 
 The "fileperms" log channel is used whenever a user action involving
 the filesystem (e.g. opening/closing/writing/renaming/deleting
 files or directories) fails. This channel will log the relevant FTP
 command, user name, UID/GID, filesystem path, and the error.
 </li>
</ul>

Trace Log Format 
Every log message in a <code>TraceLog</code> uses the following format:
<pre>
 timestamp [process ID] &lt;channel:level&gt;: message
</pre>
For example:
<pre>
 Jan 16 17:15:58 [30583] &lt;auth:6&gt;: dispatching auth request "endgrent" to module mod_auth_unix
</pre>
This shows process ID 30583 logging to the "auth" channel, log level 6, a
message about handling the "endgrent" Auth API request.

<a name="RuntimeTuning">
Runtime Tracing 
If Controls support is enabled in your <code>proftpd</code>, and
you are using the <code>mod_ctrls_admin</code> module, then you can also use the
<code>ftpdctl</code> command to adjust the trace logging settings in the
running <code>proftpd</code>, without needing to change your
<code>proftpd.conf</code> file. See:
<pre>
 <a href="../contrib/mod_ctrls_admin.html#trace">doc/contrib/mod_ctrls_admin.html#trace</a>
</pre>
for more information on the <code>ftpdctl trace</code> action.

Here's a concrete example of how tuning the trace logging at runtime can be
useful. You may need the extra information logged via trace logging in order
to track down/debug some issue, but you do not want to enable trace
logging all of the time in your environment. Fortunately, it is possible
to make it possible to get the trace logging information you need, when
you need to get it, and then turn the trace logging off all without
restarting proftpd.

First, you need to configure your <code>proftpd.conf</code> like so:
<pre>
 TraceLog /path/to/proftpd/trace.log
 Trace DEFAULT:0
</pre>
This configuration tells proftpd to direct all trace logging to that
<code>TraceLog</code> file, but to not actually write anything to the
file; the log level zero (0) filters out all trace logging messages. Start
proftpd with the updated <code>proftpd.conf</code>. Later, while proftpd is
running, you can tune the tracing using the
<a href="Controls.html"><code>ftpdctl</code></a> utility, like this:
<pre>
 # ftpdctl trace lock:10 scoreboard:5
</pre>
which dynamically changes the 'lock' trace channel level to 10, and the
'scoreboard' trace channel level to 5. Once you have gathered the necessary
information in the <code>TraceLog</code> file, you then use <code>ftpdctl</code>
again and restore the trace levels back to zero, effectively turning off
trace logging once more:
<pre>
 # ftpdctl trace DEFAULT:0
</pre>
Note that the changed settings will only apply to new sessions; this
does not change the trace logging for existing sessions.

Use Only When Needed 
Remember that tracing is a verbose (and thus expensive) form of logging,
and thus makes the <code>proftpd</code> daemon run slower. Tracing should only
ever be used for debugging and development purposes; once your
<code>proftpd</code> is up and running the way you need, you should remove all
<code>Trace</code> and <code>TraceLog</code> directives from your
<code>proftpd.conf</code>.

<a name="FAQ">
Frequently Asked Questions

Question: Can I configure <code>Trace</code> on a
per-user basis, using <code>mod_ifsession</code>'s <code>&lt;IfUser&gt;</code>? 
Answer: You can indeed use <code>mod_ifsession</code>
for <code>Trace</code> configurations, starting in ProFTPD 1.3.4rc1. To
do this, you need to use the optional "session" keyword in your
<code>Trace</code> configuration, e.g.:
<pre>
 &lt;IfUser traced-user&gt;
 Trace session DEFAULT:10
 &lt;/IfUser&gt;
</pre>
This goes for <code>&lt;IfClass&gt;</code> and <code>&lt;IfGroup&gt;</code>
sections as well.

<hr>
$Date: 2012-09-27 17:52:36 $

</body>
</html>