# Json parse exception with status 500 post upgrade to 7.4.0

**URL:** <https://discuss.elastic.co/t/json-parse-exception-with-status-500-post-upgrade-to-7-4-0/201936>\
**Category:** Elasticsearch\
**Created:** [October 2, 2019, 10:11am UTC](https://discuss.elastic.co/t/json-parse-exception-with-status-500-post-upgrade-to-7-4-0/201936 "2019-10-02T10:11:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![starrynight](https://avatars.discourse-cdn.com/v4/letter/s/a5b964/32.png) [@starrynight](https://discuss.elastic.co/u/starrynight)\
**Post date:** [October 2, 2019, 10:11am UTC](https://discuss.elastic.co/t/json-parse-exception-with-status-500-post-upgrade-to-7-4-0/201936/1 "2019-10-02T10:11:06Z")

</div>

I've upgraded from 7.3.2 to 7.4.0 and in attempting to follow the rolling upgrades document -- I've issued a:

```
[root@host elasticsearch]# curl -X PUT -u elastic "ipaddy:9200/_cluster/settings?pretty" -H 'Content-Type: application/json' -d'
> {
> "persistent": {
> "cluster.routing.allocation.enable": null
> }
> }
> '

```

I've then received the following output upon issuing the password:

```
{
  "error" : {
    "root_cause" : [
      {
        "type" : "json_parse_exception",
        "reason" : "Invalid UTF-8 start byte 0x80\n at [Source: org.elasticsearch.transport.netty4.ByteBufStreamInput@3a3d0a5c; line: 4, column: 44]"
      }
    ],
    "type" : "json_parse_exception",
    "reason" : "Invalid UTF-8 start byte 0x80\n at [Source: org.elasticsearch.transport.netty4.ByteBufStreamInput@3a3d0a5c; line: 4, column: 44]"
  },
  "status" : 500
}

```

Help?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [October 2, 2019, 11:56am UTC](https://discuss.elastic.co/t/json-parse-exception-with-status-500-post-upgrade-to-7-4-0/201936/2 "2019-10-02T11:56:49Z")

</div>

I think you might have picked up a stray unexpected character when copy-pasting the `curl` command somehow. I tried the command you shared and it worked for me:

```auto
$ curl -X PUT "localhost:9200/_cluster/settings?pretty" -H 'Content-Type: application/json' -d'
{
  "persistent": {
    "cluster.routing.allocation.enable": null
  }
}
'
{
  "acknowledged" : true,
  "persistent" : { },
  "transient" : { }
}

```

Try copying it again, or try typing it out if you cannot get copy/paste to work.

---

<div class="post-metadata">

**Author:** ![starrynight](https://avatars.discourse-cdn.com/v4/letter/s/a5b964/32.png) [@starrynight](https://discuss.elastic.co/u/starrynight)\
**Post date:** [October 2, 2019, 12:05pm UTC](https://discuss.elastic.co/t/json-parse-exception-with-status-500-post-upgrade-to-7-4-0/201936/3 "2019-10-02T12:05:59Z")

</div>

Thanks! That turned out to be the issue -- and I ended up having to hand type it. (...which is odd because I pasted the other day when I ended up doing the update to 7.3.2...)

---

<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:** [October 30, 2019, 12:06pm UTC](https://discuss.elastic.co/t/json-parse-exception-with-status-500-post-upgrade-to-7-4-0/201936/4 "2019-10-30T12:06:09Z")

</div>

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