Oleg Nechiporenko created AMBARI-6402:
-----------------------------------------
Summary: Many services failed to start when using custom user
names and groups
Key: AMBARI-6402
URL: https://issues.apache.org/jira/browse/AMBARI-6402
Project: Ambari
Issue Type: Bug
Components: client
Affects Versions: 1.6.1
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Priority: Blocker
Fix For: 1.6.1
On Customize services page set next values for users and groups:
{quote}
Name: Value
Proxy group for
Hive,WebHCat,
Oozie
and Falcon: custom-usersgr
HDFS User: custom-hdfs
MapReduce User: custom-mapred
YARN User: custom-yarn
HBase User: custom-hbase
Hive User: custom-hive
HCat User: custom-hcat
WebHCat User: custom-hcat
Oozie User: custom-oozie
Falcon User: custom-falcon
Storm User: custom-storm
ZooKeeper User: custom-zookeeper
Ganglia User: custom-nobody
Nagios User: custom-nagios
Nagios Group: custom-nagiosgr
Smoke Test User: ambari-qa
Tez User: custom-tez
Hadoop Group: custom-hadoopgr
Skip group
modifications
during install: false
{quote}
After deploy many services fail to start:
MapReduce, Hbase, Hive, WebHcat, Falcon, Oozie
Same error for all:
Call From ins1404365245-9.cs1cloud.internal/172.18.145.154 to localhost:8020
failed on connection exception: java.net.ConnectException: Connection refused;
For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
--
This message was sent by Atlassian JIRA
(v6.2#6252)