Member since
09-25-2015
51
Posts
32
Kudos Received
4
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2018 | 04-06-2017 07:10 PM | |
6361 | 08-24-2016 06:55 PM | |
5037 | 12-16-2015 03:44 PM | |
5871 | 12-08-2015 12:54 PM |
07-20-2016
06:02 PM
1 Kudo
In the ambari DB you would do: update host_role_command set status = 'COMPLETED' where request_id = 1; Also, instead of the other options you took, you could have set 17,829 to completed with almost the same command: update host_role_command set status = 'COMPLETED' where task_id = 17829;
... View more
07-05-2016
01:31 PM
Guilhemme, Could you please do a : yum whatprovides 'ambari-admin-password-reset' I just checked my 2.2.2 install and I do not see it: [root@mon-orlan ~]# ambari (hit tab to complete) ambari-python-wrap ambari-server ambari_server_main.py ambari-server.py
... View more
02-26-2016
04:33 PM
3 Kudos
Most customers actually have user ambari for the database, so it would actually be: 2. Run 'psql -U ambari ambari'
... View more
12-17-2015
06:36 PM
1 Kudo
OK, you are in a bad way. Can you get to Admin - Kerberos, and tell me do you have a disable kerberos button? I think your best bet would be to disable it, and then redeploy it.
... View more
12-17-2015
01:03 PM
1 Kudo
What do you get as output if you do: /var/lib/ambari-server/resources/scripts/configs.sh -u AMBARI_USER -p AMBARI_PASS get AMBARI_SERVER CLUSTER_NAME kerberos-env
... View more
12-16-2015
04:38 PM
3 Kudos
You in fact do have one hbase installed, the one internal to ambari metrics, and it needs to stay running. I think you may have an issue I have seen before, can you add this to your ambari.properties file: server.timeline.metrics.cache.disabled = true and then restart ambari, let me know if this helps.
... View more
12-16-2015
03:44 PM
3 Kudos
There is a similar issue in our database of issues. Can you follow this: Manually add the kerberos-env/kdc_type property back to the current kerberos-env configuration. The value must be either "mit-kdc" or "active-directory" and must be the correct one for the configuration. Once this is done, Ambari should be restarted so that any cached configuration data is refreshed. (This can be done with configs.sh command). /var/lib/ambari-server/resources/scripts/configs.sh -u AMBARI_USER -p AMBARI_PASS set hdp23 hdp23 kerberos-env kdc_type "<kdc_type_value>"
... View more
12-08-2015
05:12 PM
7 Kudos
In a browser put in: http://<AMBARI-HOST>:8080/api/v1/clusters/<CLUSTER-NAME>/requests/ Find the highest reqest number in the output. Now, we can go to each request by pasting in the number of the request, an example would be: http://<AMBARI-HOST>:8080/api/v1/clusters/<CLUSTER-NAME>/requests/110 The output should look like: {
"href" : "http://mon-orlan:8080/api/v1/clusters/test/requests/110",
"Requests" : {
"aborted_task_count" : 0,
"cluster_name" : "test",
"completed_task_count" : 3,
"create_time" : 1444340395849,
"end_time" : 1444340449936,
"exclusive" : false,
"failed_task_count" : 0,
"id" : 110,
"inputs" : "{}",
"operation_level" : "SERVICE",
"progress_percent" : 100.0,
"queued_task_count" : 0,
"request_context" : "Restart all components with Stale Configs for HIVE",
.....
If that is not your hung operation, go back one by one from the highest request number. What we are looking for is the request context matches your hung Operation, that is the one we want to abort. Once you find that request ID, then go to the ambari server command line as root and do: curl -u admin:admin -i -H "X-RequestedBy:ambari" -X PUT -d '{"Requests":{"request_status":"ABORTED","abort_reason":"Aborted by user"}}' http://localhost:8080/api/v1/clusters/<CLUSTER_NAME>/requests/<REQUEST_ID>;
... View more
Labels:
12-08-2015
01:02 PM
All, I think you may have missed an important thing: sudo /usr/sbin/ambari-server setup-ldap Using python/usr/bin/python2.7 Setting up LDAP properties... We only support python 2.6.6, using 2.7 causes many many issues. Please use python 2.6.6. Also, I suggest you do an ldapsearch to test your settings: ldapsearch -x -H ldap://ldap.xxxxx.com -b dc=CENTENE,dc=com -D "CN=xxxxxx,OU=LDAP,DC=xxxxxxx,DC=com" -W "(sAMAccountName=<User-to-search-for>)"
... View more
12-08-2015
12:54 PM
So the official support answer, as per the doc listed above is NO. We support 5.6, but not 5.7. It has issues with at least Ranger, and has not been tested at all. I would think the heavier the cluster is used the more you would find it non-compatible with. Please use the supported version.
... View more
- « Previous
-
- 1
- 2
- Next »