Appdynamics / Appdynamics/appdynamics-cookbooks
Java_Agent permission problems on conf dir
- Dominant language
- Ruby
- Stars
- 28
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
When running Java Agent as a different user than root, the conf directory needs also be changed with the specificed owner and group, not only controller-info.xml
```
[AD Thread Pool-Global1] 19 Dec 2018 10:19:17,101 INFO TransactionConfigUpdater - Updating transactions.xml to /opt/appdynamics/javaagent/conf/hostname.domain.com/transactions.xml
[AD Thread Pool-Global1] 19 Dec 2018 10:19:17,101 INFO TransactionConfigUpdater - Failed to create directory [/opt/appdynamics/javaagent/conf/hostname.domain.com]
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the cookbook entry point that manages controller-info.xml and the Java Agent conf directory, then reproduce the setup as a non-root user. Check how ownership is applied when the hostname-specific directory is created; done means the specified owner and group can create or update transactions.xml without the logged permission failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, ruby
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100