I was able to sync LDAP at one point with Ambari. I'm not sure exactly when it broke. The users were synced before it broke all work fine and show up in Ambari as being Type: LDAP. When I try to run ambari-server sync-ldap with either the --existing option or --groups I get the same output complaining about the hostname. I have verified that hostname -f shows the correct FQDN and it matches what is output in the results of the command below. ambari-server sync-ldap --existing Using python /usr/bin/python Syncing with LDAP... Enter Ambari Admin login: adminusername Enter Ambari Admin password: Syncing existing.ERROR: Exiting with exit code 1. REASON: Sync event creation failed. Error details: hostname '127.0.0.1' doesn't match u'hiddenhostname.domain.com' ... View more

I installed a fresh HDP 2.6.1 cluster and then used Ambari to enable Kerberos. When it gets to the point of Start and Test services it hangs for a long time on starting the Namenode. Reviewing logs on the namenodes doesn't reveal much but all of the datanodes have jsvc.out files showing that the jsvc is continually core dumping. The datanode.out log file doesn't contain anything useful because it never gets up and running. ... View more

I am attempting to Express Upgrade from HDP 2.6.0.3 to HDP 2.6.1.0 and it fails when it gets to the "Restarting Knox Gateway on ..." step. The message in stderr is this: Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/KNOX/0.5.0.2.2/package/scripts/knox_gateway.py", line 217, in <module> KnoxGateway().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 329, in execute method(env) File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 850, in restart self.start(env, upgrade_type=upgrade_type) File "/var/lib/ambari-agent/cache/common-services/KNOX/0.5.0.2.2/package/scripts/knox_gateway.py", line 135, in start self.configure(env) File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 119, in locking_configure original_configure(obj, *args, **kw) File "/var/lib/ambari-agent/cache/common-services/KNOX/0.5.0.2.2/package/scripts/knox_gateway.py", line 67, in configure knox() File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, in thunk return fn(*args, **kwargs) File "/var/lib/ambari-agent/cache/common-services/KNOX/0.5.0.2.2/package/scripts/knox.py", line 100, in knox recursive_ownership = True, File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 114, in __new__ cls(names_list.pop(0), env, provider, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 147, in __init__ raise Fail("%s received unsupported argument %s" % (self, key)) resource_management.core.exceptions.Fail: Directory['/usr/hdp/current/knox-server/data/'] received unsupported argument recursive stdout doesn't look like it contains anything useful. gateway.log shows nothing because it isn't getting to the point where it tries to start it. If I manually start knox it seems to start fine. ... View more