David Carlin created TS-2250:
--------------------------------
Summary: No timestamps in traffic.out
Key: TS-2250
URL: https://issues.apache.org/jira/browse/TS-2250
Project: Traffic Server
Issue Type: Bug
Components: Logging
Reporter: David Carlin
There are no timestamps in traffic.out. This makes it hard to know when things
happened, or to correlate logs. Some example output:
[E. Mgmt] log ==> [TrafficManager] using root directory '/home/y'
FATAL: Can't acquire manager lockfile
'/home/y/var/run/trafficserver/manager.lock' (No space left on device)
[E. Mgmt] log ==> [TrafficManager] using root directory '/home/y'
[example_prep.sh] Checking/Moving old cores...
[TrafficServer] using root directory '/home/y'
[example_alarm_bin.sh] sent alarm: <hostname> [TrafficManager] Traffic Server
process was reset.
[example_prep.sh] Checking/Moving old cores...
[TrafficServer] using root directory '/home/y'
NOTE: Traffic Server received Sig 11: Segmentation fault
/home/y/bin/traffic_server - STACK TRACE:
/lib64/libpthread.so.0(+0x383480f4a0)[0x2b67ccf414a0]
[...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
