"msg":"Failed to create span writer","error":"elastic: Error 502 (Bad Gateway)"

[Zhang Zhao]

Hello,

Anyone has seen this error below? Elasticsearch is my backend. The Jaeger collector was failed to start due to this error..  I had to set "--es.create-index-templates=false" specifically to be able to bring collector up.. This default setting doesn't work with Elasticsearch 7.x or sth.?

{"level":"fatal","ts":1665428066.4950516,"caller":"command-line-arguments/main.go:79","msg":"Failed to create span writer","error":"elastic: Error 502 (Bad Gateway)"}

Zhang

[Yuri Shkuro]

"Error 502 (Bad Gateway)" means Jaeger cannot connect to ES.

[Zhang Zhao]

Hmmm… But I did curl the Elasticsearch endpoint and it worked just fine. Also I did see the version info about Elasticsearch above this error message, so I thought the connection was working.. Also like I mentioned in my post, the collector was able to start after I set "--es.create-index-templates=false”.. So I don’t think connection was the issue..

-- 
You received this message because you are subscribed to a topic in the Google Groups "Jaeger Tracing" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jaeger-tracing/V5rTs-ia8jk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jaeger-tracin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jaeger-tracing/77afbc6c-96b3-421a-b0f1-c7a23ab40df2n%40googlegroups.com.

[Yuri Shkuro]

then maybe it a permissions issue where whichever user Jaeger runs as is unable to create the index templates.

[Zhang Zhao]

oh..  I did not set any user at all on Elasticsearch side. What user does Jaeger runs as by default?