[
https://issues.apache.org/jira/browse/TS-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873885#comment-13873885
]
David Carlin commented on TS-2250:
----------------------------------
Should this be left open so that {{example_prep.sh}} and
{{example_alarm_bin.sh}} are updated then?
> 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
> Assignee: James Peach
> Fix For: 4.2.0
>
>
> 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 '/usr/local'
> FATAL: Can't acquire manager lockfile '/var/run/trafficserver/manager.lock'
> (No space left on device)
> [E. Mgmt] log ==> [TrafficManager] using root directory '/usr/local'
> [example_prep.sh] Checking/Moving old cores...
> [TrafficServer] using root directory '/usr/local'
> [example_alarm_bin.sh] sent alarm: <hostname> [TrafficManager] Traffic Server
> process was reset.
> [example_prep.sh] Checking/Moving old cores...
> [TrafficServer] using root directory '/usr/local'
> NOTE: Traffic Server received Sig 11: Segmentation fault
> /usr/local/bin/traffic_server - STACK TRACE:
> /lib64/libpthread.so.0(+0x383480f4a0)[0x2b67ccf414a0]
> [...]
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
