[solved]ElasticSearch: RuntimeError: Unable to process POST request

Has anyone had this error before… just upgraded ES and the latest build of Zammad?

Dec 13 12:12:43 Updated: elasticsearch-5.6.14-1.noarch
Dec 13 12:13:46 Updated: zammad-2.8.0-1544520749.33c77b09.centos7.x86_64

E, [2018-12-13T13:33:36.164165 #28945-47317138057960] ERROR -- : 2018-12-13T13:33:36+0200: [Worker(host:jhb-io-ter-web-1.directel.co.za pid:28945)] Job BackgroundJobSearchIndex (id=60421) FAILED (4 prior attempts) with RuntimeError: Unable to process POST request to elasticsearch URL 'http://127.0.0.1:9200/zammad_production/StatsStore/39?pipeline=zammad995361596052'. Check the response and payload for detailed information: 

Response:
#<UserAgent::Result:0x00007f9db88b97e8 @success=false, @body="{\"error\":{\"root_cause\":[{\"type\":\"illegal_argument_exception\",\"reason\":\"pipeline with id [zammad995361596052] does not exist\"}],\"type\":\"illegal_argument_exception\",\"reason\":\"pipeline with id [zammad995361596052] does not exist\"},\"status\":400}", @data=nil, @code="400", @content_type=nil, @error="Client Error: #<Net::HTTPBadRequest 400 Bad Request readbody=true>!">

Payload:
{"id"=>39, "stats_store_object_id"=>1, "o_id"=>123, "key"=>"dashboard", "related_o_id"=>nil, "related_stats_store_object_id"=>nil, "data"=>{"StatsTicketChannelDistribution"=>{"channels"=>{"email"=>{"icon"=>"email", "inbound"=>0, "outbound"=>0, "inbound_in_percent"=>0, "outbound_in_percent"=>0}, "phone"=>{"icon"=>"phone", "inbound"=>0, "outbound"=>0, "inbound_in_percent"=>0, "outbound_in_percent"=>0}, "twitter"=>{"icon"=>"twitter", "inbound"=>0, "outbound"=>0, "inbound_in_percent"=>0, "outbound_in_percent"=>0}, "facebook"=>{"icon"=>"facebook", "inbound"=>0, "outbound"=>0, "inbound_in_percent"=>0, "outbound_in_percent"=>0}}}, "StatsTicketInProcess"=>{"used_for_average"=>0, "average_per_agent"=>22.2, "state"=>"supergood", "in_process"=>0, "percent"=>0, "total"=>0}, "StatsTicketLoadMeasure"=>{"used_for_average"=>0, "average_per_agent"=>16.7, "percent"=>0, "state"=>"supergood", "own"=>0, "total"=>0}, "StatsTicketEscalation"=>{"used_for_average"=>0, "average_per_agent"=>0.0, "state"=>"supergood", "own"=>0, "total"=>0}, "StatsTicketReopen"=>{"used_for_average"=>0, "percent"=>0, "average_per_agent"=>13.4, "state"=>"supergood", "count"=>0, "total"=>0}, "StatsTicketWaitingTime"=>{"handling_time"=>0, "average_per_agent"=>0, "state"=>"supergood", "percent"=>0.0}}, "created_by_id"=>1, "created_at"=>Tue, 11 Dec 2018 14:59:11 UTC +00:00, "updated_at"=>Thu, 13 Dec 2018 11:27:09 UTC +00:00, "stats_store_object"=>"User", ..............

Payload size: 0M


[2018-12-13T13:40:32,794][DEBUG][o.e.a.b.TransportBulkAction] [6lNx6DJ] failed to execute pipeline [zammad995361596052] for document [zammad_production/StatsStore/39]
java.lang.IllegalArgumentException: pipeline with id [zammad995361596052] does not exist
        at org.elasticsearch.ingest.PipelineExecutionService.getPipeline(PipelineExecutionService.java:194) ~[elasticsearch-5.6.14.jar:5.6.14]
        at org.elasticsearch.ingest.PipelineExecutionService.access$100(PipelineExecutionService.java:41) ~[elasticsearch-5.6.14.jar:5.6.14]
        at org.elasticsearch.ingest.PipelineExecutionService$2.doRun(PipelineExecutionService.java:88) [elasticsearch-5.6.14.jar:5.6.14]
        at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:675) [elasticsearch-5.6.14.jar:5.6.14]
        at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-5.6.14.jar:5.6.14]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_191]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_191]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]

I did some digging and I think it had to do with the version upgrade to 5.6.x.

I installed the ingest-attachment plugin and restarted it all… seemed to have been the issue.

https://docs.zammad.org/en/latest/install-elasticsearch.html

1 Like

Hi @InsaneSplash,

so everything is working again?
Or is there anything we can do to help

regards

Johannes

All good now thanks! I think that was the issue… it upgraded, but didn’t know I needed to add the missing module… only figured it out after reviewing the install docs…

Thanks!

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