Author: buildbot
Date: Mon May 16 23:01:50 2011
New Revision: 789665
Log:
Staging update by buildbot
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/event-logging-formats/index.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-line-commands/index.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-server-error-messages/index.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/working-log-files/index.en.html
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
Mon May 16 23:01:50 2011
@@ -1524,6 +1524,8 @@ disk.</p>
</dd>
<dd>
<p>The amount of space allocated to the logging directory (in MB).</p>
+<p><strong>Note:</strong> All files in the logging directory contribute
+to the space used, even if they are not log files.</p>
</dd>
<dt
id="proxy.config.log.max_space_mb_for_orphan_logs"><em><code>proxy.config.log.max_space_mb_for_orphan_logs</code></em></dt>
<dd>
@@ -1565,10 +1567,12 @@ directory is less than the value specifi
<p><code>STRING</code></p>
</dd>
<dd>
-<p>Default: <code>*install_dir*``/logs</code></p>
+<p>Default: <em><code>install_dir</code></em><code>/logs</code></p>
</dd>
<dd>
<p>The full path to the logging directory.</p>
+<p>This can be an absolute path or a path relative to the directory in which
Traffic Server is installed.</p>
+<p><strong>Note:</strong> The directory you specify must already exist.</p>
</dd>
<dt
id="proxy.config.log.logfile_perm"><em><code>proxy.config.log.logfile_perm</code></em></dt>
<dd>
@@ -1789,6 +1793,11 @@ format.</p>
<dd>
<p>When enabled (<code>1</code>), configures Traffic Server to store ICP
transactions in a separate log file.</p>
+<ul>
+<li><code>0</code> = separation is disabled, all ICP transactions are recorded
in the same file as HTTP transactions</li>
+<li><code>1</code> = all ICP transactions are recorded in a separate log
file.</li>
+<li><code>-1</code> = filter all ICP transactions from the default log files;
ICP transactions are not logged anywhere.</li>
+</ul>
</dd>
<dt
id="proxy.config.log.separate_host_logs"><em><code>proxy.config.log.separate_host_logs</code></em></dt>
<dd>
@@ -1919,6 +1928,8 @@ values:</p>
<dd>
<p>The log file rolling interval, in seconds. The minimum value is
<code>300</code> (5 minutes). The maximum value is 86400 seconds (one day).</p>
+<p><strong>Note:</strong> If you start Traffic Server within a few minutes of
the next rolling time,
+then rolling might not occur until the next rolling time.</p>
</dd>
<dt
id="proxy.config.log.rolling_offset_hr"><em><code>proxy.config.log.rolling_offset_hr</code></em></dt>
<dd>
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/event-logging-formats/index.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/admin/event-logging-formats/index.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/admin/event-logging-formats/index.en.html
Mon May 16 23:01:50 2011
@@ -97,7 +97,7 @@ since January 1, 1970 UTC. Time is expre
<dd>The client request timestamp. The time of the client request in the format
hh:mm:ss, where hh is the two-digit hour in 24-hour format, mm is the
two-digit
minutes value, and ss is the 2-digit seconds value (for example, 16:01:19).
</dd>
-<dt><code>cqtx</code></dt>
+<dt id="cqtx"><code>cqtx</code></dt>
<dd>
<p>The full HTTP client request text, minus headers; for example, </p>
<div class="codehilite"><pre> <span class="n">GET</span> <span
class="n">http:</span><span class="sr">//</span><span class="n">www</span><span
class="o">.</span><span class="n">company</span><span class="o">.</span><span
class="n">com</span> <span class="n">HTTP</span><span class="o">/</span><span
class="mf">1.0</span>
@@ -105,20 +105,16 @@ minutes value, and ss is the 2-digit sec
<p>In reverse proxy mode, Traffic Server logs the rewritten/mapped URL
(according
-to the rules in the <code>remap.config</code> file), and _ not_ the
pristine/unmapped
-URL. To configure Traffic Server to log the original, unmapped URL, set the
-variable <code>_proxy.config.url_remap.pristine_host_hdr _</code> in the
<code>records.config</code>
-file to <code>1</code> .</p>
+to the rules in the <a
href="../configuration-files/remap.config"><code>remap.config</code></a> file),
and _not _ the pristine/unmapped
+URL. To configure Traffic Server to log the original, unmapped URL, set the
variable
+<a
href="../configuration-files/records.config#proxy.config.url_remap.pristine_host_hdr"><em><code>proxy.config.url_remap.pristine_host_hdr</code></em></a>
+in the <a
href="../configuration-files/records.config"><code>records.config</code></a>
file to <code>1</code> .</p>
</dd>
<dt><code>cqu</code></dt>
<dd>
<p>The universal resource identifier (URI) of the request from client to
Traffic
Server (subset of <code>cqtx</code> ).</p>
-<p>In reverse proxy mode, Traffic Server logs the rewritten/mapped URL
(according
-to the rules in the <code>remap.config</code> file), and _ not _ the
pristine/unmapped
-URL. To configure Traffic Server to log the original, unmapped URL, set the
-variable <code>_proxy.config.url_remap.pristine_host_hdr _</code> in the
<code>records.config</code>
-file to <code>1</code> .</p>
+<p>See the description of <a href="#cqtx"><code>cqtx</code></a> for behaviour
in reverse proxy mode.</p>
</dd>
<dt><code>cquc</code></dt>
<dd>
@@ -126,16 +122,12 @@ file to <code>1</code> .</p>
other characters that might not be parsed by log analysis tools) are replaced
by escape sequences. The escape sequence is a percentage sign followed by the
ASCII code number in hex.</p>
-<p>In reverse proxy mode, Traffic Server logs the rewritten/mapped URL
(according
-to the rules in the <code>remap.config</code> file), and <em>not</em> the
pristine/unmapped
-URL. To configure Traffic Server to log the original (unmapped) URL, set the
-<em><code>proxy.config.url_remap.pristine_host_hdr</code></em> variable in the
<code>records.config</code>
-file to <code>1</code> .</p>
+<p>See the description of <a href="#cqtx"><code>cqtx</code></a> for behaviour
in reverse proxy mode.</p>
</dd>
<dt><code>cqup</code></dt>
<dd>
<p>The client request URL path; specifies the argument portion of the URL
(everything after the host).
- For example, if the URL is <code>http://www.company.com/images/x.gif</code> ,
then this field displays <code>/images/x.gif</code></p>
+ For example, if the URL is <code>http://www.company.com/images/x.gif</code>,
then this field displays <code>/images/x.gif</code></p>
</dd>
<dt><code>cqus</code></dt>
<dd>
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html
Mon May 16 23:01:50 2011
@@ -191,7 +191,7 @@ and origin server connections, you must
</ul>
</li>
</ul>
-<h5
id="to_configure_ssl_termination_for_traffic_serverorigin_server_connections___configuresslterminationfortsoriginserverconnections">To
configure SSL termination for Traffic Server/origin server connections: #####
{#configureSSLterminationforTS/originserverconnections}</h5>
+<h5 id="configureSSLterminationforTSoriginserverconnections">To configure SSL
termination for Traffic Server/origin server connections:</h5>
<ol>
<li>Edit the following variables in the <code>SSL Termination</code> section
of the <code>records.config</code> file: <ul>
<li><a
href="../configuration-files/records.config#proxy.config.ssl.auth.enabled"><em><code>proxy.config.ssl.auth.enabled</code></em></a></li>
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-line-commands/index.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-line-commands/index.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-line-commands/index.en.html
Mon May 16 23:01:50 2011
@@ -55,40 +55,40 @@ path, then prepend the Traffic Line comm
<code>./traffic_line -p</code>).</p>
<p>The following list describes all the commands available in Traffic Line.</p>
<dl>
-<dt><code>traffic_line -b</code></dt>
+<dt><code>-b</code></dt>
<dd>Bounces Traffic Server on the local node. Bouncing Traffic Server shuts
down
and immediately restarts the Traffic Server node.</dd>
-<dt><code>traffic_line -c</code></dt>
+<dt><code>-c</code></dt>
<dd>Clears accumulated statistics on the local node.</dd>
-<dt><code>traffic_line -h</code></dt>
+<dt><code>-h</code></dt>
<dd>Displays a list of Traffic Line commands.</dd>
-<dt><code>traffic_line -p</code> <em><code>socket_path</code></em></dt>
+<dt><code>-p</code> <em><code>socket_path</code></em></dt>
<dd>Specifies location (directory and path) of the socket used for Traffic
Line communication.<br />
The default path is:
<em><code>install_dir</code></em><code>/config/cli</code></dd>
-<dt><code>traffic_line -r _variable_</code></dt>
+<dt><code>-r _variable_</code></dt>
<dd>Displays specific performance statistics or a current configuration
setting.
For a list of the variables you can specify, see <a
href="#TrafficLineVariables">Traffic Line Variables</a>.</dd>
-<dt><code>traffic_line -s</code> <em><code>variable</code></em>
<code>-v</code> <em><code>value</code></em></dt>
+<dt><code>-s</code> <em><code>variable</code></em> <code>-v</code>
<em><code>value</code></em></dt>
<dd>Sets configuration variables, where <em><code>variable</code></em> is the
configuration variable
you want to change and <em><code>value</code></em> is the value you want to
set. Refer to <a href="../configuration-files/records.config">records.config</a>
for a list of the configuration variables you can specify.</dd>
-<dt><code>traffic_line -x</code></dt>
+<dt><code>-x</code></dt>
<dd>Initiates a Traffic Server configuration file reread. Use this command
after
every configuration file modification.</dd>
-<dt><code>traffic_line -B</code></dt>
+<dt><code>-B</code></dt>
<dd>Bounces all Traffic Server nodes in the cluster. Bouncing Traffic Server
shuts
down and immediately restarts Traffic Server, node-by-node.</dd>
-<dt><code>traffic_line -C</code></dt>
+<dt><code>-C</code></dt>
<dd>Clears accumulated statistics on all nodes in the cluster.</dd>
-<dt><code>traffic_line -L</code></dt>
+<dt><code>-L</code></dt>
<dd>Restarts the <code>traffic_manager</code> and <code>traffic_server</code>
processes on the local
node.</dd>
-<dt><code>traffic_line -M</code></dt>
+<dt><code>-M</code></dt>
<dd>Restarts the <code>traffic_manager</code> process and the
<code>traffic_server</code> process
on all the nodes in a cluster.</dd>
-<dt><code>traffic_line -S</code></dt>
+<dt><code>-S</code></dt>
<dd>Shuts down Traffic Server on the local node.</dd>
-<dt><code>traffic_line -U</code></dt>
+<dt><code>-U</code></dt>
<dd>Starts Traffic Server on the local node.</dd>
</dl>
<h1 id="TrafficLineVariables">Traffic Line Variables</h1>
@@ -272,11 +272,9 @@ following table. To view a statistic in
</dl>
<h3 id="TLVarsCongestionControl">Congestion Control</h3>
<dl>
-<dt>Number of congestions Traffic Server has observed because the maximum
number</dt>
-<dt>of connections was exceeded.</dt>
+<dt>Number of congestions Traffic Server has observed because the maximum
number of connections was exceeded.</dt>
<dd><em><code>proxy.process.congestion.congested_on_max_connection</code></em></dd>
-<dt>Number of congestions Traffic Server has observed because of an OS
response</dt>
-<dt>or timeout failure.</dt>
+<dt>Number of congestions Traffic Server has observed because of an OS
response or timeout failure.</dt>
<dd><em><code>proxy.process.congestion.congested_on_conn_failures</code></em></dd>
</dl>
</div>
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-server-error-messages/index.en.html
==============================================================================
---
websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-server-error-messages/index.en.html
(original)
+++
websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-server-error-messages/index.en.html
Mon May 16 23:01:50 2011
@@ -52,7 +52,6 @@
list is not exhaustive; it simply describes common warning messages that can
occur and which might require your attention.</p>
<h3 id="TSProcessFatal">Traffic Server Process Fatal</h3>
-<p><strong>Message</strong> <strong>Description</strong></p>
<dl>
<dt><code>Accept port is not between 1 and 65535. Please check
configuration</code></dt>
<dd>The port specified in the <code>records.config</code> file that accepts
incoming HTTP
@@ -92,7 +91,7 @@ errors. The disk might be corrupt and mi
<dt><code>No cache disks specified in storage.config file: cache
disabled</code></dt>
<dd>The Traffic Server <code>storage.config</code> file does not list any
cache disks; Traffic
Server is running in proxy-only mode. You must add the disks you want to use
-for the cache to the <a href="files.htm#storage.config">storage.config</a>
file.</dd>
+for the cache to the <a
href="../configuration-files/storage.config">storage.config</a> file.</dd>
</dl>
<h2 id="TSAlarmMessages">Traffic Server Alarm Messages</h2>
<dl>
@@ -125,7 +124,7 @@ file.</dd>
<dd>Check permissions for the indicated file and the logging directory.</dd>
<dt><code>Traffic Server failed to parse line</code>
<em><code>line_number</code></em> <code>of the logging config file</code>
<em><code>filename</code></em></dt>
<dd>Check your custom log configuration file; there could be syntax errors.
Refer
-to <a href="logfmts.htm#66912"> Custom Logging Fields</a> for correct custom
log format
+to <a href="logfmts.htm#66912">Custom Logging Fields</a> for correct custom
log format
fields.</dd>
<dt><code>vip_config binary is not setuid root, manager will be unable to
enable virtual ip addresses</code></dt>
<dd>The <code>traffic_manager</code> process is not able to set virtual IP
addresses. You
