You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2016/09/06 19:17:21 UTC
[jira] [Updated] (TS-4800) Fix logging.config reloading.
[ https://issues.apache.org/jira/browse/TS-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Peach updated TS-4800:
----------------------------
Summary: Fix logging.config reloading. (was: Verify that reloading logging.config works.)
> Fix logging.config reloading.
> -----------------------------
>
> 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)