https://datahubproject.io logo
Join Slack
Powered by
So we had Datahub running in AWS using v0.8.45 and...
# troubleshoot
s
So we had Datahub running in AWS using v0.8.45 and just ran the updated helm charts to update to v0.10.0 and I'm seeing a lot of warnings in the gms pod:
Copy code
2023-02-10 21:53:46,052 [qtp447981768-17] WARN  c.d.a.a.AuthenticatorChain:80 - Authentication chain failed to resolve a valid authentication. Errors: [(com.datahub.authentication.authenticator.DataHubSystemAuthenticator,Failed to authenticate inbound request: Authorization header is missing Authorization header.), (com.datahub.authentication.authenticator.DataHubTokenAuthenticator,Failed to authenticate inbound request: Request is missing 'Authorization' header.)]
The datahub site seems to be up and running. But when trying to search for entities I keep seeing a notification "An unknown error occurred. (Code 500). All the pods seem to be running and this warning is all I keep seeing.
✅ 1
I was also getting the following errors logged from the gms pod:
Copy code
Suppressed: org.elasticsearch.client.ResponseException: method [POST], host [<https://search-datahub-cihpbucl53m35jsrl3nlj5a2vm.us-west-2.es.amazonaws.com:443>], URI [/datasetindex_v2/_search?typed_keys=true&max_concurrent_shard_requests=5&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&ignore_throttled=true&search_type=query_then_fetch&batched_reduce_size=512&ccs_minimize_roundtrips=true], status line [HTTP/1.1 400 Bad Request]
{"error":{"root_cause":[{"type":"parsing_exception","reason":"[match_phrase_prefix] query does not support [zero_terms_query]","line":1,"col":1932}],"type":"x_content_parse_exception","reason":"[1:1932] [bool] failed to parse field [must]","caused_by":{"type":"x_content_parse_exception","reason":"[1:1932] [bool] failed to parse field [should]","caused_by":{"type":"x_content_parse_exception","reason":"[1:1932] [bool] failed to parse field [should]","caused_by":{"type":"parsing_exception","reason":"[match_phrase_prefix] query does not support [zero_terms_query]","line":1,"col":1932}}}},"status":400}
For those that may experience the same issue., I was able to resolve both problems by tearing down the AWS OpenSearch instance (which was using ElasticSearch v7.9) and rebuilding it using OpenSearch v2.3. I also commented the following settings under global.elasticseearch in the values.yaml file:
Copy code
# skipcheck: "false"
# insecure: "false"
This seemed to fix both issues.
w
@silly-angle-91497 did you fix the 
Authentication chain failed to resolve a valid authentication
? if yes then how ?
22 Views
Open in Slack
PreviousNext
Powered by