
228
Appendix F
Traffic Server Error Messages
Traffic Server Process fatal
Traffic Server Warnings
rolled file <file name> already exists, attempting
version <version>
Attempting to roll over existing file, so roll is
being changed.
“\”Vary: <header field>” —object not served from
cache
Document content varies on header fields, so the
cached copy is not being served back to the
client.
Message
Description
accept port is not between 1 and 65535. Please
check configuration
The port specified in the
records.config
file for
accepting incoming HTTP requests is not valid.
self loop is detected in parent proxy
configuration
The name and port of the parent proxy are the same as
that of Traffic Server. This creates a loop when Traffic
Server attempts to send the request to the parent proxy.
Message
Description
<Log file> error: <error number>
Generic logging error.
Bad cluster major version range
<version1-version2> for node <IP address>
connect failed
Incompatible software versions causing a problem.
cache read error
If this message appears by itself, it might indicate a cache
read problem; call Technical Support. If it appears with
other cache warnings such as unable to read cache
segment, marking segment corrupt, or unable to write
pool header, there is a disk problem. You may have to
replace your disk.
can't open config file <config file name> for
reading custom formats
Custom logging was enabled, but Traffic Server cannot
find the
logs.config
file.
connect by disallowed client <IP address>,
closing
The specified client is not allowed to connect to the
Traffic Server proxy. The client IP address is not listed in
the
ip_allow.config
file.
Could not rename <log file name> to <rolled
file name>
System error in renaming log file during roll.
Did <this amount> of backup still to do
<remaining amount>
Congestion is approaching.
Different clustering minor versions <version 1,
version 2> for node <IP address> continuing
Incompatible software versions causing a problem.
log format symbol <symbol name> not found
Custom log format references a field symbol that does not
exist. See
Appendix E‚ Event Logging Formats
.
marking segment <segment identifier> corrupt
Traffic Server is marking the indicated part of a disk as
corrupt. You may have to replace the disk.
missing field for field marker
Error in reading a log buffer.
No storage available. Cache disabled.
There is no cache storage available. There is a
configuration or hardware problem. Check for other
syslog
messages that give more specific information.
Message
Description