You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/02/02 17:20:08 UTC

[jira] [Updated] (TS-2250) No timestamps in traffic.out

     [ https://issues.apache.org/jira/browse/TS-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-2250:
------------------------------

    Fix Version/s:     (was: 4.2.0)

> 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
>
> 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)