You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by bu...@apache.org on 2011/03/25 00:49:56 UTC
svn commit: r787487 - in
/websites/staging/trafficserver/trunk/content/docs/trunk/admin:
configuration-files/ traffic-server-error-messages/ working-log-files/
Author: buildbot
Date: Thu Mar 24 23:49:56 2011
New Revision: 787487
Log:
Staging update by buildbot
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/index.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/logs_xml.config.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/order.txt
websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.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/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/index.en.html Thu Mar 24 23:49:56 2011
@@ -47,7 +47,6 @@
<li><a href="icp.config">icp.config</a></li>
<li><a href="ip_allow.config">ip_allow.config</a></li>
<li><a href="log_hosts.config">log_hosts.config</a></li>
-<li><a href="logs.config">logs.config</a></li>
<li><a href="logs_xml.config">logs_xml.config</a></li>
<li><a href="parent.config">parent.config</a></li>
<li><a href="partition.config">partition.config</a></li>
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/logs_xml.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/logs_xml.config.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/logs_xml.config.en.html Thu Mar 24 23:49:56 2011
@@ -327,16 +327,16 @@ entries are sent to port 4000 of the col
<p>Traffic Server supports WELF (WebTrends Enhanced Log Format) so you
can analyze Traffic Server log files with WebTrends reporting
tools. A predefined <code><LogFormat></code> that is compatible with WELF is
-provided at the end of the <code>logs.config</code> file (shown below).
+provided in the <code>logs_xml.config</code> file (shown below).
To create a WELF format log file, create a <code><LogObject></code> that
uses this predefined format.</p>
<div class="codehilite"><pre> <span class="nt"><LogFormat></span>
<span class="nt"><Name</span> <span class="err">=</span> <span class="err">"welf"</span><span class="nt">/></span>
<span class="nt"><Format</span> <span class="err">=</span> <span class="err">"</span><span class="na">id=</span><span class="s">firewall</span> <span class="na">time=</span><span class="s">\"%<cqtd</span><span class="nt">></span> %<span class="nt"><cqtt></span>\" fw=%<span class="nt"><phn></span> pri=6
- proto=%<span class="nt"><cqus></span> duration=%<span class="nt"><ttmsf></span> sent=%<span class="nt"><psql></span> rcvd=%<span class="nt"><cqhl></span>
- src=%<span class="nt"><chi></span> dst=%<span class="nt"><shi></span> dstname=%<span class="nt"><shn></span> user=%<span class="nt"><caun></span> op=%<span class="nt"><cqhm></span>
- arg=\"%<span class="nt"><cqup></span>\" result=%<span class="nt"><pssc></span> ref=\"%<span class="err"><</span>{Referer}cqh>\"
- agent=\"%<span class="err"><</span>{user-agent}cqh>\" cache=%<span class="nt"><crc></span>"/>
+ proto=%<span class="nt"><cqus></span> duration=%<span class="nt"><ttmsf></span> sent=%<span class="nt"><psql></span> rcvd=%<span class="nt"><cqhl></span>
+ src=%<span class="nt"><chi></span> dst=%<span class="nt"><shi></span> dstname=%<span class="nt"><shn></span> user=%<span class="nt"><caun></span> op=%<span class="nt"><cqhm></span>
+ arg=\"%<span class="nt"><cqup></span>\" result=%<span class="nt"><pssc></span> ref=\"%<span class="err"><</span>{Referer}cqh>\"
+ agent=\"%<span class="err"><</span>{user-agent}cqh>\" cache=%<span class="nt"><crc></span>"/>
<span class="nt"></LogFormat></span>
</pre></div>
</div>
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/order.txt
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/order.txt (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/order.txt Thu Mar 24 23:49:56 2011
@@ -6,7 +6,6 @@ hosting.config
icp.config
ip_allow.config
log_hosts.config
-logs.config
logs_xml.config
parent.config
partition.config
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 Thu Mar 24 23:49:56 2011
@@ -1270,18 +1270,6 @@ T=SERVER_PORT_BLIND_TUNNEL</p>
<dd><code>INT</code></dd>
<dd><code>0</code></dd>
<dd>Enables (<code>1</code>) or disables (<code>0</code>) custom logging.</dd>
-<dt><em><code>proxy.config.log.xml_logs_config</code></em></dt>
-<dd><code>INT</code></dd>
-<dd><code>1</code></dd>
-<dd>Enables (<code>1</code>) or disables (<code>0</code>) extended custom logging using an</dd>
-</dl>
-<p>XML-based configuration file.<br />
- A value of <code>0</code> instructs Traffic Server to use the traditional
- custom log formats.</p>
-<p><strong>Note:</strong> Although Traffic Server supports traditional custom
- logging, you should use the more versatile XML-based custom
- formats.</p>
-<dl>
<dt><em><code>proxy.config.log.squid_log_enabled</code></em></dt>
<dd><code>INT</code></dd>
<dd><code>1</code></dd>
@@ -1291,8 +1279,10 @@ T=SERVER_PORT_BLIND_TUNNEL</p>
<dd><code>1</code></dd>
<dd>The squid log file type:</dd>
</dl>
-<p><code>1</code> = ASCII<br />
-<code>0</code> = binary</p>
+<ul>
+<li><code>1</code> = ASCII</li>
+<li><code>0</code> = binary</li>
+</ul>
<dl>
<dt><em><code>proxy.config.log.squid_log_name</code></em></dt>
<dd><code>STRING</code></dd>
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 Thu Mar 24 23:49:56 2011
@@ -31,7 +31,7 @@
<span class="nav"><a href="../faqs/index.en.html">Next</a></span>
- <span class="nav"><a href="../configuration-files/files.en.html">Back</a></span>
+ <span class="nav"><a href="../configuration-files/bypass.config.en.html">Back</a></span>
</div>
@@ -67,9 +67,6 @@ a loop when Traffic Server attempts to s
<dd>Generic logging error.</dd>
<dt><code>Bad cluster major version range</code> <em><code>version1-version2</code></em> <code>for node</code> <em><code>IP address</code></em> <code>connect failed</code></dt>
<dd>Incompatible software versions causing a problem.</dd>
-<dt><code>Can't open config file</code> <em><code>filename</code></em> <code>for reading custom formats</code></dt>
-<dd>Custom logging is enabled, but Traffic Server cannot find the <code>logs.config</code>
-file.</dd>
<dt><code>Connect by disallowed client</code> <em><code>IP address</code></em><code>, closing</code></dt>
<dd>The specified client is not allowed to connect to Traffic Server; the client
IP address is not listed in the <code>ip_allow.config</code> file.</dd>
@@ -124,10 +121,6 @@ consider rolling log files more frequent
<dd>Go to the Traffic Server <code>config</code> directory and check the indicated file.
If it is indeed zero in length, then use a backup copy of the configuration
file.</dd>
-<dt><code>Traffic Server can't open</code> <em><code>filename</code></em> <code>for reading custom formats</code></dt>
-<dd>Make sure the <em><code>proxy.config.log.config_file</code></em> variable in the <code>records.config</code>
-file contains the correct path to the custom log configuration file (the default
-is <code>logging/logs.config</code>).</dd>
<dt><code>Traffic Server could not open logfile</code> <em><code>filename</code></em></dt>
<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>
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/working-log-files/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/working-log-files/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/working-log-files/index.en.html Thu Mar 24 23:49:56 2011
@@ -305,13 +305,9 @@ at the beginning of the log file, just b
<dt><strong>Variable</strong> <strong>Description</strong></dt>
<dt><code>_proxy.config.log.custom_logs_enabled_</code></dt>
<dd>Set this variable to 1 to enable custom logging.</dd>
-<dt><code>_proxy.config.log.xml_logs_config_</code></dt>
-<dd>Make sure this variable is set to 1 (the default value).</dd>
</dl>
</li>
-<li>
-<p>Save and close the <code>records.config</code> file. </p>
-</li>
+<li>Save and close the <code>records.config</code> file. </li>
<li>Open the <code>logs_xml.config</code> file located in the Traffic Server <code>config</code> directory. </li>
<li>Add <code>LogFormat</code>, <code>LogFilter</code>, and <code>LogObject</code> specifications to the configuration file. For detailed information about this file, see <a href="files.htm#logs_xml.config">logs_xml.config</a>.</li>
<li>Save and close the <code>log``s_xml.config</code> file. </li>
@@ -976,11 +972,8 @@ file as before.</p>
<dt><strong>Variable</strong> <strong>Description</strong></dt>
<dt><code>_proxy.config.log.custom_logs_enabled _</code></dt>
<dd>Set this variable to 1 to enable custom logging.</dd>
-<dt><code>_proxy.config.log.xml_logs_config_</code></dt>
-<dd>Set this variable to 0 to disable XML-based custom logging.</dd>
</dl>
</li>
-<li />
<li>Save and close the <code>records.config</code> file. </li>
<li>Navigate to the Traffic Server <code>bin</code> directory. </li>
<li>Run the command <code>traffic_line -x</code> to apply the configuration changes.</li>