PageRenderTime 10ms CodeModel.GetById 1ms app.highlight 6ms RepoModel.GetById 1ms app.codeStats 0ms

/doc/admin/traffic-server-error-messages.en.rst

https://github.com/anorsich/trafficserver
ReStructuredText | 373 lines | 284 code | 89 blank | 0 comment | 0 complexity | ac9b2d6c72f276abe29acd34d80df2a0 MD5 | raw file
  1.. _traffic-server-error-messages:
  2
  3Error Messages
  4**************
  5
  6.. Licensed to the Apache Software Foundation (ASF) under one
  7   or more contributor license agreements.  See the NOTICE file
  8   distributed with this work for additional information
  9   regarding copyright ownership.  The ASF licenses this file
 10   to you under the Apache License, Version 2.0 (the
 11   "License"); you may not use this file except in compliance
 12   with the License.  You may obtain a copy of the License at
 13
 14   http://www.apache.org/licenses/LICENSE-2.0
 15
 16   Unless required by applicable law or agreed to in writing,
 17   software distributed under the License is distributed on an
 18   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 19   KIND, either express or implied.  See the License for the
 20   specific language governing permissions and limitations
 21   under the License.
 22
 23.. toctree::
 24   :maxdepth: 2
 25
 26Traffic Server Error Messages
 27=============================
 28
 29The following table lists messages that can appear in system log files.
 30This list is not exhaustive; it simply describes common warning messages
 31that can occur and which might require your attention.
 32
 33Traffic Server Process Fatal
 34============================
 35
 36``Accept port is not between 1 and 65535. Please check configuration``
 37   The port specified in the :file:`records.config` file that accepts
 38   incoming HTTP requests is not valid.
 39
 40``Self loop is detected in parent proxy configuration``
 41   The name and port of the parent proxy match that of Traffic Server.
 42   This creates a loop when Traffic Server attempts to send the request
 43   to the parent proxy.
 44
 45Traffic Server Warnings
 46-----------------------
 47
 48``<Logfile> error: error_number``
 49   Generic logging error.
 50
 51``Bad cluster major version range <version1-version2> for node <IP address> connect failed``
 52   Incompatible software versions causing a problem.
 53
 54``Connect by disallowed client <IP address>, closing``
 55   The specified client is not allowed to connect to Traffic Server;
 56   the client IP address is not listed in the ``ip_allow.config`` file.
 57
 58``Could not rename log <filename> to <rolled filename>``
 59   System error when renaming log file during roll.
 60
 61``Did <this amount> of backup; still to do <remaining amount>``
 62   Congestion is approaching.
 63
 64``Different clustering minor versions <version1, version2> for node <IP address> continuing``
 65   Incompatible software versions are causing a problem.
 66
 67``Log format symbol <symbol name> not found``
 68   Custom log format references a field symbol that does not exist.
 69   Refer to :ref:`event-logging-formats`.
 70
 71``Missing field for field marker``
 72   Error reading a log buffer.
 73
 74``Unable to open log file <filename>, errno=<error number>``
 75   Cannot open the log file.
 76
 77``Error accessing disk <disk name>``
 78   Traffic Server might have a cache read problem. You might need to
 79   replace the disk.
 80
 81``Too many errors accessing disk <disk name>: declaring disk bad``
 82   Traffic Server is not using the cache disk because it encountered
 83   too many errors. The disk might be corrupt and might have to be
 84   replaced.
 85
 86``No cache disks specified in storage.config file: cache disabled``
 87   The Traffic Server ``storage.config`` file does not list any cache
 88   disks; Traffic Server is running in proxy-only mode. You must add
 89   the disks you want to use for the cache to :file:`storage.config`.
 90
 91Traffic Server Alarm Messages
 92=============================
 93
 94``[Rollback::Rollback] Config file is read-only: <filename>``
 95   Go to the Traffic Server ``config`` directory and check the
 96   indicated file permissions; change if necessary.
 97
 98``[Rollback::Rollback] Unable to read or write config file <filename>``
 99   Go to the Traffic Server ``config`` directory and make sure the
