Traffic Server Alarm Messages - HP P4535A - Web Cache Server Appliance Administrator's Manual

Appendix F
Message
Unable to accept cluster connections on port:
<cluster port number>
Unable to open logfile <file name>, errno =
<error number>
unable to read cache segment

Traffic Server alarm messages

The following table describes alarm messages that you may see on the Dashboard page of Traffic Manager.
Message
[Rollback::Rollback] Config file is read-only:
<file name>
[Rollback::Rollback] Unable to read or write
config file <filename>
[Traffic Manager] Configuration File Update
Failed: <error number>
[Traffic Manager] Mgmt <==>Proxy conn.
closed
Access logging suspended - configured space
allocation exhausted.
Access logging suspended - no more space on
the logging partition.
Created zero length place holder for config file
<file name>
Traffic Server can't open <file name> for
reading custom formats
Traffic Server could not open logfile
<file name>
Description
Call technical support
Cannot open the log file.
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.
Description
Go to Traffic Server's
config
indicated file permissions; change them if necessary.
Go to Traffic Server's
config
the indicated file exists. Check its permissions and
change them if necessary.
Go to Traffic Server's
config
indicated file permissions; change them if necessary.
This is an informational message informing you that the
process was down. For example, you
traffic_server
would see this message if there was a restart.
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
files‚ on page 109.
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
page 109.
Go to Traffic Server's
config
indicated file. If it is indeed zero in length, use a backup
copy of the configuration file.
Make sure that the
proxy.config.log2.config_file
file contains the correct path to the
records.config
custom log configuration file (the default is
).
logs.config
Check permissions for the indicated file and the logging
directory.
Traffic Server Error Messages
directory and check the
directory and make sure
directory and check the
Rolling event log
Rolling event log files‚ on
directory and check the
variable in the
logging/
229