Chef Backend HA default Elasticsearch mapping search failure

When the mappings/settings on a search index are the Elasticsearch defaults rather than what would be set by a successful chef-server-ctl reconfigure (while no traffic is coming into the Chef Backend HA cluster), attempted searches afterward will fail. This article addresses this scenario and provides suggestions to fix it. root@client1:~# knife search node '*:*' ERROR: knife search failed: invalid index name or query Frontend erchef request log: 2018-10-02T15:43:35Z erchef@127.0.0.1 method=GET; path=/organizations/4thcoffee/search/node?q=*:*&sort=X_CHEF_id_CHEF_X%20asc&start=0; status=400; req_id=g3IAA2QAEGVyY2hlZkAxMjcuMC4wLjEDAACIqgAAAAEAAAAA; org_name=4thcoffee; msg={solr_400,"/chef/_search"}; couchdb_groups=false; couchdb_organizations=false; couchdb_containers=false; couchdb_acls=false; 503_mode=false; couchdb_associations=false; couchdb_association_requests=false; req_time=40; rdbms_time=1; rdbms_count=3; solr_time=32; solr_count=1; user=me; req_api_version=1;

Was this article helpful?

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.