Traffic Server Process Fatal; Traffic Server Warnings - HP P4535A - Web Cache Server Appliance Administrator's Manual

Appendix F
Message
rolled file <file name> already exists, attempting
version <version>
"\"Vary: <header field>" —object not served from
cache

Traffic Server Process fatal

Message
accept port is not between 1 and 65535. Please
check configuration
self loop is detected in parent proxy
configuration

Traffic Server Warnings

Message
<Log file> error: <error number>
Bad cluster major version range
<version1-version2> for node <IP address>
connect failed
cache read error
can't open config file <config file name> for
reading custom formats
connect by disallowed client <IP address>,
closing
Could not rename <log file name> to <rolled
file name>
Did <this amount> of backup still to do
<remaining amount>
Different clustering minor versions <version 1,
version 2> for node <IP address> continuing
log format symbol <symbol name> not found
marking segment <segment identifier> corrupt Traffic Server is marking the indicated part of a disk as
missing field for field marker
No storage available. Cache disabled.
Description
Attempting to roll over existing file, so roll is
being changed.
Document content varies on header fields, so the
cached copy is not being served back to the
client.
Description
The port specified in the
records.config
accepting incoming HTTP requests is not valid.
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.
Description
Generic logging error.
Incompatible software versions causing a problem.
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.
Custom logging was enabled, but Traffic Server cannot
find the file.
logs.config
The specified client is not allowed to connect to the
Traffic Server proxy. The client IP address is not listed in
the file.
ip_allow.config
System error in renaming log file during roll.
Congestion is approaching.
Incompatible software versions causing a problem.
Custom log format references a field symbol that does not
exist. See Appendix E‚ Event Logging
corrupt. You may have to replace the disk.
Error in reading a log buffer.
There is no cache storage available. There is a
configuration or hardware problem. Check for other
syslog messages that give more specific information.
Traffic Server Error Messages
file for
Formats.
228