- 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.
Upgraded nodes fail to start due to datafeed issues
editUpgraded nodes fail to start due to datafeed issues
editThis problem occurs when you have a datafeed that contains search or query domain specific language (DSL) that was discontinued. For example, if you created a datafeed query in 5.x using search syntax that was deprecated in 5.x and removed in 6.0, you must fix the datafeed before you upgrade to 6.0.
Symptoms:
- If deprecation logging is enabled before the upgrade, deprecation messages are generated when the datafeeds attempt to retrieve data.
- After the upgrade, nodes fail to start and the error indicates that they failed to read the local state.
Resolution:
Before you upgrade, identify the problematic search or query DSL. In 5.6.5 and later, the Upgrade Assistant detects these scenarios. If you cannot fix the DSL before the upgrade, you must delete the datafeed then re-create it with valid DSL after the upgrade.
If you do not fix or delete the datafeed before the upgrade, in order to successfully start the failing nodes you must downgrade the nodes then fix the problem per above.
See also Upgrading the Elastic Stack.