229
Appendix F
Traffic Server Error Messages
Traffic Server alarm messages
The following table describes alarm messages that you may see on the Dashboard page of Traffic Manager.
Unable to accept cluster connections on port:
<cluster port number>
Call technical support
Unable to open logfile <file name>, errno =
<error number>
Cannot open the log file.
unable to read cache segment
The garbage collector is unable to read cache segments in
the following cases: if the segment is corrupt, if the pool
the segment is in is corrupt, or if there is an actual disk
error while trying to read the segment. This warning is
usually accompanied by a warning indicating that the
segment is being marked as corrupt.
Message
Description
[Rollback::Rollback] Config file is read-only:
<file name>
Go to Traffic Server’s
config
directory and check the
indicated file permissions; change them if necessary.
[Rollback::Rollback] Unable to read or write
config file <filename>
Go to Traffic Server’s
config
directory and make sure
the indicated file exists. Check its permissions and
change them if necessary.
[Traffic Manager] Configuration File Update
Failed: <error number>
Go to Traffic Server’s
config
directory and check the
indicated file permissions; change them if necessary.
[Traffic Manager] Mgmt <==>Proxy conn.
closed
This is an informational message informing you that the
traffic_server
process was down. For example, you
would see this message if there was a restart.
Access logging suspended - configured space
allocation exhausted.
The space allocated to the event log files is full. You must
either increase the space or delete some log files to enable
access logging to continue. To prevent this from
happening, consider rolling log files more frequently and
enabling the autodelete feature. See
Rolling event log
files‚ on page 109
.
Access logging suspended - no more space on
the logging partition.
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 from happening,
consider rolling log files more frequently and enabling
the autodelete feature. See
Rolling event log files‚ on
page 109
.
Created zero length place holder for config file
<file name>
Go to Traffic Server’s
config
directory and check the
indicated file. If it is indeed zero in length, use a backup
copy of the configuration file.
Traffic Server can’t open <file name> for
reading custom formats
Make sure that the
proxy.config.log2.config_file
variable in the
records.config
file contains the correct path to the
custom log configuration file (the default is
logging/
logs.config
).
Traffic Server could not open logfile
<file name>
Check permissions for the indicated file and the logging
directory.
Message
Description