F Traffic Server Error Messages
This appendix contains the following sections:
Traffic Server error messages‚ on page 227
the system log file (messages)
Traffic Server alarm messages‚ on page 229
Monitor pages
HTML messages sent to clients‚ on page 230
to browser clients (not to be confused with standard HTTP response codes)
Standard HTTP response messages‚ on page 232
servers send to browser clients
Traffic Server error messages
The following table lists messages that can appear in messages files. This list is not exhaustive; it describes
messages that can occur and may require your attention.
Traffic Server Notes
Message
machine down <IP address>
machine up <IP address>, protocol version=<X.Y>,
Cluster notes
Cluster <IP address> not in config, declaring down
Cluster bbwrite to <IP address> failed, declaring down
Cluster network connection to <IP address> backing up
Cluster read from <IP address> failed, declaring down
Cluster write to <IP address> failed, declaring down
Illegal cluster connection from <IP address>
machine down <IP address:port>
machine down <IP address>
machine up <IP address:port>
machine up <IP address>
Network congestion to <IP address> cleared, reverting
to cache mode
Network congestion to <IP address> encountered,
reverting to proxy only mode
Unable to accept cluster connections
Host database notes
reconfiguring host database
<Hostname>'s round robin DNS entry updated,
entries=<entry number>, IP list: <IP list name>
Logging notes
describes the messages that Traffic Server software sends to
describes the alarm messages that appear in Traffic Manager
describes the HTML error messages that Traffic Server sends
describes the standard HTTP response codes that origin
Description
Machine with given IP address is down.
Machine with given IP address and protocol
version is up.
Congestion is cleared and cache capability
returns.
Traffic Server is too congested to cache and is
reverting to proxy only mode.
227