100   indicated file exists. Check permissions and modify if necessary.
101
102``[Traffic Manager] Configuration File Update Failed: <error number>``
103   Go to the Traffic Server ``config`` directory and check the
104   indicated file permissions; change if necessary.
105
106``[Traffic Manager] Mgmt <==>Proxy conn. closed``
107   An informational message to inform you that the :program:`traffic_server`
108   process is down.
109
110``Access logging suspended - configured space allocation exhausted.``
111   The space allocated to the event log files is full; you must either
112   increase the space or delete some log files so that access logging
113   to continue. To prevent this error, consider rolling log files more
114   frequently and enabling the autodelete feature.
115
116``Access logging suspended - no more space on the logging partition.``
117   The entire partition containing the event logs is full; you must
118   delete or move some log files to enable access logging to continue.
119   To prevent this error, consider rolling log files more frequently
120   and enabling the autodelete feature.
121
122``Created zero length place holder for config file <filename>``
123   Go to the Traffic Server ``config`` directory and check the
124   indicated file. If it is indeed zero in length, then use a backup
125   copy of the configuration file.
126
127``Traffic Server could not open logfile <filename>``
128   Check permissions for the indicated file and the logging directory.
129
130``Traffic Server failed to parse line <line number> of the logging config file <filename>``
131   Check your custom log configuration file; there could be syntax
132   errors. Refer to :ref:`custom-logging-fields` for correct custom log format fields.
133
134``vip_config binary is not setuid root, manager will be unable to enable virtual ip addresses``
135   The :program:`traffic_manager` process is not able to set virtual IP
136   addresses. You must ``setuid root`` for the ``vip_config`` file in
137   the Traffic Server ``bin`` directory.
138
139HTML Messages Sent to Clients
140=============================
141
142Traffic Server returns detailed error messages to browser clients when
143there are problems with the HTTP transactions requested by the browser.
144These Traffic Server response messages correspond to standard HTTP
145response codes, but provide more information. A list of the more
146frequently-encountered HTTP response codes is provided in :ref:`standard-http-response-messages`.
147You can customize the Traffic Server response messages (typically in 
148proxy/config/body_factory/default/, but set by 
149:ts:cv:`proxy.config.body_factory.template_sets_dir`).
150
151The following table lists the hard-coded Traffic Server HTTP messages,
152with corresponding HTTP response codes and customizable files.
153
154``Access Denied``
155   ``403``
156   You are not allowed to access the document at location ``URL``.
157   ``access#denied``
158
159``Cache Read Error``
160   ``500``
161   Error reading from cache; please retry request.
162   ``cache#read_error``
163
164``Connection Timed Out``
165   ``504``
166   Too much time has elapsed since the server has sent data.
167   ``timeout#inactivity``
168
169``Content Length Required``
170   ``400``
171   Could not process this request because ``Content-Length`` was not specified.
172   ``request#no_content_length``
173
174``Cycle Detected``
175   ``400``
176   Your request is prohibited because it would cause an HTTP proxy cycle.
177   ``request#cycle_detected``
178
179``Forbidden``
180    ``403``
181    ``<port number>`` is not an allowed port for SSL connections (you have made a request for a secure SSL connection to a forbidden port  number).
182    ``access#ssl_forbidden``
183
184``Host Header Required``
185   ``400``
186   An attempt was made to transparently proxy your request, but this
187   attempt failed because your browser did not send an HTTP ``Host``
188   header. Manually configure your browser to use
189   ``http://<proxy name>:<proxy port>`` as the HTTP
190   proxy. Alternatively, end users can upgrade to a browser that
191   supports the HTTP ``Host`` header field.
192   ``interception#no_host``
193
194``Host Header Required``
195   ``400``
196   Because your browser did not send a ``Host`` HTTP header field, the
197   virtual host being requested could not be determined. To access the
198   website correctly, you must upgrade to a browser that supports the
199   HTTP ``Host`` header field.
200   ``request#no_host``
201
202``HTTP Version Not Supported``
203   ``505``
204   The origin server ``<server name>`` is using an unsupported version
205   of the HTTP protocol.
206   ``response#bad_version``
207
208``Invalid Content Length``
209   ``400``
210   Could not process this request because the specified ``Content-Length``
211   was invalid (less than 0)..
212   ``request#invalid_content_length``
213
214``Invalid HTTP Request``
215   ``400``
216   Could not process this ``<client request>`` HTTP method request for ``URL``.
217   ``request#syntax_error``
218
219``Invalid HTTP Response``
220   ``502``
221   The host ``<server name>`` did not return the document ``URL`` correctly.
222   ``response#bad_response``
223
224``Malformed Server Response``
225   ``502``
226   The host ``<server name>`` did not return the document ``URL`` correctly.
227   ``response#bad_response``
228
229``Malformed Server Response Status``
230   ``502``
231   The host ``<server name>`` did not return the document ``URL`` correctly.
232   ``response#bad_response``
233
234``Maximum Transaction Time exceeded``
235   ``504``
236   Too much time has elapsed while transmitting document ``URL``.
237   ``timeout#activity``
238
239``No Response Header From Server``
240   ``502``
241   The host ``<server name>`` did not return the document ``URL`` correctly.
242   ``response#bad_response``
243
244``Not Cached``
245   ``504``
246   This document was not available in the cache, and you (the client)
247   only accept cached copies.
248   ``cache#not_in_cache``
249
250``Not Found on Accelerator``
251   ``404``
252   The request for ``URL`` on host ``<server name>`` was not found.
253   Check the location and try again.
254   ``urlrouting#no_mapping``
255
256``NULL``
257   ``502``
258   The host ``<hostname>`` did not return the document ``URL`` correctly.
259   ``response#bad_response``
260
261``Proxy Authentication Required``
262   ``407``
263   Please log in with username and password.
264   ``access#proxy_auth_required``
265
266``Server Hangup``
267   ``502``
268   The server ``<hostname>`` closed the connection before the transaction was completed.
269   ``connect#hangup``
270
271``Temporarily Moved``
272   ``302``
273   The document you requested, ``URL``, has moved to a new location. The new location is ``<new URL>``.
274   ``redirect#moved_temporarily``
275
276``Transcoding Not Available``
277   ``406``
278   Unable to provide the document ``URL`` in the format requested by your browser.
279   ``transcoding#unsupported``
280
281``Tunnel Connection Failed``
282   ``502``
283   Could not connect to the server ``<hostname>``.
284   ``connect#failed_connect``
285
286``Unknown Error``
287   ``502``
288   The host ``<hostname>`` did not return the document ``URL`` correctly.
289   ``response#bad_response``
290
291``Unknown Host``
292   ``500``
293   Unable to locate the server named ``<hostname>``; the server does
294   not have a DNS entry. Perhaps there is a misspelling in the server
295   name or the server no longer exists; double-check the name and try
296   again.
297   ``connect#dns_failed``
298
299``Unsupported URL Scheme``
300   ``400``
301   Cannot perform your request for the document ``URL`` because the
302   protocol scheme is unknown.
303   ``request#scheme_unsupported``
304
305
306.. _standard-http-response-messages:
307
308Standard HTTP Response Messages
309-------------------------------
310
311The following standard HTTP response messages are provided for your
312information.
313
314``200``
315   OK
316
317``202``
318   Accepted
319
320``204``
321   No Content
322
323``206``
324   Partial Content
325
326``300``
327   Multiple Choices
328
329``301``
330   Moved Permanently
331
332``302``
333   Found
334
335``303``
336   See Other
337
338``304``
339   Not Modified
340
341``400``
342   Bad Request
343
344``401``
345   Unauthorized; retry
346
347``403``
348   Forbidden
349
350``404``
351   Not Found
352
353``405``
354   Method Not Allowed
355
356``406``
357   Not acceptable
358
359``408``
360   Request Timeout
361
362``500``
363   Internal server error
364
365``501``
366   Not Implemented
367
368``502``
369   Bad Gateway
370
371``504``
372   Gateway Timeout
373