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 2013/07/02 22:15:21 UTC

[jira] [Closed] (TS-1573) does rolling options work for ATS?

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

Leif Hedstrom closed TS-1573.
-----------------------------

    Resolution: Cannot Reproduce
    
> does rolling options work for ATS?
> ----------------------------------
>
>                 Key: TS-1573
>                 URL: https://issues.apache.org/jira/browse/TS-1573
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 3.2.0
>         Environment: RHEL6.3
>            Reporter: Aidan McGurn
>             Fix For: 3.3.5
>
>
> I have configured my rolling options as follows:
> CONFIG proxy.config.log.rolling_enabled INT 1 << enabled
> CONFIG proxy.config.log.rolling_interval_sec INT 300   << min 5 mins
> CONFIG proxy.config.log.rolling_offset_hr INT 16  << 16 = 4pm today  (also left this running from yesterday)
> Above should have rolled @4pm and every 5 min's thereafter….
> I tried this and left it overnight without any logs appearing..
> looked under:
> .../tools/trafficserver/var/log/trafficserver/
> we have 2 logs from traffic server:
> 1. normal debug which is standard out which is redirected to file which the system uses for all standard out
> 2. ATS's errors in error.log
> i.e. in this setup do we expect at most the error.log to roll?
> Also for #1, is this not working becuause of the way we redirect std::out,
> (TS launched like this:
> master process -> calls perl script execs -> ATM -> ATS  - std:out redirected to central log file)
> could someone confirm or have an example of rolling working on 3.2.0 so i can work around the above limitations we may have set for ourselves?
> thanks,
> /aidan

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