# Version 5.4.1 Separate Monitoring Cluster Error: "Monitoring: Error 400 Bad Request: Cannot create property 'type' on string 'green'" **URL:** \ **Category:** Elasticsearch\ **Created:** [June 16, 2017, 9:12pm UTC](https://discuss.elastic.co/t/version-5-4-1-separate-monitoring-cluster-error-monitoring-error-400-bad-request-cannot-create-property-type-on-string-green/89774 "2017-06-16T21:12:40Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![luke\_smoron](https://avatars.discourse-cdn.com/v4/letter/l/f14d63/32.png) [@luke\_smoron](https://discuss.elastic.co/u/luke_smoron)\ **Post date:** [June 16, 2017, 9:12pm UTC](https://discuss.elastic.co/t/version-5-4-1-separate-monitoring-cluster-error-monitoring-error-400-bad-request-cannot-create-property-type-on-string-green/89774/1 "2017-06-16T21:12:40Z")
Hi, I got separate monitoring cluster. When updating that cluster to version 5.4.1 I got following error Monitoring: Error 400 Bad Request: Cannot read property 'type' of null This version does work if I use local cluster for monitoring. Main landing page of the monitoring app: ![](https://us1.discourse-cdn.com/elastic/original/3X/2/d/2d5f3b7223a108ad3b518b853ff221c691d403c2.png) When I try to click on Nodes section ![](https://us1.discourse-cdn.com/elastic/original/3X/7/8/781764b401ad4d794c19889101518d34fe38fa15.png) This is the log ![](https://us1.discourse-cdn.com/elastic/original/3X/c/4/c452671f3288c59ba9ddee9bc76f6dc5834dab2f.png) My setup used to work fine on older versions of kibana and elk ---
**Author:** ![bohyun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bohyun/32/10087_2.png) [@bohyun](https://discuss.elastic.co/u/bohyun)\ **Post date:** [June 18, 2017, 8:22pm UTC](https://discuss.elastic.co/t/version-5-4-1-separate-monitoring-cluster-error-monitoring-error-400-bad-request-cannot-create-property-type-on-string-green/89774/2 "2017-06-18T20:22:29Z")
Hi @luke_smoron A couple of questions: > My setup used to work fine on older versions of kibana and elk What version were you using before? Can you share your setup details? Thanks, Bohyun ---
**Author:** ![luke\_smoron](https://avatars.discourse-cdn.com/v4/letter/l/f14d63/32.png) [@luke\_smoron](https://discuss.elastic.co/u/luke_smoron)\ **Post date:** [June 19, 2017, 3:17pm UTC](https://discuss.elastic.co/t/version-5-4-1-separate-monitoring-cluster-error-monitoring-error-400-bad-request-cannot-create-property-type-on-string-green/89774/3 "2017-06-19T15:17:57Z")
Version 2.3.5 we also did initial setup for 5.4.0 (did not fully tested that one since we decided to switch to 5.4.1) We run our clusters in aws. The main cluster talks to the monitoring elastic using following configuration: network.bind\_host: _ec2_ discovery.zen.hosts\_provider: ec2 xpack.security.enabled: false cluster.name= \< name \> discovery.ec2.tag.stage= \< name\> xpack.monitoring.exporters.id1.type=http xpack.monitoring.exporters.id1.host=http://\< IP\>:9200 the monitoring cluster is basically a single node elastic instance with mostly out of box configuration xpack.security.enabled: false xpack.monitoring.enabled: false We had to disable monitoring on it since basic x-pack license only allows monitoring single cluster. I wonder if this might be the issue. If we enable monitoring on monitoring cluster x-pack is able to show monitoring info for the monitoring cluster but it refuses to show monitoring for main cluster due to license. ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [June 20, 2017, 4:27am UTC](https://discuss.elastic.co/t/version-5-4-1-separate-monitoring-cluster-error-monitoring-error-400-bad-request-cannot-create-property-type-on-string-green/89774/4 "2017-06-20T04:27:51Z")
This is going to sound crazy, but do you happen to have an index named `nodes` that would have stats in the monitoring data? There is a known bug that will be fixed very very soon. Your issue looks like the symptom of that bug. ---
**Author:** ![luke\_smoron](https://avatars.discourse-cdn.com/v4/letter/l/f14d63/32.png) [@luke\_smoron](https://discuss.elastic.co/u/luke_smoron)\ **Post date:** [June 20, 2017, 2:17pm UTC](https://discuss.elastic.co/t/version-5-4-1-separate-monitoring-cluster-error-monitoring-error-400-bad-request-cannot-create-property-type-on-string-green/89774/5 "2017-06-20T14:17:42Z")
Yes there was such index on the main cluster > curl \< ip\>:9200/\_cat/indices > green open development\_2 bG8hK0a0Sg6iTOpwMGDVww 10 1 0 0 3.1kb 1.5kb > green open development\_1 BU-PTAvlQwWrmmqbn6F9rQ 10 1 3330110 451514 69.7gb 34.8gb > green open system\_test\_feb\_21 pXtebrcYSiWyIB83YAUlAQ 10 1 3099439 1181424 53.7gb 26.8gb > green open it\_test akd8oXl1Q4yyHlC-0xHw8Q 1 0 15 0 40.5kb 40.5kb > green open nodes qBAOcd-GSV-RyoMAdZsw\_Q 5 1 1 0 7.7kb 3.8kb > green open development 1WBrmAUESwqTC8xFDJ2k7g 10 1 451 19 28.1mb 14mb > green open integration\_v2 G3rWLkGwTZafEoLPdPTn4A 10 2 75366 11477 4.4gb 1.4gb > curl \< ip\>:9200/nodes > {"nodes":{"aliases":{},"mappings":{"stats":{"properties":{"query":{"properties":{"filtered":{"properties":{"query":{"properties":{"term":{"properties":{"\_id":{"type":"string"}}}}}}}}}}}},"settings":{"index":{"creation\_date":"1495134153824","number\_of\_shards":"5","number\_of\_replicas":"1","uuid":"qBAOcd-GSV-RyoMAdZsw\_Q","version":{"created":"2030599","upgraded":"5040199"}}}} After removing it and cleaning monitoring cluster everything started to work fine. Thanks 😀 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 18, 2017, 2:17pm UTC](https://discuss.elastic.co/t/version-5-4-1-separate-monitoring-cluster-error-monitoring-error-400-bad-request-cannot-create-property-type-on-string-green/89774/6 "2017-07-18T14:17:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.