# Confused by deprecation message

**URL:** <https://discuss.elastic.co/t/confused-by-deprecation-message/325780>\
**Category:** Elasticsearch\
**Created:** [February 16, 2023, 10:10pm UTC](https://discuss.elastic.co/t/confused-by-deprecation-message/325780 "2023-02-16T22:10:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Russell\_Fulton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/russell_fulton/32/62888_2.png) [@Russell\_Fulton](https://discuss.elastic.co/u/Russell_Fulton)\
**Post date:** [February 16, 2023, 10:10pm UTC](https://discuss.elastic.co/t/confused-by-deprecation-message/325780/1 "2023-02-16T22:10:43Z")

</div>

I am looking at upgrading my 7.17 cluster to version 8, first stop the depreciation logs!

I notice that there is both a `deprecation.log` and a `deprecation.json` and they have different data.

deprecation.log:

```auto
[2020-11-16T19:25:42,963][WARN][o.e.d.l.XPackLicenseState] [secmonprd08] Automatically enabling security because [xpack.security.transport.ssl.enabled] is true. This behaviour will be removed in a future version of Elasticsearch. Please set [xpack.security.enabled] to true
[2020-11-17T08:28:53,361][WARN][o.e.d.x.c.s.SSLService] [secmonprd08] SSL configuration [xpack.security.http.ssl.] relies upon fallback to another configuration for [key configuration, trust configuration], which is deprecated.
[2020-11-17T08:28:53,385][WARN][o.e.d.x.c.s.SSLService] [secmonprd08] SSL configuration [xpack.http.ssl] relies upon fallback to another configuration for [key configuration, trust configuration], which is deprecated.
[2020-11-17T08:28:53,385][WARN][o.e.d.x.c.s.SSLService] [secmonprd08] SSL configuration [xpack.security.transport.ssl.] relies upon fallback to another configuration for [key configuration, trust configuration], which is deprecated.

```

repeated every 5 minutes or so ?

in configuration file I have:

```auto
xpack.security.enabled: true
xpack.security.http.ssl.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.http.ssl.key: /etc/elasticsearch/ssl/privkey.pem
xpack.security.http.ssl.certificate: /etc/elasticsearch/ssl/fullchain.pem
xpack.security.transport.ssl.key: /etc/elasticsearch/ssl/privkey.pem
xpack.security.transport.ssl.certificate: /etc/elasticsearch/ssl/fullchain.pem
xpack.security.transport.ssl.verification_mode: certificate

```

`xpack.security.enabled` is explicitly set ???

Very confused!

Also these messages _do not_ appear in the `deprecation.json` file ??

other messages relating to zen.discovery appear in both logs.

I just remembered the upgrade assistant! It lists only the errors relating to the discovery and recovery options as critical. I have fixed these on my test cluster without issues.. It makes no mention of the xpack security issues. I assume this means that, assuming the issues are real they are not going to break anything when I move to 8.

It also lists one critical kibana issue `Setting "logging.dest" is deprecated` -- this option is no in the kibana.yml file?

Lastly there are a bunch of depreciation issues related to "system" indexes -- as far as I can see these are all kibana related indexes -- again confusing

---

<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:** [March 16, 2023, 10:10pm UTC](https://discuss.elastic.co/t/confused-by-deprecation-message/325780/2 "2023-03-16T22:10:56Z")

</div>

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