Community Articles
Find and share helpful community-sourced technical articles
Labels (2)
Cloudera Employee

PROBLEM:

Changed Ambari from root to non-root user and hiveview doesn't work. Ambari hive view fails with Usernames not matched error. ERROR:

  Service 'userhome' check failed:
java.io.IOException: Usernames not matched: name=ambari-server-<cluster_name> != expected=<custom_user>
   at sun.reflect.GeneratedConstructorAccessor243.newInstance(Unknown Source)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
   at org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)

ROOT CAUSE: Configuration issue on Ambari Hive view definition as username doesn't match.

SOLUTION: Navigate to Hive and YARN Configs in Ambari UI and change as below and restart respective services.

A) Custom webhcat-site

webhcat.proxyuser.<AMBARI_SERVER_PRINCIPAL_USER>.groups=*
webhcat.proxyuser.<AMBARI_SERVER_PRINCIPAL_USER>.hosts=*
B) Custom yarn-site
yarn.timeline-service.http-authentication.<AMBARI_SERVER_PRINCIPAL_USER>.groups=*
yarn.timeline-service.http-authentication.<AMBARI_SERVER_PRINCIPAL_USER>.hosts=*
yarn.timeline-service.http-authentication.<AMBARI_SERVER_PRINCIPAL_USER>.users=*
1,647 Views
Comments
Expert Contributor

Hi @apatel can you validate the custom yarn-site properties once again.

yarn.timeline-service.http-authentication.proxyuser.<AMBARI_SERVER_PRINCIPAL_USER>.groups=*
yarn.timeline-service.http-authentication.proxyuser.<AMBARI_SERVER_PRINCIPAL_USER>.hosts=*
yarn.timeline-service.http-authentication.proxyuser.<AMBARI_SERVER_PRINCIPAL_USER>.users=*