Member since
10-12-2015
3
Posts
24
Kudos Received
0
Solutions
03-31-2017
10:28 PM
8 Kudos
Before Ambari 2.5.0, solr keytab was not on logsearch host, hence it is expected that user re-generates keytabs post Ambari upgrade before restarting LogSearch. Ambari has an option Regenerate Keytabs under Admin--> Kerberos to do the same
... View more
03-31-2017
10:11 PM
12 Kudos
I have LogSearch installed on cluster with Ambari 2.4.2.0 upgrade Ambari to 2.5.0 Log Search fails to start {code} resource_management.core.exceptions.ExecutionFailed: Execution of 'ambari-sudo.sh /usr/bin/kinit -kt /etc/security/keytabs/ambari-infra-solr.service.keytab infra-solr/<myintenalhost>@EXAMPLE.COM; ambari-sudo.sh curl -k -s --negotiate -u : http://<hostnamehere>:8886/solr/admin/authorization | grep authorization.enabled && ambari-sudo.sh /usr/bin/kinit -kt /etc/security/keytabs/ambari-infra-solr.service.keytab infra-solr/<hostname>@EXAMPLE.COM; ambari-sudo.sh curl -H 'Content-type:application/json' -d '{"set-user-role": {"logsearch@EXAMPLE.COM": ["logsearch_user", "ranger_admin_user", "dev"]}}' -s -o /dev/null -w'%{http_code}' --negotiate -u: -k http://<hostnamehere>:8886/solr/admin/authorization | grep 200' returned 1. kinit: Client not found in Kerberos database while getting initial credentials
... View more
Labels:
- Labels:
-
Apache Ambari
-
Apache Solr
-
Kerberos
-
Security