Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 11-09-2015 05:12 PM
During the install of SmartSense we are getting the following errors:
500 status code received on GET method for API: /api/v1/clusters/test/services?ServiceInfo/state=INSTALLED&ServiceInfo/service_name.in(SMARTSENSE)¶ms/run_smoke_test=true¶ms/reconfigure_client=false
Error message: org.apache.ambari.server.controller.spi.SystemException: An internal system exception occurred: Invalid transition for service, clusterName=test, clusterId=2, serviceName=SMARTSENSE, currentDesiredState=INIT, newDesiredState=STARTED
{ "status" : 500, "message" : "org.apache.ambari.server.controller.spi.SystemException: An internal system exception occurred: Invalid 'kdc_type' value: Existing MIT KDC" }
Created on 11-09-2015 05:51 PM - edited 08-19-2019 05:52 AM
I am getting the same or at least similar error after my Ranger installation. It looks like a bug in Ambari 2.1.2, be careful your installation might have messed up the "kdc_type" (go to <ambari_host>/api/v1/clusters/<clustername> search for kdc_type. If the value is something like "Existing MIT KDC", than you probably have to change it back to avoid any further issues)
Update: I discussed this problem with support and we came to the conclusion that this was a weird hick-up that coincidentally happened at the same time on our two clusters. I was not able to reproduce this issue and it seems like this issue did not come up somewhere else. If you still have the logs, please open a support case and forward them to support/engineering.
Created 11-09-2015 05:20 PM
whats your Ambari version? This might be an Ambari 2.1.2 issue, my Ranger installation just failed with the same error
Created 11-09-2015 05:28 PM
Yes. This is Ambari 2.1.2 on HDP 2.3.2
Created 11-09-2015 09:24 PM
Which kerberos wizard option did you use MIT, AD, or Manual?
Created on 11-09-2015 05:51 PM - edited 08-19-2019 05:52 AM
I am getting the same or at least similar error after my Ranger installation. It looks like a bug in Ambari 2.1.2, be careful your installation might have messed up the "kdc_type" (go to <ambari_host>/api/v1/clusters/<clustername> search for kdc_type. If the value is something like "Existing MIT KDC", than you probably have to change it back to avoid any further issues)
Update: I discussed this problem with support and we came to the conclusion that this was a weird hick-up that coincidentally happened at the same time on our two clusters. I was not able to reproduce this issue and it seems like this issue did not come up somewhere else. If you still have the logs, please open a support case and forward them to support/engineering.
Created 11-09-2015 05:52 PM
Created 11-09-2015 05:53 PM
thanks @Neeraj I will open a support ticket as well
Created 11-09-2015 06:00 PM
Is there an api command for changing the kdc_type?
Created 11-09-2015 06:08 PM
Checkout my answer in this post => http://community.hortonworks.com/questions/2421/ambari-append-to-env-templates-eg-hadoop-env-clean.h...
Let me know if you have any questions 🙂
Created 11-09-2015 06:21 PM
@Jonas Straub Nice!