You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Geoffrey Corey (JIRA)" <ji...@apache.org> on 2015/04/03 20:39:54 UTC

[jira] [Comment Edited] (INFRA-9383) Change JIRA catalina log to have timestamp

    [ https://issues.apache.org/jira/browse/INFRA-9383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394880#comment-14394880 ] 

Geoffrey Corey edited comment on INFRA-9383 at 4/3/15 6:39 PM:
---------------------------------------------------------------

I was looking under /x1/, so I was more than likely in the wrong folder location.

EDIT: /usr/local/tomcat is a symlink to /x1/jira, Looks like I just didn't know what I was looking for in the logs.


was (Author: coreyg):
I was looking under /x1/, so I was more than likely in the wrong folder location.

> Change JIRA catalina log to have timestamp
> ------------------------------------------
>
>                 Key: INFRA-9383
>                 URL: https://issues.apache.org/jira/browse/INFRA-9383
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Geoffrey Corey
>            Priority: Minor
>
> When creating a new project in JIRA, it (again) got into a weird state and needs to be restarted to fix it. When trying to find the cause in the logs, there is no reference for where in the catalina log file to start looking because there is no timestamp. It would be helpful to have that for future debugging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)