[ https://issues.apache.org/jira/browse/TS-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102336#comment-15102336 ]
Peter Chou commented on TS-4134: -------------------------------- Alan, the problem was evident only when running as a non-root user. I applied your patch and it seems to be working fine now. It also seemed to fix another issue where running 'trafficserver start' would only start traffic_cop and subsequently traffic_manager would have to be started manually and separately. Thanks for explaining about the scoping/destructor/auto-de-elevate behavior and for the quick response. > Traffic Manager aborts on attempted privilege escalation when non-root. > ----------------------------------------------------------------------- > > Key: TS-4134 > URL: https://issues.apache.org/jira/browse/TS-4134 > Project: Traffic Server > Issue Type: Bug > Affects Versions: 6.2.0 > Reporter: Peter Chou > Assignee: Alan M. Carroll > Fix For: 6.1.0 > > > Traffic Manager aborts since it cannot elevate access in mgmt/Rollback.cc and > mgmt/LocalManager.cc. The root of the issue might be that the semantics of > the ElevateAccess constructor argument was changed from (boolean,level) to > just a (level) by commit 6a5f6241 or TS-306. It seems the ElevateAccess > access( <boolean-expression> ) calls in these two files were not changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)