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/10 02:01:01 UTC
svn commit: r786787 - in
/websites/staging/trafficserver/trunk/content/docs/trunk/admin:
http-proxy-caching/index.en.html monitoring-traffic/index.en.html
traffic-server-error-messages/index.en.html
Author: buildbot
Date: Thu Mar 10 01:01:00 2011
New Revision: 786787
Log:
Staging update by buildbot
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/http-proxy-caching/index.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/monitoring-traffic/index.en.html
websites/staging/trafficserver/trunk/content/docs/trunk/admin/traffic-server-error-messages/index.en.html
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/http-proxy-caching/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/http-proxy-caching/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/http-proxy-caching/index.en.html Thu Mar 10 01:01:00 2011
@@ -71,10 +71,7 @@ object in its object database (<strong>c
<p><strong>Step 3</strong> If the object is in the cache, then Traffic Server checks to see
if the object is fresh enough to serve. If it is fresh, then Traffic Server
serves it to the user as a <strong>cache hit</strong> (see the figure below).</p>
-<p><img alt="" src="images/cache_hit.jpg" /></p>
-<blockquote>
-<p><em><strong>A cache hit</strong></em> </p>
-</blockquote>
+<p><img alt="A cache hit" src="/images/admin/cache_hit.jpg" /></p>
<p><strong>Step 4</strong> If the data in the cache is stale, then Traffic Server connects
to the origin server and checks if the object is still fresh (a <strong>revalidation</strong>).
If it is, then Traffic Server immediately sends the cached copy to the user. </p>
@@ -84,10 +81,7 @@ object from the origin server. The objec
the user and the Traffic Server local cache (see the figure below). Subsequent
requests for the object can be served faster because the object is retrieved
directly from cache.</p>
-<p><img alt="" src="images/cache_miss.jpg" /></p>
-<blockquote>
-<p><em><strong>A cache miss</strong></em> </p>
-</blockquote>
+<p><img alt="A cache miss" src="/images/admin/cache_miss.jpg" /></p>
<p>Caching is typically more complex than the preceding overview suggests. In
particular, the overview does not discuss how Traffic Server ensures freshness,
serves correct HTTP alternates, and treats requests for objects that cannot/should
@@ -759,19 +753,12 @@ available alternates in the object store
<li>Edit the following variable:</li>
<li>
<dl>
-<dt><strong>Variable</strong> <strong>Description</strong></dt>
-<dt><code>_proxy.config.cache.limits.http.max_alts_</code></dt>
-<dd />
+<dt><em><code>proxy.config.cache.limits.http.max_alts</code></em></dt>
+<dd>Set this variable to specify the maximum number of alternate versions of an
+ object you want Traffic Server to cache. The default value is three.</dd>
</dl>
-<div class="codehilite"><pre><span class="n">Set</span> <span class="n">this</span> <span class="n">variable</span> <span class="n">to</span> <span class="n">specify</span> <span class="n">the</span> <span class="n">maximum</span> <span class="n">number</span> <span class="n">of</span> <span class="n">alternate</span> <span class="n">versions</span> <span class="n">of</span> <span class="n">an</span>
-<span class="n">object</span> <span class="n">you</span> <span class="n">want</span> <span class="n">Traffic</span> <span class="n">Server</span> <span class="n">to</span> <span class="n">cache</span><span class="o">.</span> <span class="n">The</span> <span class="n">default</span> <span class="n">value</span> <span class="n">is</span> <span class="n">three</span><span class="o">.</span>
-</pre></div>
-
-
-</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>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>
</ol>
@@ -795,49 +782,17 @@ server later. </p>
<li>Edit the following variable:</li>
<li>
<dl>
-<dt><strong>Variable</strong> <strong>Description</strong></dt>
-<dt><code>_proxy.config.http.congestion_control.enabled_</code></dt>
-<dd />
+<dt><em><code>proxy.config.http.congestion_control.enabled</code></em></dt>
+<dd>Set this variable to 1 to enable the congestion control option.</dd>
</dl>
-<div class="codehilite"><pre><span class="n">Set</span> <span class="n">this</span> <span class="n">variable</span> <span class="n">to</span> <span class="mi">1</span> <span class="n">to</span> <span class="n">enable</span> <span class="n">the</span> <span class="n">congestion</span> <span class="n">control</span> <span class="n">option</span><span class="o">.</span>
-</pre></div>
-
-
-</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>In a text editor, open the <code>congestion.config</code> file located in the Traffic Server <code>config</code> directory. </li>
<li>Enter rules to specify which origin servers are tracked for congestion and the timeout values Traffic Server uses to determine congestion. Refer to <a href="files.htm#congestion.config">congestion.config</a> for the rule format. </li>
<li>Save and close the <code>congestion.config</code> file. </li>
<li>Navigate to the Traffic Server <code>bin</code> directory. </li>
-<li>
-<p>Run the command <code>traffic_line -x</code> to apply the configuration changes. </p>
-</li>
-<li>
-<p><a href="intro.htm">Overview</a></p>
-</li>
-<li><a href="getstart.htm">Getting Started</a></li>
-<li><a href="http.htm">HTTP Proxy Caching </a></li>
-<li><a href="explicit.htm">Explicit Proxy Caching</a></li>
-<li><a href="reverse.htm">Reverse Proxy and HTTP Redirects</a></li>
-<li><a href="hier.htm">Hierarchical Caching</a></li>
-<li><a href="cache.htm">Configuring the Cache</a></li>
-<li><a href="monitor.htm">Monitoring Traffic</a></li>
-<li><a href="configure.htm">Configuring Traffic Server</a></li>
-<li><a href="secure.htm">Security Options</a></li>
-<li><a href="log.htm">Working with Log Files</a></li>
-<li><a href="cli.htm">Traffic Line Commands</a></li>
-<li><a href="logfmts.htm">Event Logging Formats</a></li>
-<li><a href="files.htm">Configuration Files</a> </li>
-<li><a href="errors.htm">Traffic Server Error Messages</a></li>
-<li><a href="trouble.htm">FAQ and Troubleshooting Tips</a></li>
-<li><a href="ts_admin_chinese.pdf">Traffic Server 管çåæå</a> (PDF)</li>
-</ol>
-<p>Copyright © 2011 <a href="http://www.apache.org/">The Apache Software Foundation</a>.
-Licensed under the <a href="http://www.apache.org/licenses/">Apache License</a>, Version
-2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the
-Apache feather logo are trademarks of The Apache Software Foundation.</p>
+<li>Run the command <code>traffic_line -x</code> to apply the configuration changes. </li>
+</ol>
</div>
</div><!-- main -->
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/monitoring-traffic/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/monitoring-traffic/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/monitoring-traffic/index.en.html Thu Mar 10 01:01:00 2011
@@ -8,7 +8,7 @@
<link rel="stylesheet" href="/styles/ts.css" />
- <title>Monitoring Traffic</title>
+ <title>Apache Traffic Server - Monitoring Traffic</title>
<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
</head>
@@ -20,7 +20,7 @@
<span class="doc-title">Adminstrator's Guide</span><br />
- <span class="title">Monitoring Traffic</span>
+ <span class="title">Apache Traffic Server - Monitoring Traffic</span>
</td>
</tr></table>
</div><!-- header -->
@@ -105,29 +105,6 @@ to the statistic you want to see. </p>
<code>traffic_line -r proxy.node.http.cache_hit_ratio</code><br />
</p>
<p>If the Traffic Server <code>bin</code> directory is not in your path, then prepend the Traffic Line command with <code>./</code> (for example: <code>./traffic_line -r _variable_</code>).</p>
-<ul>
-<li><a href="intro.htm">Overview</a></li>
-<li><a href="getstart.htm">Getting Started</a></li>
-<li><a href="http.htm">HTTP Proxy Caching </a></li>
-<li><a href="explicit.htm">Explicit Proxy Caching</a></li>
-<li><a href="reverse.htm">Reverse Proxy and HTTP Redirects</a></li>
-<li><a href="hier.htm">Hierarchical Caching</a></li>
-<li><a href="cache.htm">Configuring the Cache</a></li>
-<li><a href="monitor.htm">Monitoring Traffic</a></li>
-<li><a href="configure.htm">Configuring Traffic Server</a></li>
-<li><a href="secure.htm">Security Options</a></li>
-<li><a href="log.htm">Working with Log Files</a></li>
-<li><a href="cli.htm">Traffic Line Commands</a></li>
-<li><a href="logfmts.htm">Event Logging Formats</a></li>
-<li><a href="files.htm">Configuration Files</a> </li>
-<li><a href="errors.htm">Traffic Server Error Messages</a></li>
-<li><a href="trouble.htm">FAQ and Troubleshooting Tips</a></li>
-<li><a href="ts_admin_chinese.pdf">Traffic Server 管çåæå</a> (PDF)</li>
-</ul>
-<p>Copyright © 2011 <a href="http://www.apache.org/">The Apache Software Foundation</a>.
-Licensed under the <a href="http://www.apache.org/licenses/">Apache License</a>, Version
-2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the
-Apache feather logo are trademarks of The Apache Software Foundation.</p>
</div>
</div><!-- main -->
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 10 01:01:00 2011
@@ -8,7 +8,7 @@
<link rel="stylesheet" href="/styles/ts.css" />
- <title>Error Messages</title>
+ <title>Apache Traffic Server - Error Messages</title>
<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
</head>
@@ -20,7 +20,7 @@
<span class="doc-title">Adminstrator's Guide</span><br />
- <span class="title">Error Messages</span>
+ <span class="title">Apache Traffic Server - Error Messages</span>
</td>
</tr></table>
</div><!-- header -->
@@ -39,599 +39,280 @@
<div class="main">
<div id="content">
- <h1 id="AppendixF-TSErrorMessages">Appendix F - Traffic Server Error Messages</h1>
-<p>This appendix contains the following sections:</p>
+ <h1 id="AppendixF-TSErrorMessages">Traffic Server Error Messages</h1>
+<p>This section contains the following sections:</p>
<ul>
-<li><a href="#57301">Traffic Server Error Messages</a>: describes the warning messages Traffic Server sends to the system log file.</li>
-<li><a href="#65686">Traffic Server Alarm Messages</a>: describes the alarm messages that may appear on Traffic Manager Monitor pages.</li>
-<li><a href="#55499">HTML Messages Sent to Clients</a>: describes the HTML error messages Traffic Server sends to browser clients.</li>
-<li><a href="#55388">Standard HTTP Response Messages</a>: describes the standard HTTP response codes origin servers send to browser clients.</li>
+<li><a href="#TSErrorMessages">Traffic Server Error Messages</a>: describes the warning messages Traffic Server sends to the system log file.</li>
+<li><a href="#TSAlarmMessages">Traffic Server Alarm Messages</a>: describes the alarm messages that may appear on Traffic Manager Monitor pages.</li>
+<li><a href="#HTMLMessagesSentClients">HTML Messages Sent to Clients</a>: describes the HTML error messages Traffic Server sends to browser clients.</li>
+<li><a href="#StandardHTTPResponseMessages">Standard HTTP Response Messages</a>: describes the standard HTTP response codes origin servers send to browser clients.</li>
</ul>
<h2 id="TSErrorMessages">Traffic Server Error Messages</h2>
-<p>The following table lists messages that can appear in system log files. This
-list is not exhaustive; it simply describes common warning messages that can
-occur and which might require your attention. </p>
+<p>The following table lists messages that can appear in system log files. This
+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>
-<div class="codehilite"><pre> <span class="o">**</span>
-</pre></div>
-
-
-<p>Message</p>
-<hr />
-<p>Description</p>
-<p>** </p>
+<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>
-<p>The port specified in the <code>records.config</code> file that accepts incoming HTTP
-requests is not valid. </p>
-</dd>
+<dd>The port specified in the <code>records.config</code> file that accepts incoming HTTP
+requests is not valid.</dd>
<dt><code>Self loop is detected in parent proxy configuration</code></dt>
-<dd>
-<p>The name and port of the parent proxy match that of Traffic Server. This creates
-a loop when Traffic Server attempts to send the request to the parent proxy. </p>
-</dd>
+<dd>The name and port of the parent proxy match that of Traffic Server. This creates
+a loop when Traffic Server attempts to send the request to the parent proxy.</dd>
</dl>
<h3 id="TSWarnings">Traffic Server Warnings</h3>
-<div class="codehilite"><pre> <span class="o">**</span>
-</pre></div>
-
-
-<p>Message</p>
-<hr />
-<p>Description</p>
-<p>** </p>
<dl>
-<dt><code>_ Logfile_ error: _ error_number_</code></dt>
-<dd>
-<p>Generic logging error.</p>
-</dd>
-<dt>` Bad cluster major version range _ version1_ -_ version2_ for node _ IP address_ </dt>
-<dt>connect failed`</dt>
-<dd>
-<p>Incompatible software versions causing a problem.</p>
-</dd>
-<dt><code>Can't open config file _ filename_ for reading custom formats</code></dt>
-<dd>
-<p>Custom logging is enabled, but Traffic Server cannot find the <code>logs.config</code>
-file. </p>
-</dd>
-<dt><code>Connect by disallowed client _ IP address_, closing</code></dt>
-<dd>
-<p>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. </p>
-</dd>
-<dt>Could not rename log_ <code>filename</code>_ to _ <code>rolled filename</code>_ </dt>
-<dd>
-<p>System error when renaming log file during roll. </p>
-</dd>
-<dt><code>Did _ this_amount_ of backup; still to do _ remaining_amount_</code></dt>
-<dd>
-<p>Congestion is approaching.</p>
-</dd>
-<dt>` Different clustering minor versions _ version1_ , _ version2_ for node _ </dt>
-<dt>IP address_ continuing`</dt>
-<dd>
-<p>Incompatible software versions are causing a problem. </p>
-</dd>
-<dt><code>Log format symbol _ symbol_name_ not found</code></dt>
-<dd>
-<p>Custom log format references a field symbol that does not exist. Refer to
-<a href="logfmts.htm">Event Logging Formats</a>.</p>
-</dd>
+<dt><em><code>Logfile</code></em> <code>error:</code> <em><code>error_number</code></em></dt>
+<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>
+<dt><code>Could not rename log</code> <em><code>filename</code></em> to <em><code>rolled filename</code></em></dt>
+<dd>System error when renaming log file during roll.</dd>
+<dt><code>Did</code> <em><code>this_amount</code></em> <code>of backup; still to do</code> <em><code>remaining_amount</code></em></dt>
+<dd>Congestion is approaching.</dd>
+<dt><code>Different clustering minor versions</code> <em><code>version1, version2</code></em> <code>for node</code> <em><code>IP address</code></em> <code>continuing</code></dt>
+<dd>Incompatible software versions are causing a problem.</dd>
+<dt><code>Log format symbol</code> <em><code>symbol_name</code></em> <code>not found</code></dt>
+<dd>Custom log format references a field symbol that does not exist. Refer to
+<a href="logfmts.htm">Event Logging Formats</a>.</dd>
<dt><code>Missing field for field marker</code></dt>
-<dd>
-<p>Error reading a log buffer.</p>
-</dd>
-<dt><code>Unable to open log file_ filename_, errno=_ error_number_</code></dt>
-<dd>
-<p>Cannot open the log file.</p>
-</dd>
-<dt><code>Error accessing disk _ disk_name_</code></dt>
-<dd>
-<p>Traffic Server might have a cache read problem. You might need to replace
-the disk.</p>
-</dd>
-<dt><code>Too many errors accessing disk _ disk_name_ : declaring disk bad</code></dt>
-<dd>
-<p>Traffic Server is not using the cache disk because it encountered too many
-errors. The disk might be corrupt and might have to be replaced.</p>
-</dd>
+<dd>Error reading a log buffer.</dd>
+<dt><code>Unable to open log file</code> <em><code>filename</code></em><code>, errno=</code><em><code>error_number</code></em></dt>
+<dd>Cannot open the log file.</dd>
+<dt><code>Error accessing disk</code> <em><code>disk_name</code></em></dt>
+<dd>Traffic Server might have a cache read problem. You might need to replace
+the disk.</dd>
+<dt><code>Too many errors accessing disk</code> <em><code>disk_name</code></em> <code>: declaring disk bad</code></dt>
+<dd>Traffic Server is not using the cache disk because it encountered too many
+errors. The disk might be corrupt and might have to be replaced.</dd>
<dt><code>No cache disks specified in storage.config file: cache disabled</code></dt>
-<dd>
-<p>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.</p>
-</dd>
+<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>
</dl>
<h2 id="TSAlarmMessages">Traffic Server Alarm Messages</h2>
-<div class="codehilite"><pre> <span class="o">**</span>
-</pre></div>
-
-
-<p>Message</p>
-<hr />
-<p>Description</p>
-<p>** </p>
<dl>
-<dt><code>[Rollback::Rollback] Config file is read-only:_ filename_</code></dt>
-<dd>
-<p>Go to the Traffic Server <code>config</code> directory and check the indicated file
-permissions; change if necessary. </p>
-</dd>
-<dt><code>[Rollback::Rollback] Unable to read or write config file_ filename_</code></dt>
-<dd>
-<p>Go to the Traffic Server <code>config</code> directory and make sure the indicated file
-exists. Check permissions and modify if necessary. </p>
-</dd>
-<dt><code>[Traffic Manager] Configuration File Update Failed: _ error_number_</code></dt>
-<dd>
-<p>Go to the Traffic Server <code>config</code> directory and check the indicated file
-permissions; change if necessary. </p>
-</dd>
+<dt><code>[Rollback::Rollback] Config file is read-only:</code> <em><code>filename</code></em></dt>
+<dd>Go to the Traffic Server <code>config</code> directory and check the indicated file
+permissions; change if necessary.</dd>
+<dt><code>[Rollback::Rollback] Unable to read or write config file</code> <em><code>filename</code></em></dt>
+<dd>Go to the Traffic Server <code>config</code> directory and make sure the indicated file
+exists. Check permissions and modify if necessary.</dd>
+<dt><code>[Traffic Manager] Configuration File Update Failed:</code> <em><code>error_number</code></em></dt>
+<dd>Go to the Traffic Server <code>config</code> directory and check the indicated file
+permissions; change if necessary.</dd>
<dt><code>[Traffic Manager] Mgmt <==>Proxy conn. closed</code></dt>
-<dd>
-<p>An informational message to inform you that the <code>traffic_server</code> process
-is down. </p>
-</dd>
+<dd>An informational message to inform you that the <code>traffic_server</code> process
+is down.</dd>
<dt><code>Access logging suspended - configured space allocation exhausted.</code></dt>
-<dd>
-<p>The space allocated to the event log files is full; you must either increase
-the space or delete some log files so that access logging to continue. To prevent
-this error, consider rolling log files more frequently and enabling the autodelete
-feature. </p>
-</dd>
+<dd>The space allocated to the event log files is full; you must either increase
+the space or delete some log files so that access logging to continue. To prevent
+this error, consider rolling log files more frequently and enabling the autodelete
+feature.</dd>
<dt><code>Access logging suspended - no more space on the logging partition.</code></dt>
-<dd>
-<p>The entire partition containing the event logs is full; you must delete or
-move some log files to enable access logging to continue. To prevent this error,
-consider rolling log files more frequently and enabling the autodelete feature. </p>
-</dd>
-<dt><code>Created zero length place holder for config file_ filename_</code></dt>
-<dd>
-<p>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. </p>
-</dd>
-<dt><code>Traffic Server can't open_ filename _for reading custom formats</code></dt>
-<dd>
-<p>Make sure the <code>_proxy.config.log.config_file_</code> 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> ). </p>
-</dd>
-<dt><code>Traffic Server could not open logfile _ filename_</code></dt>
-<dd>
-<p>Check permissions for the indicated file and the logging directory. </p>
-</dd>
-<dt>` Traffic Server failed to parse line _ line_number_ of the logging config </dt>
-<dt>file_ filename_`</dt>
-<dd>
-<p>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
-fields. </p>
-</dd>
-<dt>`vip_config binary is not setuid root, manager will be unable to enable virtual </dt>
-<dt>ip addresses`</dt>
-<dd>
-<p>The <code>traffic_manager</code> process is not able to set virtual IP addresses. You
-must <code>setuid root</code>for the <code>vip_config</code> file in the Traffic Server <code>bin</code>
-directory. </p>
-</dd>
+<dd>The entire partition containing the event logs is full; you must delete or
+move some log files to enable access logging to continue. To prevent this error,
+consider rolling log files more frequently and enabling the autodelete feature.</dd>
+<dt><code>Created zero length place holder for config file</code> <em><code>filename</code></em></dt>
+<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>
+<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
+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
+must <code>setuid root</code>for the <code>vip_config</code> file in the Traffic Server <code>bin</code>
+directory.</dd>
</dl>
<h2 id="HTMLMessagesSentClients">HTML Messages Sent to Clients</h2>
-<p>Traffic Server returns detailed error messages to browser clients when there
-are problems with the HTTP transactions requested by the browser. These Traffic
-Server response messages correspond to standard HTTP response codes, but provide
-more information. A list of the more frequently-encountered HTTP response codes
-is provided in <a href="#55388">Standard HTTP Response Messages</a>. You can customize
+<p>Traffic Server returns detailed error messages to browser clients when there
+are problems with the HTTP transactions requested by the browser. These Traffic
+Server response messages correspond to standard HTTP response codes, but provide
+more information. A list of the more frequently-encountered HTTP response codes
+is provided in <a href="#StandardHTTPResponseMessages">Standard HTTP Response Messages</a>. You can customize
the Traffic Server response messages, if desired.</p>
-<p>The following table lists the hard-coded Traffic Server HTTP messages, with
-corresponding HTTP response codes and customizable files. </p>
-<div class="codehilite"><pre> <span class="o">**</span>
-</pre></div>
-
-
-<p>Title </p>
-<hr />
-<p>HTTP Code</p>
-<hr />
-<p>Description</p>
-<hr />
-<p>Customizable Filename</p>
-<p>** </p>
+<p>The following table lists the hard-coded Traffic Server HTTP messages, with
+corresponding HTTP response codes and customizable files.</p>
<dl>
<dt><code>Access Denied</code></dt>
-<dd>
-<dl>
-<dt><code>403</code></dt>
-<dd />
-<dt>You are not allowed to access the document at location <code>_ URL_</code> . </dt>
-<dd />
-</dl>
-<p><code>access#denied</code></p>
-</dd>
+<dd><code>403</code></dd>
+<dd>You are not allowed to access the document at location <em><code>URL</code></em> .</dd>
+<dd><code>access#denied</code></dd>
<dt><code>Cache Read Error</code></dt>
-<dd>
-<dl>
-<dt><code>500</code></dt>
-<dd />
-<dt>Error reading from cache; please retry request.</dt>
-<dd />
-</dl>
-<p><code>cache#read_error</code></p>
-</dd>
+<dd><code>500</code></dd>
+<dd>Error reading from cache; please retry request.</dd>
+<dd><code>cache#read_error</code></dd>
<dt><code>Connection Timed Out</code></dt>
-<dd>
-<dl>
-<dt><code>504</code></dt>
-<dd />
-<dt>Too much time has elapsed since the server has sent data. </dt>
-<dd />
-</dl>
-<p><code>timeout#inactivity</code></p>
-</dd>
+<dd><code>504</code></dd>
+<dd>Too much time has elapsed since the server has sent data.</dd>
+<dd><code>timeout#inactivity</code></dd>
<dt><code>Content Length Required</code></dt>
-<dd>
-<dl>
-<dt><code>400</code></dt>
-<dd />
-<dt>Could not process this request because <code>Content-Length</code> was not specified. </dt>
-<dd />
-</dl>
-<p><code>request#no_content_length</code></p>
-</dd>
+<dd><code>400</code></dd>
+<dd>Could not process this request because <code>Content-Length</code> was not specified.</dd>
+<dd><code>request#no_content_length</code></dd>
<dt><code>Cycle Detected</code></dt>
-<dd>
-<dl>
-<dt><code>400</code></dt>
-<dd />
-<dt>Your request is prohibited because it would cause an HTTP proxy cycle. </dt>
-<dd />
-</dl>
-<p><code>request#cycle_detected</code></p>
-</dd>
+<dd><code>400</code></dd>
+<dd>Your request is prohibited because it would cause an HTTP proxy cycle.</dd>
+<dd><code>request#cycle_detected</code></dd>
<dt><code>Forbidden</code></dt>
-<dd>
-<dl>
-<dt><code>403</code></dt>
-<dd />
-<dt><code>_ port_number_</code> is not an allowed port for SSL connections (you have made </dt>
-<dt>a request for a secure SSL connection to a forbidden port number).</dt>
-<dd />
-</dl>
-<p><code>access#ssl_forbidden</code></p>
-</dd>
+<dd><code>403</code></dd>
+<dd><em><code>port_number</code></em> is not an allowed port for SSL connections (you have made
+ a request for a secure SSL connection to a forbidden port number).</dd>
+<dd><code>access#ssl_forbidden</code></dd>
<dt><code>Host Header Required</code></dt>
-<dd>
-<dl>
-<dt><code>400</code></dt>
-<dd />
-<dt>An attempt was made to transparently proxy your request, but this attempt </dt>
-<dt>failed because your browser did not send an HTTP <code>Host</code> header. Manually configure </dt>
-<dt>your browser to use <code>http://</code> <code>_ proxy_name_</code> :<code>_ proxy_port_</code> as the HTTP </dt>
-<dt>proxy. Alternatively, end users can upgrade to a browser that supports the </dt>
-<dt>HTTP <code>Host</code> header field.</dt>
-<dd />
-</dl>
-<p><code>interception#no_host</code></p>
-</dd>
+<dd><code>400</code></dd>
+<dd>An attempt was made to transparently proxy your request, but this attempt
+failed because your browser did not send an HTTP <code>Host</code> header. Manually configure
+your browser to use <code>http://</code><em><code>proxy_name</code></em><code>:</code><em><code>proxy_port</code></em> as the HTTP
+proxy. Alternatively, end users can upgrade to a browser that supports the
+HTTP <code>Host</code> header field.</dd>
+<dd><code>interception#no_host</code></dd>
<dt><code>Host Header Required</code></dt>
-<dd>
-<dl>
-<dt><code>400</code></dt>
-<dd />
-<dt>Because your browser did not send a <code>Host</code> HTTP header field, the virtual </dt>
-<dt>host being requested could not be determined. To access the website correctly, </dt>
-<dt>you must upgrade to a browser that supports the HTTP <code>Host</code> header field.</dt>
-<dd />
-</dl>
-<p><code>request#no_host</code></p>
-</dd>
+<dd><code>400</code></dd>
+<dd>Because your browser did not send a <code>Host</code> HTTP header field, the virtual
+host being requested could not be determined. To access the website correctly,
+you must upgrade to a browser that supports the HTTP <code>Host</code> header field.</dd>
+<dd><code>request#no_host</code></dd>
<dt><code>HTTP Version Not Supported</code></dt>
-<dd>
-<dl>
-<dt><code>505</code></dt>
-<dd />
-<dt>The origin server <em><code>server_name</code></em> is using an unsupported version of the </dt>
-<dt>HTTP protocol.</dt>
-<dd />
-</dl>
-<p><code>response#bad_version</code></p>
-</dd>
+<dd><code>505</code></dd>
+<dd>The origin server <em><code>server_name</code></em> is using an unsupported version of the
+HTTP protocol.</dd>
+<dd><code>response#bad_version</code></dd>
<dt><code>Invalid HTTP Request</code></dt>
-<dd>
-<dl>
-<dt><code>400</code></dt>
-<dd />
-<dt>Could not process this <code>_ client_request_</code> HTTP method request for <em><code>URL</code></em> </dt>
-<dt>.</dt>
-<dd />
-</dl>
-<p><code>request#syntax_error</code></p>
-</dd>
+<dd><code>400</code></dd>
+<dd>Could not process this <em><code>client_request</code></em> HTTP method request for <em><code>URL</code></em>.</dd>
+<dd><code>request#syntax_error</code></dd>
<dt><code>Invalid HTTP Response</code></dt>
-<dd>
-<dl>
-<dt><code>502</code></dt>
-<dd />
-<dt>The host <code>_ server_name_</code> did not return the document <code>_ URL_</code> correctly. </dt>
-<dd />
-</dl>
-<p><code>response#bad_response</code></p>
-</dd>
+<dd><code>502</code></dd>
+<dd>The host <em><code>server_name</code></em> did not return the document <em><code>URL</code></em> correctly.</dd>
+<dd><code>response#bad_response</code></dd>
<dt><code>Malformed Server Response</code></dt>
-<dd>
-<dl>
-<dt><code>502</code></dt>
-<dd />
-<dt>The host <code>_ server_name_</code> did not return the document <code>_ URL_</code> correctly. </dt>
-<dd />
-</dl>
-<p><code>response#bad_response</code></p>
-</dd>
+<dd><code>502</code></dd>
+<dd>The host <em><code>server_name</code></em> did not return the document <em><code>URL</code></em> correctly.</dd>
+<dd><code>response#bad_response</code></dd>
<dt><code>Malformed Server Response Status</code></dt>
-<dd>
-<dl>
-<dt><code>502</code></dt>
-<dd />
-<dt>The host <code>_ server_name _</code> did not return the document <code>_ URL _</code> correctly. </dt>
-<dd />
-</dl>
-<p><code>response#bad_response</code></p>
-</dd>
+<dd><code>502</code></dd>
+<dd>The host <em><code>server_name</code></em> did not return the document <em><code>URL</code></em> correctly.</dd>
+<dd><code>response#bad_response</code></dd>
<dt><code>Maximum Transaction Time exceeded</code></dt>
-<dd>
-<dl>
-<dt><code>504</code></dt>
-<dd />
-<dt>Too much time has elapased while transmitting document <code>_ URL_</code> .</dt>
-<dd />
-</dl>
-<p><code>timeout#activity</code></p>
-</dd>
+<dd><code>504</code></dd>
+<dd>Too much time has elapased while transmitting document <em><code>URL</code></em> .</dd>
+<dd><code>timeout#activity</code></dd>
<dt><code>No Response Header From Server</code></dt>
-<dd>
-<dl>
-<dt><code>502</code></dt>
-<dd />
-<dt>The host <code>_ server_name _</code> did not return the document <code>_ URL_</code> correctly. </dt>
-<dd />
-</dl>
-<p><code>response#bad_response</code></p>
-</dd>
+<dd><code>502</code></dd>
+<dd>The host <em><code>server_name</code></em> did not return the document <em><code>URL</code></em> correctly.</dd>
+<dd><code>response#bad_response</code></dd>
<dt><code>Not Cached</code></dt>
-<dd>
-<dl>
-<dt><code>504</code></dt>
-<dd />
-<dt>This document was not available in the cache, and you (the client) only accept </dt>
-<dt>cached copies.</dt>
-<dd />
-</dl>
-<p><code>cache#not_in_cache</code></p>
-</dd>
+<dd><code>504</code></dd>
+<dd>This document was not available in the cache, and you (the client) only accept
+cached copies.</dd>
+<dd><code>cache#not_in_cache</code></dd>
<dt><code>Not Found on Accelerator</code></dt>
-<dd>
-<dl>
-<dt><code>404</code></dt>
-<dd />
-<dt>The request for <code>_ URL_</code> on host <code>_ server_name _</code> was not found. Check the </dt>
-<dt>location and try again.</dt>
-<dd />
-</dl>
-<p><code>urlrouting#no_mapping</code></p>
-</dd>
+<dd><code>404</code></dd>
+<dd>The request for <em><code>URL</code></em> on host <em><code>server_name</code></em> was not found. Check the
+location and try again.</dd>
+<dd><code>urlrouting#no_mapping</code></dd>
<dt><code>NULL</code></dt>
-<dd>
-<dl>
-<dt><code>502</code></dt>
-<dd />
-<dt>The host <code>_ hostname_</code> did not return the document <code>_ URL_</code> correctly.</dt>
-<dd />
-</dl>
-<p><code>response#bad_response</code></p>
-</dd>
+<dd><code>502</code></dd>
+<dd>The host <em><code>hostname</code></em> did not return the document <em><code>URL</code></em> correctly.</dd>
+<dd><code>response#bad_response</code></dd>
<dt><code>Proxy Authentication Required</code></dt>
-<dd>
-<dl>
-<dt><code>407</code></dt>
-<dd />
-<dt>Please log in with username and password.</dt>
-<dd />
-</dl>
-<p><code>access#proxy_auth_required</code></p>
-</dd>
+<dd><code>407</code></dd>
+<dd>Please log in with username and password.</dd>
+<dd><code>access#proxy_auth_required</code></dd>
<dt><code>Server Hangup</code></dt>
-<dd>
-<dl>
-<dt><code>502</code></dt>
-<dd />
-<dt>The server <code>_ hostname_</code> closed the connection before the transaction was </dt>
-<dt>completed.</dt>
-<dd />
-</dl>
-<p><code>connect#hangup</code></p>
-</dd>
+<dd><code>502</code></dd>
+<dd>The server <em><code>hostname</code></em> closed the connection before the transaction was
+ completed.</dd>
+<dd><code>connect#hangup</code></dd>
<dt><code>Temporarily Moved</code></dt>
-<dd>
-<dl>
-<dt><code>302</code></dt>
-<dd />
-<dt>The document you requested,<code>_ URL_</code> , has moved to a new location. The new </dt>
-<dt>location is <code>_ new_URL_</code> .</dt>
-<dd />
-</dl>
-<p><code>redirect#moved_temporarily</code></p>
-</dd>
+<dd><code>302</code></dd>
+<dd>The document you requested, <em><code>URL</code></em>, has moved to a new location. The new
+ location is <em><code>new_URL</code></em>.</dd>
+<dd><code>redirect#moved_temporarily</code></dd>
<dt><code>Transcoding Not Available</code></dt>
-<dd>
-<dl>
-<dt><code>406</code></dt>
-<dd />
-<dt>Unable to provide the document <code>_ URL_</code> in the format requested by your browser. </dt>
-<dd />
-</dl>
-<p><code>transcoding#unsupported</code></p>
-</dd>
+<dd><code>406</code></dd>
+<dd>Unable to provide the document <em><code>URL</code></em> in the format requested by your browser.</dd>
+<dd><code>transcoding#unsupported</code></dd>
<dt><code>Tunnel Connection Failed</code></dt>
-<dd>
-<dl>
-<dt><code>502</code></dt>
-<dd />
-<dt>Could not connect to the server <code>_ hostname_</code> .</dt>
-<dd />
-</dl>
-<p><code>connect#failed_connect</code></p>
-</dd>
+<dd><code>502</code></dd>
+<dd>Could not connect to the server <em><code>hostname</code></em>.</dd>
+<dd><code>connect#failed_connect</code></dd>
<dt><code>Unknown Error</code></dt>
-<dd>
-<dl>
-<dt><code>502</code></dt>
-<dd />
-<dt>The host <code>_ hostname_</code> did not return the document <code>_ URL_</code> correctly.</dt>
-<dd />
-</dl>
-<p><code>response#bad_response</code></p>
-</dd>
+<dd><code>502</code></dd>
+<dd>The host <em><code>hostname</code></em> did not return the document <em><code>URL</code></em> correctly.</dd>
+<dd><code>response#bad_response</code></dd>
<dt><code>Unknown Host</code></dt>
-<dd>
-<dl>
-<dt><code>500</code></dt>
-<dd />
-<dt>Unable to locate the server named <code>_ hostname_</code>; the server does not have </dt>
-<dt>a DNS entry. Perhaps there is a misspelling in the server name or the server </dt>
-<dt>no longer exists; double-check the name and try again. </dt>
-<dd />
-</dl>
-<p><code>connect#dns_failed</code></p>
-</dd>
+<dd><code>500</code></dd>
+<dd>Unable to locate the server named <em><code>hostname</code></em>; the server does not have
+a DNS entry. Perhaps there is a misspelling in the server name or the server
+no longer exists; double-check the name and try again.</dd>
+<dd><code>connect#dns_failed</code></dd>
<dt><code>Unsupported URL Scheme</code></dt>
-<dd>
-<dl>
-<dt><code>400</code></dt>
-<dd />
-<dt>Cannot perform your request for the document <code>_ URL_</code> because the protocol </dt>
-<dt>scheme is unknown.</dt>
-<dd />
-</dl>
-<p><code>request#scheme_unsupported</code></p>
-</dd>
+<dd><code>400</code></dd>
+<dd>Cannot perform your request for the document <em><code>URL</code></em> because the protocol
+scheme is unknown.</dd>
+<dd><code>request#scheme_unsupported</code></dd>
</dl>
<h3 id="StandardHTTPResponseMessages">Standard HTTP Response Messages</h3>
-<p>The following standard HTTP response messages are provided for your information. </p>
-<div class="codehilite"><pre><span class="o">**</span>
-</pre></div>
-
-
-<p>Message</p>
-<hr />
-<p>Description</p>
-<p>** </p>
+<p>The following standard HTTP response messages are provided for your information.</p>
<dl>
<dt><strong><code>200</code></strong></dt>
-<dd>
-<p>OK</p>
-</dd>
+<dd>OK</dd>
<dt><strong><code>202</code></strong></dt>
-<dd>
-<p>Accepted</p>
-</dd>
+<dd>Accepted</dd>
<dt><strong><code>204</code></strong></dt>
-<dd>
-<p>No Content</p>
-</dd>
+<dd>No Content</dd>
<dt><strong><code>206</code></strong></dt>
-<dd>
-<p>Partial Content</p>
-</dd>
+<dd>Partial Content</dd>
<dt><strong><code>300</code></strong></dt>
-<dd>
-<p>Multiple Choices</p>
-</dd>
+<dd>Multiple Choices</dd>
<dt><strong><code>301</code></strong></dt>
-<dd>
-<p>Moved Permanently</p>
-</dd>
+<dd>Moved Permanently</dd>
<dt><strong><code>302</code></strong></dt>
-<dd>
-<p>Found</p>
-</dd>
+<dd>Found</dd>
<dt><strong><code>303</code></strong></dt>
-<dd>
-<p>See Other</p>
-</dd>
+<dd>See Other</dd>
<dt><strong><code>304</code></strong></dt>
-<dd>
-<p>Not Modified</p>
-</dd>
+<dd>Not Modified</dd>
<dt><strong><code>400</code></strong></dt>
-<dd>
-<p>Bad Request</p>
-</dd>
+<dd>Bad Request</dd>
<dt><strong><code>401</code></strong></dt>
-<dd>
-<p>Unauthorized; retry</p>
-</dd>
+<dd>Unauthorized; retry</dd>
<dt><strong><code>403</code></strong></dt>
-<dd>
-<p>Forbidden</p>
-</dd>
+<dd>Forbidden</dd>
<dt><strong><code>404</code></strong></dt>
-<dd>
-<p>Not Found</p>
-</dd>
+<dd>Not Found</dd>
<dt><strong><code>405</code></strong></dt>
-<dd>
-<p>Method Not Allowed</p>
-</dd>
+<dd>Method Not Allowed</dd>
<dt><strong><code>406</code></strong></dt>
-<dd>
-<p>Not acceptable</p>
-</dd>
+<dd>Not acceptable</dd>
<dt><strong><code>408</code></strong></dt>
-<dd>
-<p>Request Timeout</p>
-</dd>
+<dd>Request Timeout</dd>
<dt><strong><code>500</code></strong></dt>
-<dd>
-<p>Internal server error</p>
-</dd>
+<dd>Internal server error</dd>
<dt><strong><code>501</code></strong></dt>
-<dd>
-<p>Not Implemented</p>
-</dd>
+<dd>Not Implemented</dd>
<dt><strong><code>502</code></strong></dt>
-<dd>
-<p>Bad Gateway</p>
-</dd>
+<dd>Bad Gateway</dd>
<dt><strong><code>504</code></strong></dt>
-<dd>
-<p>Gateway Timeout</p>
-</dd>
+<dd>Gateway Timeout</dd>
</dl>
-<ul>
-<li><a href="intro.htm">Overview</a></li>
-<li><a href="getstart.htm">Getting Started</a></li>
-<li><a href="http.htm">HTTP Proxy Caching </a></li>
-<li><a href="explicit.htm">Explicit Proxy Caching</a></li>
-<li><a href="reverse.htm">Reverse Proxy and HTTP Redirects</a></li>
-<li><a href="hier.htm">Hierarchical Caching</a></li>
-<li><a href="cache.htm">Configuring the Cache</a></li>
-<li><a href="monitor.htm">Monitoring Traffic</a></li>
-<li><a href="configure.htm">Configuring Traffic Server</a></li>
-<li><a href="secure.htm">Security Options</a></li>
-<li><a href="log.htm">Working with Log Files</a></li>
-<li><a href="cli.htm">Traffic Line Commands</a></li>
-<li><a href="logfmts.htm">Event Logging Formats</a></li>
-<li><a href="files.htm">Configuration Files</a> </li>
-<li><a href="errors.htm">Traffic Server Error Messages</a></li>
-<li><a href="trouble.htm">FAQ and Troubleshooting Tips</a></li>
-<li><a href="ts_admin_chinese.pdf">Traffic Server 管çåæå</a> (PDF)</li>
-</ul>
-<p>Copyright © 2011 <a href="http://www.apache.org/">The Apache Software Foundation</a>.
-Licensed under the <a href="http://www.apache.org/licenses/">Apache License</a>, Version
-2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the
-Apache feather logo are trademarks of The Apache Software Foundation.</p>
</div>
</div><!-- main -->