# Diagnosing "ElasticSearchParseException\[Failed to derive xcontent from \]" error

**URL:** <https://discuss.elastic.co/t/diagnosing-elasticsearchparseexception-failed-to-derive-xcontent-from-error/4144>\
**Category:** Elasticsearch\
**Created:** [March 22, 2011, 11:55am UTC](https://discuss.elastic.co/t/diagnosing-elasticsearchparseexception-failed-to-derive-xcontent-from-error/4144 "2011-03-22T11:55:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![skaffman\_2](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@skaffman\_2](https://discuss.elastic.co/u/skaffman_2)\
**Post date:** [March 22, 2011, 11:55am UTC](https://discuss.elastic.co/t/diagnosing-elasticsearchparseexception-failed-to-derive-xcontent-from-error/4144/1 "2011-03-22T11:55:04Z")

</div>

Whilst updating a mapping document using the REST API, I suddenly  
started getting a 500 error from the server when PUTting the document:

{"error":"ElasticSearchParseException[Failed to derive xcontent  
from ]","status":500}

The server's logs contain nothing.

The mapping document itself is fine (I can push it to another  
ElasticSearch instance with no problems), so I'm thinking the internal  
state of the server is corrupted somehow.

How do I go about diagnosing this? Shouldn't I be seeing something in  
the log if I'm getting something as irrecoverable as a 500 error?

---

<div class="post-metadata">

**Author:** ![skaffman\_2](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@skaffman\_2](https://discuss.elastic.co/u/skaffman_2)\
**Post date:** [March 22, 2011, 11:55am UTC](https://discuss.elastic.co/t/diagnosing-elasticsearchparseexception-failed-to-derive-xcontent-from-error/4144/2 "2011-03-22T11:55:57Z")

</div>

I'm using ES 0.15.2, incidentally.

On Mar 22, 11:55 am, skaffman [ke...@chasmcity.com](mailto:ke...@chasmcity.com) wrote:

> Whilst updating a mapping document using the REST API, I suddenly  
> started getting a 500 error from the server when PUTting the document:
> 
> {"error":"ElasticSearchParseException[Failed to derive xcontent  
> from ]","status":500}
> 
> The server's logs contain nothing.
> 
> The mapping document itself is fine (I can push it to another  
> Elasticsearch instance with no problems), so I'm thinking the internal  
> state of the server is corrupted somehow.
> 
> How do I go about diagnosing this? Shouldn't I be seeing something in  
> the log if I'm getting something as irrecoverable as a 500 error?

---

<div class="post-metadata">

**Author:** ![skaffman\_2](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@skaffman\_2](https://discuss.elastic.co/u/skaffman_2)\
**Post date:** [March 22, 2011, 12:17pm UTC](https://discuss.elastic.co/t/diagnosing-elasticsearchparseexception-failed-to-derive-xcontent-from-error/4144/3 "2011-03-22T12:17:23Z")

</div>

Please ignore the above. I'm an idiot.

On Mar 22, 11:55 am, skaffman [ke...@chasmcity.com](mailto:ke...@chasmcity.com) wrote:

> I'm using ES 0.15.2, incidentally.
> 
> On Mar 22, 11:55 am, skaffman [ke...@chasmcity.com](mailto:ke...@chasmcity.com) wrote:
> 
> > Whilst updating a mapping document using the REST API, I suddenly  
> > started getting a 500 error from the server when PUTting the document:
> 
> > {"error":"ElasticSearchParseException[Failed to derive xcontent  
> > from ]","status":500}
> 
> > The server's logs contain nothing.
> 
> > The mapping document itself is fine (I can push it to another  
> > Elasticsearch instance with no problems), so I'm thinking the internal  
> > state of the server is corrupted somehow.
> 
> > How do I go about diagnosing this? Shouldn't I be seeing something in  
> > the log if I'm getting something as irrecoverable as a 500 error?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:09am UTC](https://discuss.elastic.co/t/diagnosing-elasticsearchparseexception-failed-to-derive-xcontent-from-error/4144/4 "2017-07-06T04:09:28Z")

</div>


