Member since
06-20-2017
11
Posts
0
Kudos Received
0
Solutions
08-24-2017
12:15 PM
Yes that workaround does work. Will wait for a fix before I Accept the solution.
... View more
08-03-2017
04:51 PM
my /etc/hosts file only contains the 2 standard localhost lines. I have verified that both forward and revers DNS works correctly for the Ambari server and the LDAP server. I did try adding both of them into the /etc/hosts file in the format of "IP FQDN shortname" and that did not seem to make any difference at all. I looked at the ambari.properties file and it has the correct LDAP hostname in it.
... View more
08-03-2017
04:35 PM
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
Labels:
06-28-2017
09:10 PM
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
- Tags:
- datanode
- Hadoop Core
Labels:
06-23-2017
04:10 PM
I'm not sure how an old version of knox.py would have gotten there. Anyway I reverted snapshots back to before I did the upgrade and everything worked fine now. Something must have just gotten really messed up.
... View more
06-22-2017
09:49 PM
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
Labels:
06-22-2017
05:15 PM
I worked around the issue by using the API to add a HTTP based repository instead of using the Satellite Repo. I would prefer that Satellite repo's actually worked properly but in the meantime this is letting the upgrade go forward. I am now running into an issue during the upgrade with Knox but this is a different issue so I will start a new topic if I can't find a solution on my own.
... View more
06-21-2017
07:42 PM
Sorry I replied yesterday but the reply is above.
... View more
06-20-2017
04:48 PM
SQL> SELECT * FROM cluster_version;
ID REPO_VERSION_ID CLUSTER_ID STATE
---------- --------------- ---------- --------------------------------
START_TIME END_TIME USER_NAME
---------- ---------- --------------------------------
1 1 1 CURRENT
SQL> SELECT repo_version_id, stack_id, version, display_name FROM repo_version;
REPO_VERSION_ID STACK_ID
--------------- ----------
VERSION
--------------------------------------------------------------------------------
DISPLAY_NAME
--------------------------------------------------------------------------------
1 2
2.6.0.3-8
HDP-2.6
... View more
06-20-2017
03:36 PM
I installed HDP 2.5.0.3 using local Red Hat Satellite repos. Now if I go to Admin -> Stack and Versions -> Versions it hangs. Also if I go into Manage Versions, the current version is completely blank. I can register a new version and provide details for 2.5.1.0 and it appears fine but if I try to update the cluster to that version I get redirected to the Versions page that hangs. I have done DB queries and don't see anything off there. I have also verified that all nodes are showing the right CURRENT version. The error that I see in developer tools of web browsers is Unable to get property OperatingSystems. Screenshot attached.
... View more
Labels: