Troubleshooting Apache Ranger Admin¶

Log File Location for Apache Ranger Admin¶

There are couple of different ways you can access it

Privacera Diagnostic Tool¶

You can use the Privacera Diagnostic Tool to view the logs for Apache Ranger Admin. After logging into the Privacera Diagnostics Server, go the Ranger Admin pod and click on the "POD EXPLORER" tab and clice on the service_logs link to list the logs.

Kubectl or K9s¶

You can get on to the Ranger pod using kubectl or K9s. The log files for Apache Ranger Admin pod are located in the following directory:

1

cd /opt/ranger/ranger-admin/ews/logs

Log Files¶

The following log file(s) are relevant for Apache Ranger Admin:

Enable Debug Logging¶

To enable debug logging for Apache Ranger Admin, you can set the RANGER_ADMIN_LOG_LEVEL configuration parameter to DEBUG. This configuration allows you to view detailed logs for Apache Ranger Admin to troubleshoot issues.

Go to the server where Privacera Manager is installed and navigate to the configuration directory:

1
2
3
4

cd ~/privacera/privacera-manager/config
# Copy the sample vars file to the custom vars directory if it does not exist in custom-vars directory
cp -n sample-vars/vars.ranger.admin.yml custom-vars/
vi custom-vars/vars.ranger.admin.yml

Add the following property and set it to DEBUG. If the property already exists, update the value to DEBUG:

1

RANGER_LOG_LEVEL: "DEBUG"

After making the changes, save the file and run the following command to apply the configuration changes and restart the Ranger Admin service:

Step 1 - Setup which generates the helm charts. This step usually takes few minutes.

1
2

cd ~/privacera/privacera-manager
./privacera-manager.sh setup

1
2

cd ~/privacera/privacera-manager
./pm_with_helm.sh upgrade

After restarting the Ranger Admin service, you should be able to see detailed logs in the Ranger Admin log files.

Revert to Default Log Level¶

It is not advised to run Apache Ranger Admin with debug logging enabled in production environments. To revert to the default log level, set the RANGER_LOG_LEVEL configuration parameter to INFO or comment out the property in the custom-vars/vars.ranger.admin.yml file. After making the changes, save the file and run the commands to apply the configuration changes and restart the Ranger Admin service:

Comments