# Get a "illegal\_argument\_exception" error after upgrade

**URL:** https://discuss.elastic.co/t/get-a-illegal-argument-exception-error-after-upgrade/189069
**Category:** Elasticsearch
**Created:** [July 5, 2019, 10:33am UTC](https://discuss.elastic.co/t/get-a-illegal-argument-exception-error-after-upgrade/189069 "2019-07-05T10:33:20Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![yeziblo](https://avatars.discourse-cdn.com/v4/letter/y/74df32/32.png) [@yeziblo](https://discuss.elastic.co/u/yeziblo)
#### Post date: [July 5, 2019, 10:33am UTC](https://discuss.elastic.co/t/get-a-illegal-argument-exception-error-after-upgrade/189069/1 "2019-07-05T10:33:21Z")

</div>

Hi, everyone.

I'm trying to upgrade ES from 5.4.0 to 6.8.0.

According to official documents, I execute this method after upgrade:

curl -XPUT -H "Content-Type:application/json" 172.16.1.133:9200/\_cluster/settings -d'  
{  
"persistent": {  
"cluster.routing.allocation.enable": null  
}  
}  
'

And I got error:

{"error":{"root\_cause":[{"type":"illegal\_argument\_exception","reason":"unknown setting [archived.xpack.security.transport.filter.deny] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"}],"type":"illegal\_argument\_exception","reason":"unknown setting [archived.xpack.security.transport.filter.deny] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"},"status":400}

How can I solve this problem?

Thanks and regards!

---

<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: [July 5, 2019, 1:58pm UTC](https://discuss.elastic.co/t/get-a-illegal-argument-exception-error-after-upgrade/189069/2 "2019-07-05T13:58:21Z")

</div>

Somewhere along the way, Elasticsearch has failed to recognise your `xpack.security.transport.filter.deny` setting and has archived it. You must remove any archived settings before you can set any other settings. I think this is a valid setting, as long as you are not using an unusual distribution. Can you share the output of `curl http://172.16.1.133:9200/`?

To remove an archived setting, set it to `null`:

```auto
curl -XPUT -H "Content-Type:application/json" http://172.16.1.133:9200/_cluster/settings -d'
{
  "persistent": {
    "archived.xpack.security.transport.filter.deny": null
  }
}'

```

---

<div class="post-metadata">

### Author: ![yeziblo](https://avatars.discourse-cdn.com/v4/letter/y/74df32/32.png) [@yeziblo](https://discuss.elastic.co/u/yeziblo)
#### Post date: [July 8, 2019, 2:10am UTC](https://discuss.elastic.co/t/get-a-illegal-argument-exception-error-after-upgrade/189069/3 "2019-07-08T02:10:07Z")

</div>

it works！  
Tnanks and best regards！

---

<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: [August 5, 2019, 2:10am UTC](https://discuss.elastic.co/t/get-a-illegal-argument-exception-error-after-upgrade/189069/4 "2019-08-05T02:10:10Z")

</div>

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