Nach der anpassung der zammad.conf im NGNIX und einen Neustart steht beim reindex das mit den 400er
Wenn ich dann Zammad per Webinterface neu installiert habe und was unter Statistik suche, bekomme im Modal diesen Fehler
Blockquote
{“error”:“Unable to process POST at hxxp://127.0.0.1:9200/zammad_production/Ticket/_search\n#\u003cUserAgent::Result:0x007f59f815a258 @success=false, @body=nil, @data=nil, @code="400", @content_type=nil, @error="Client Error: #\u003cNet::HTTPBadRequest 400 Bad Request readbody=true\u003e!"\u003e”}
Blockquote
can you provide some log output from your ES - startup and when you try to search.
The solution @anon8950880 provided could be correct.
Also please check if you set the ES url correct. zammad run rails r "Setting.set('es_url', 'http://localhost:9200')"
without a trailing “/” sometimes this is an issue to.
I don’t think that the RAM is an issue here. But Zammad and Elasticsearch need a lot of RAM because both apps are heavily utilising cacheing mechanism. Which are stored in the RAM.
We have several installations running using exactly these setup. So the logs will help to finde the point we or you missed.
How I understand zammad and elasticsearch is that zammad actually feeds/triggers elasticsearch.
When I had 400 & 500 errors, I was not using 5.6.x of elasticsearch and also “zammad run rake searchindex:rebuild” had errors.
On my Suse I had to run the above command twice for it to go through without error.
@PatrickGoenner Your error looks like a firewall problem or elasticsearch service not running.
You have to go through all the described steps for elasticsearch integration and maybe also check if your firewall is filtering pakets on localhost (shouldn’t do it but sometimes you never know…)
Also check, as written, if elasticsearch is running. If you installed elasticsearch and run the comments from the documentation, a service restart of zammad and elasticsearch may be necessary.
that was the key for me! I had installed, uninstalled and reinstalled elasticsearch so many times that I was bagning my head. Finally I tried the above command, and started the process over again and it worked.