Elastic Nest 7 , unknown from: POST /_reindex?wait_for_completion=true

Elastic Stack Elasticsearch
1

i'm reindexing docs from one index to another and usually i got this exception which i dont know what cause it, in my local pc i didnt have it but in az pipeline it happens frequently . this is the code i'm using to do the reindex :

var result = await client.ReindexOnServerAsync(r =>
            {
                return r.Source(s => s.Index(startIndex))
                    .Destination(d => d.Index(finalIndexName))
                    .Script(s=>s.Source(scriptContent.Source).Lang(scriptContent.Lang).Params(scriptContent.Params))
                    .WaitForCompletion();
            });

Elasticsearch.Net.ElasticsearchClientException: An error occurred while sending the request. Call: Status code unknown from: POST /_reindex?wait_for_completion=true
2024-10-16T09:48:05.2852394Z ---> System.Net.Http.HttpRequestException: An error occurred while sending the request.
2024-10-16T09:48:05.2854157Z ---> System.IO.IOException: The decryption operation failed, see inner exception.
2024-10-16T09:48:05.2855892Z ---> Interop+OpenSsl+SslException: Decrypt failed with OpenSSL error - SSL_ERROR_SSL.
2024-10-16T09:48:05.2857883Z ---> Interop+Crypto+OpenSslCryptographicException: error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac
2024-10-16T09:48:05.2859493Z --- End of inner exception stack trace ---

2

Hi @blqck ,

this is not an error caused by the NEST client.

DECRYPTION_FAILED_OR_BAD_RECORD_MAC means that either the server certificate is invalid, or the data has been tampered with.

There might be a SSL proxy that inspects traffic on your Azure pipeline or something similar.

3

Hii @flobernd ,

thanks for your comment.

what do you mean by the data has been tampered with ?
because i'm using Lucene script to make doc id = my entity id .
in case of tampered data what can i use to know what data has issue ?

4

Hi @blqck ,

tempered somewhere on the networking layer is what I meant :confused: Like with using a "man in the middle" (MITM) proxy or something similar.

This could as well happen, if you have package loss / packages get dropped for some reason.

I would definitely have a look at the virtual network of your Azure Pipeline and run some network diagnostics.