400 Bad Request when trying to reindex Magento 2

Elastic Stack Elasticsearch
1

I have a Magento 2 store running with Elasticsearch 7.x and Litemage. I’m getting the following error when trying to run an index job on Magento 2:


Design Config Grid index has been rebuilt successfully in 00:00:00
Customer Grid index has been rebuilt successfully in 00:00:00
Category Products index LiteMage purged tags cat_c
has been rebuilt successfully in 00:00:02
Product Categories index has been rebuilt successfully in 00:00:00
Catalog Rule Product index LiteMage purged tags cat_p,BLOCK_HTML
has been rebuilt successfully in 00:00:01
Product EAV index has been rebuilt successfully in 00:00:07
Stock index has been rebuilt successfully in 00:00:01
Inventory index LiteMage purged tags cat_p_2791
<!DOCTYPE html>
<html style="height:100%">
<head>
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" >
<title> 400 Bad Request
</title></head>
<body style="color: #444; margin:0;font: normal 14px/20px Arial, Helvetica, sans-serif; height:100%; background-color: #fff;">
<div style="height:auto; min-height:100%; ">     <div style="text-align: center; width:800px; margin-left: -400px; position:absolute; top: 30%; left:50%;">
        <h1 style="margin:0; font-size:150px; line-height:150px; font-weight:bold;">400</h1>
<h2 style="margin-top:20px;font-size: 30px;">Bad Request
</h2>
<p>It is not a valid request!</p>
</div></div></body></html>
has been rebuilt successfully in 00:00:14
Catalog Product Rule index has been rebuilt successfully in 00:00:00
Product Price index has been rebuilt successfully in 00:00:01
Catalog Search index has been rebuilt successfully in 00:00:08
Order Attributes Grid by Amasty index has been rebuilt successfully in 00:00:00
Mageplaza Reward Catalog Rule index has been rebuilt successfully in 00:00:00
Mageplaza Reward Product Rule index has been rebuilt successfully in 00:00:00

The issue only started once I did a "Transfer Inventory To Source" on certain products (e.g transferred inventory quantities from one source to another).

I've tried to disable litespeed_litemage module; going back to built-in cache, running the command (which doesn't give any errors) and then turning litemage back on (without success).

I'm stuck and need help.

2

Welcome to our community! :smiley:

We aren't Magento experts here, so not sure if we can help with that error above.
However I would suggest you look at the Elasticsearch logs and see if there is anything related.

3

Unfortunately, I am not sure what I am looking for in the logs

In elasticsearch_deprecation.log I see this

[2020-11-09T11:22:44,684][WARN ][o.e.d.a.b.BulkRequestParser] [el.za-dns.com] [types removal] Specifying types in bulk requests is deprecated.
[2020-11-09T11:23:01,630][WARN ][o.e.d.r.a.a.i.RestPutMappingAction] [el.za-dns.com] [types removal] Using include_type_name in put mapping requests is deprecated. The parameter will be removed in the next major version.

In gc.log

[2020-11-09T09:47:49.345+0000][20178][safepoint ] Safepoint "Cleanup", Time since last: 8001620078 ns, Reaching safepoint: 349167 ns, At safepoint: 34983 ns, Total: 384150 ns

in elasticsearch.log

[2020-11-09T11:22:10,617][INFO ][o.e.g.GatewayService ] [el.za-dns.com] recovered [1] indices into cluster_state
[2020-11-09T11:22:11,516][INFO ][o.e.c.r.a.AllocationService] [el.za-dns.com] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[magento2_product_1_v5][0]]]).
[2020-11-09T11:23:01,412][INFO ][o.e.c.m.MetadataCreateIndexService] [el.za-dns.com] [magento2_product_1_v6] creating index, cause [api], templates , shards [1]/[1]
[2020-11-09T11:23:01,747][INFO ][o.e.c.m.MetadataMappingService] [el.za-dns.com] [magento2_product_1_v6/Sl78cAOGSpCsY_ehRf6SEQ] create_mapping [document]
[2020-11-09T11:23:10,253][INFO ][o.e.c.m.MetadataMappingService] [el.za-dns.com] [magento2_product_1_v6/Sl78cAOGSpCsY_ehRf6SEQ] update_mapping [document]
[2020-11-09T11:23:10,991][INFO ][o.e.c.m.MetadataDeleteIndexService] [el.za-dns.com] [magento2_product_1_v5/rHsYbLVxTSy-bjqeP2E6NQ] deleting index
[2020-11-09T11:37:07,845][INFO ][o.e.c.m.MetadataCreateIndexService] [el.za-dns.com] [magento2_product_1_v7] creating index, cause [api], templates , shards [1]/[1]
[2020-11-09T11:37:08,108][INFO ][o.e.c.m.MetadataMappingService] [el.za-dns.com] [magento2_product_1_v7/4tOH82soSTO3BrV4WsSaxw] create_mapping [document]
[2020-11-09T11:37:16,348][INFO ][o.e.c.m.MetadataMappingService] [el.za-dns.com] [magento2_product_1_v7/4tOH82soSTO3BrV4WsSaxw] update_mapping [document]
[2020-11-09T11:37:17,016][INFO ][o.e.c.m.MetadataDeleteIndexService] [el.za-dns.com] [magento2_product_1_v6/Sl78cAOGSpCsY_ehRf6SEQ] deleting index
[2020-11-09T11:40:35,357][INFO ][o.e.c.m.MetadataCreateIndexService] [el.za-dns.com] [magento2_product_1_v8] creating index, cause [api], templates , shards [1]/[1]
[2020-11-09T11:40:35,606][INFO ][o.e.c.m.MetadataMappingService] [el.za-dns.com] [magento2_product_1_v8/Nsyu61SpS962XK30MHuvuw] create_mapping [document]
[2020-11-09T11:40:43,873][INFO ][o.e.c.m.MetadataMappingService] [el.za-dns.com] [magento2_product_1_v8/Nsyu61SpS962XK30MHuvuw] update_mapping [document]
[2020-11-09T11:40:44,514][INFO ][o.e.c.m.MetadataDeleteIndexService] [el.za-dns.com] [magento2_product_1_v7/4tOH82soSTO3BrV4WsSaxw] deleting index
[2020-11-09T11:41:45,387][INFO ][o.e.c.m.MetadataCreateIndexService] [el.za-dns.com] [magento2_product_1_v9] creating index, cause [api], templates , shards [1]/[1]
[2020-11-09T11:41:45,618][INFO ][o.e.c.m.MetadataMappingService] [el.za-dns.com] [magento2_product_1_v9/EkjplCdlT92aY9BkOloNew] create_mapping [document]
[2020-11-09T11:41:53,784][INFO ][o.e.c.m.MetadataMappingService] [el.za-dns.com] [magento2_product_1_v9/EkjplCdlT92aY9BkOloNew] update_mapping [document]
[2020-11-09T11:41:54,523][INFO ][o.e.c.m.MetadataDeleteIndexService] [el.za-dns.com] [magento2_product_1_v8/Nsyu61SpS962XK30MHuvuw] deleting index

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.