Community Articles
Find and share helpful community-sourced technical articles
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
Labels (1)
Contributor

Issue:

If there is a custom PID location configured for services and a non standard service account other than user "ranger", before finalizing upgrade, Ambari shows Ranger service as stopped.

Solution:

Confirm that the Ranger process is running:

ps -ef | grep ranger

The pid and the chown values are hard coded in the /usr/bin/ranger*.

From this location, start and stop are called.

The pidf and the chown values are hard coded in the /usr/bin/ranger-admin from where start and stop are called if you invoke the same from ambari UI.

after changing those values to custom parameters ambari reported the service as running from UI.

Previous value:

cd /usr/bin

cat ranger-admin | grep -i pid

pidf=/var/run/ranger/rangeradmin.pid

New value:

vi ranger-admin

pidf=<custom location>

Save and quit

After changing these values restart ranger service from ambari

244 Views
Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
1 of 1
Last update:
‎12-31-2016 08:14 PM
Updated by:
 
Contributors
Top Kudoed Authors