During hdp upgrade Ranger PID file not being read if custom location is provided and non-standard service account is used

[#1]

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