- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Setting Up X-Pack
- Breaking Changes
- X-Pack APIs
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Reporting from Kibana
- Securing the Elastic Stack
- Getting Started with Security
- How Security Works
- Setting Up User Authentication
- Configuring SAML Single-Sign-On on the Elastic Stack
- Configuring Role-based Access Control
- Auditing Security Events
- Encrypting Communications
- Restricting Connections with IP Filtering
- Cross Cluster Search, Tribe, Clients and Integrations
- Reference
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Machine Learning in the Elastic Stack
- Troubleshooting
- Getting Help
- X-Pack security
- Can’t log in after upgrading to 6.2.4
- Some settings are not returned via the nodes settings API
- Authorization exceptions
- Users command fails due to extra arguments
- Users are frequently locked out of Active Directory
- Certificate verification fails for curl on Mac
- SSLHandshakeException causes connections to fail
- Common SSL/TLS exceptions
- Internal Server Error in Kibana
- Setup-passwords command fails due to connection failure
- X-Pack Watcher
- X-Pack monitoring
- X-Pack machine learning
- Limitations
- License Management
- Release Notes
WARNING: Version 6.2 of the Elastic Stack has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Upgrading X-Pack
editUpgrading X-Pack
editYou must upgrade all of the Elastic Stack products you are using when upgrading to a new major version.
If you use X-Pack security and are upgrading directly to
6.2.4 from 5.5 or earlier, you must upgrade the .security
index
after you restart Elasticsearch. Native realm users will not be able to
authenticate until the index is upgraded. For instructions, see
Upgrading
internal indices. You also need to upgrade the .security
index if
you restore a pre-5.6 snapshot to a fresh 6.0 install.
To upgrade X-Pack:
- Stop any machine learning jobs that are running before starting the upgrade process. See Stopping Machine Learning.
- Stop Elasticsearch.
-
Uninstall X-Pack from Elasticsearch:
bin/elasticsearch-plugin remove x-pack
-
If you have not already done so, upgrade Elasticsearch.
If you use X-Pack monitoring, re-use the data directory when you upgrade Elasticsearch. Monitoring identifies unique Elasticsearch nodes by using the persistent UUID, which is stored in the data directory. For more information about the location of the data directory, see path.data and path.logs.
- Install the new version of X-Pack into Elasticsearch.
-
Restart Elasticsearch.
If you’re upgrading a production cluster, perform a rolling upgrade to ensure recovery is as quick as possible. Rolling upgrades are supported when upgrading to a new minor version. A full cluster restart is required when upgrading to a new major version.
-
Uninstall X-Pack from Kibana:
bin/kibana-plugin remove x-pack
-
If you have not already done so, upgrade Kibana.
If you use X-Pack monitoring, you must re-use the data directory when you upgrade Kibana. Otherwise, the Kibana instance is assigned a new persistent UUID and becomes a new instance in the monitoring data.
- Install the new version of X-Pack into Kibana.
- Restart Kibana.
-
Uninstall X-Pack from Logstash:
bin/logstash-plugin remove x-pack
-
If you have not already done so, upgrade Logstash.
If you use X-Pack monitoring, you must re-use the data directory when you upgrade Logstash. Otherwise, the Logstash node is assigned a new persistent UUID and becomes a new node in the monitoring data.
- Install the new version of X-Pack into Logstash.
- Restart Logstash.
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now