- 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 Elasticsearch and Kibana
- 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.1.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.1 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.
Machine learning features unavailable after rolling upgrade
editMachine learning features unavailable after rolling upgrade
editThis problem occurs after you upgrade all of the nodes in your cluster to
6.1.4 by using rolling upgrades. When you try to use X-Pack machine learning features for
the first time, all attempts fail, though GET _xpack
and GET _xpack/usage
indicate that X-Pack is enabled.
Symptoms:
-
Errors when you click Machine Learning in Kibana.
For example:
Jobs list could not be created
andAn internal server error occurred
. -
Null pointer and remote transport exceptions when you run machine learning APIs such as
GET _xpack/ml/anomaly_detectors
andGET _xpack/ml/datafeeds
. -
Errors in the log files on the master nodes.
For example:
unable to install ml metadata upon startup
Resolution:
After you upgrade all master-eligible nodes to Elasticsearch 6.1.4 and X-Pack 6.1.4, restart the current master node, which triggers the X-Pack machine learning features to re-initialize.
For more information, see Rolling upgrades.