# Marvel.agent.exporter getting 500 back from logging cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [December 9, 2014, 3:11am UTC](https://discuss.elastic.co/t/marvel-agent-exporter-getting-500-back-from-logging-cluster/21160 "2014-12-09T03:11:00Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Lane\_Harris](https://avatars.discourse-cdn.com/v4/letter/l/ea5d25/32.png) [@Lane\_Harris](https://discuss.elastic.co/u/Lane_Harris)\ **Post date:** [December 9, 2014, 3:11am UTC](https://discuss.elastic.co/t/marvel-agent-exporter-getting-500-back-from-logging-cluster/21160/1 "2014-12-09T03:11:00Z")
Hello all We are running Marvel 1.2.1 on ES 1.3.4/Java 1.7.55 with a separate "logging cluster" that marvel.agent.exporter.es.hosts points to. The logging cluster is running the same bits as our production cluster with marvel.agent.enabled set to false. About a week ago, we stopped seeing events for the "Cluster Pulse" and "Shard Allocation" dashboards. Whenever one of the events tracked on these dashboards occurs, the current master spits out the following log message: [2014-12-09 02:54:59,220][ERROR][marvel.agent.exporter] [T02-C01-M03] remote target didn't respond with 200 OK response code [500 Internal Server Error]. content: [🙂 ?error?JsonParseException[Invalid shared name reference 293; only got 0 names in buffer (invalid content) at [Source: org.elasticsearch.transport.netty.ChannelBufferStreamInput@3fc84b46; line: -1, column: 4]]?status$ ??] On the logging cluster, the relevant types for these pages (node\_event, shard\_event, etc) dried up at the same time the errors started appearing in the logs. I checked the both the Marvel template and the actual mappings - no differences between the two days. Has anyone seen a similar issue? Lane -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/22b183f3-6df3-4936-a5c9-9e4483d3c348%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/22b183f3-6df3-4936-a5c9-9e4483d3c348%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [December 20, 2014, 8:55am UTC](https://discuss.elastic.co/t/marvel-agent-exporter-getting-500-back-from-logging-cluster/21160/2 "2014-12-20T08:55:07Z")
You are probably running into [https://github.com/FasterXML/jackson-dataformat-smile/issues/18](https://github.com/FasterXML/jackson-dataformat-smile/issues/18), which was fixed by upgrading jackson in ES with [Upgrade to Jackson Smile 2.4.1.1 by kimchy · Pull Request #7327 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/pull/7327) (version 1.4.0) Cheers, Boaz On Tuesday, December 9, 2014 4:11:00 AM UTC+1, Lane Harris wrote: > Hello all > > We are running Marvel 1.2.1 on ES 1.3.4/Java 1.7.55 with a separate > "logging cluster" that marvel.agent.exporter.es.hosts points to. The > logging cluster is running the same bits as our production cluster > with marvel.agent.enabled set to false. About a week ago, we stopped > seeing events for the "Cluster Pulse" and "Shard Allocation" dashboards. > Whenever one of the events tracked on these dashboards occurs, the current > master spits out the following log message: > > [2014-12-09 02:54:59,220][ERROR][marvel.agent.exporter] [T02-C01-M03] > remote target didn't respond with 200 OK response code [500 Internal Server > Error]. content: [🙂 > ?error?JsonParseException[Invalid shared name reference 293; only got 0 > names in buffer (invalid content) > at [Source: > org.elasticsearch.transport.netty.ChannelBufferStreamInput@3fc84b46; line: > -1, column: 4]]?status$ ??] > > On the logging cluster, the relevant types for these pages (node\_event, > shard\_event, etc) dried up at the same time the errors started appearing in > the logs. I checked the both the Marvel template and the actual mappings - > no differences between the two days. Has anyone seen a similar issue? > > Lane -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/78ae2a44-7900-46c4-ad47-51698455dd76%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/78ae2a44-7900-46c4-ad47-51698455dd76%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dfr0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dfr0/32/6433_2.png) [@dfr0](https://discuss.elastic.co/u/dfr0)\ **Post date:** [November 27, 2015, 2:20am UTC](https://discuss.elastic.co/t/marvel-agent-exporter-getting-500-back-from-logging-cluster/21160/3 "2015-11-27T02:20:12Z")
I've the same problem with the 2.0 version. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:35pm UTC](https://discuss.elastic.co/t/marvel-agent-exporter-getting-500-back-from-logging-cluster/21160/4 "2017-07-05T23:35:30Z")