[ 
https://issues.apache.org/jira/browse/TS-4800?focusedWorklogId=28217&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-28217
 ]

ASF GitHub Bot logged work on TS-4800:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Sep/16 19:16
            Start Date: 06/Sep/16 19:16
    Worklog Time Spent: 10m 
      Work Description: GitHub user jpeach opened a pull request:

    https://github.com/apache/trafficserver/pull/969

    TS-4800: Fix logging.config reloading.

    We were still listening for reconfiguration events on the old XML
    log file record. Fix logging.config reload by listening on the
    correct record name.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jpeach/trafficserver fix/4800

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/969.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #969
    
----
commit 424d6abbb4dcfc05352083feffffb07b0e9f5c90
Author: James Peach <jpe...@apache.org>
Date:   2016-09-06T19:11:45Z

    TS-4800: Fix logging.config reloading.
    
    We were still listening for reconfiguration events on the old XML
    log file record. Fix logging.config reload by listening on the
    correct record name.

----


Issue Time Tracking
-------------------

            Worklog Id:     (was: 28217)
            Time Spent: 10m
    Remaining Estimate: 0h

> Verify that reloading logging.config works.
> -------------------------------------------
>
>                 Key: TS-4800
>                 URL: https://issues.apache.org/jira/browse/TS-4800
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Logging
>            Reporter: James Peach
>            Priority: Blocker
>             Fix For: 7.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Seen in my dev environment:
> {noformat}
> [Aug 30 23:54:46.884] Manager {0x7fa0c82b6700} NOTE: 
> [Rollback::checkForUserUpdate] Failed to roll changed user file 
> logging.config: System Call Error
> [Aug 30 23:54:46.884] Manager {0x7fa0c82b6700} NOTE: User has changed config 
> file logging.config
> [Aug 30 23:55:07.406] Manager {0x7fa0c82b6700} NOTE: 
> [Rollback::internalUpdate] Link failed : Operation not permitted
> [Aug 30 23:55:07.406] Manager {0x7fa0c82b6700} NOTE: [Alarms::signalAlarm] 
> Skipping Alarm: '[TrafficManager] Configuration File Update Failed: Operation 
> not permitted'
> [Aug 30 23:55:07.406] Manager {0x7fa0c82b6700} NOTE: 
> [Rollback::checkForUserUpdate] Failed to roll changed user file 
> logging.config: System Call Error
> [Aug 30 23:55:07.406] Manager {0x7fa0c82b6700} NOTE: User has changed config 
> file logging.config
> {noformat}
> Seems like reloading is not working correctly.



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

Reply via email to