[
https://issues.apache.org/jira/browse/RANGER-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-4180:
-------------------------------------
Fix Version/s: 2.5.0
> Log Dir for gc-worker.log is not using same VAR as logs dir for other ranger
> logs
> ---------------------------------------------------------------------------------
>
> Key: RANGER-4180
> URL: https://issues.apache.org/jira/browse/RANGER-4180
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
> Reporter: Jai Patel
> Assignee: Jai Patel
> Priority: Major
> Fix For: 3.0.0, 2.5.0
>
>
> While trying to use the "ranger_in_docker" script for bringing up ranger
> services on local, the log dir is set to "var/log/ranger" using the variable
> ${RANGER_ADMIN_LOG_DIR}.
> This path does not get used for gc-worker.log since its hardcoded to use
> -"Xloggc:${XAPOLICYMGR_EWS_DIR}/logs/gc-worker.log" in the
> "ranger-admin-services.sh" script.
> !image-2023-04-11-10-51-17-107.png!
> This causes issues for "gc-worker.log" to not be generated.
> While Java8 is fine with this error, when we use Java11, the JVM fails to
> start.
> Hence, raising this JIRA.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
