Created 12-12-2017 12:28 AM
Below is the Exception that shows up when starting the Ambari Infra service for the solr instance.
Not sure where the kerberos-env needs to be set? Or what is the underlying issue. The ambari-infra keytabs are present in the /etc/security/keytabs folder.
===========================================================================================
Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA/0.1.0/package/scripts/infra_solr.py", line 123, in <module> InfraSolr().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 367, in execute method(env) File "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA/0.1.0/package/scripts/infra_solr.py", line 46, in start self.configure(env) File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 120, in locking_configure original_configure(obj, *args, **kw) File "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA/0.1.0/package/scripts/infra_solr.py", line 41, in configure setup_infra_solr(name = 'server') File "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA/0.1.0/package/scripts/setup_infra_solr.py", line 101, in setup_infra_solr mode=0640) File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 166, in __init__ self.env.run() File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run self.run_action(resource, action) File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action provider_action() File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 123, in action_create content = self._get_content() File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 160, in _get_content return content() File "/usr/lib/python2.6/site-packages/resource_management/core/source.py", line 52, in __call__ return self.get_content() File "/usr/lib/python2.6/site-packages/resource_management/core/source.py", line 144, in get_content rendered = self.template.render(self.context) File "/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py", line 891, in render return self.environment.handle_exception(exc_info, True) File "/var/lib/ambari-agent/cache/common-services/AMBARI_INFRA/0.1.0/package/templates/infra-solr-security.json.j2", line 28, in top-level template code "{{atlas_kerberos_service_user}}@{{kerberos_realm}}": ["{{infra_solr_role_atlas}}", "{{infra_solr_role_ranger_audit}}", "{{infra_solr_role_dev}}"], File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py", line 73, in __getattr__ raise Fail("Configuration parameter '" + self.name + "' was not found in configurations dictionary!") resource_management.core.exceptions.Fail: Configuration parameter 'kerberos-env' was not found in configurations dictionary! ==============================================================================================
Created 12-12-2017 07:58 AM
# locate zookeeper Client
# locate zkCli /usr/hdp/2.6.2.0-205/zookeeper/bin/zkCli.sh
Go tp the bin directory
# cd /usr/hdp/2.6.2.0-205/zookeeper # bin/zkCli.sh
Check the configs stored in zookeeper, there should be that of solr_infra
[zk: localhost:2181(CONNECTED) 0] ls /
To get the live Solr node you should get a similar output
[zk: localhost:2181(CONNECTED) 7] ls /infra-solr/live_nodes [xxxxxx.com:8886_solr] [zk: localhost:2181(CONNECTED) 8] ls /infra-solr/collections [vertex_index, edge_index, fulltext_index] [zk: localhost:2181(CONNECTED) 9] ls /infra-solr/overseer_elect [leader, election] [zk: localhost:2181(CONNECTED) 10] ls /infra-solr/security.json []
Delete the Solr_infra entry in zookeeper
[zk: localhost:2181(CONNECTED) 10] rmr /infra-solr
Restart Infra_solr this should reload the config into zookeeper and it should start successfully
Created 12-13-2017 03:25 AM
@Geoffrey Shelton Okot - The instruction above does not solve the issue. Still have the same problem.
Created 01-15-2018 06:45 PM
currently getting the same...
did you manage to resolve this issue? If yes, how?
Thanks
Bruno