diff --git a/manage-data/lifecycle/index-lifecycle-management/index-lifecycle.md b/manage-data/lifecycle/index-lifecycle-management/index-lifecycle.md index 3342324c55..b9d21d94ce 100644 --- a/manage-data/lifecycle/index-lifecycle-management/index-lifecycle.md +++ b/manage-data/lifecycle/index-lifecycle-management/index-lifecycle.md @@ -31,7 +31,7 @@ If you use {{es}}'s security features, {{ilm-init}} performs operations as the u The minimum age defaults to zero, which causes {{ilm-init}} to move indices to the next phase as soon as all actions in the current phase complete. ::::{note} -If an index has been [rolled over](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-rollover.html), then the `min_age` value is relative to the time the index was rolled over, not the index creation time. [Learn more](../../../troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md#min-age-calculation). +If an index has been [rolled over](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-rollover.html), then the `min_age` value is relative to the time the index was rolled over, not the index creation time. [Learn more](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md#min-age-calculation). :::: diff --git a/manage-data/lifecycle/index-lifecycle-management/rollover.md b/manage-data/lifecycle/index-lifecycle-management/rollover.md index 0b18e20ffd..6f1d433c50 100644 --- a/manage-data/lifecycle/index-lifecycle-management/rollover.md +++ b/manage-data/lifecycle/index-lifecycle-management/rollover.md @@ -27,7 +27,7 @@ Data streams are designed for append-only data, where the data stream name can b * A single index designated as the *write index*. This is the active index that handles all write requests. On each rollover, the new index becomes the write index. ::::{note} -When an index is rolled over, the previous index’s age is updated to reflect the rollover time. This date, rather than the index’s `creation_date`, is used in {{ilm}} `min_age` phase calculations. [Learn more](../../../troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md#min-age-calculation). +When an index is rolled over, the previous index’s age is updated to reflect the rollover time. This date, rather than the index’s `creation_date`, is used in {{ilm}} `min_age` phase calculations. [Learn more](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md#min-age-calculation). :::: diff --git a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md index 3b2a238f40..4507753baa 100644 --- a/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md +++ b/manage-data/lifecycle/index-lifecycle-management/skip-rollover.md @@ -12,7 +12,7 @@ You can set it manually to skip rollover if you need to make an exception to you If an index’s lifecycle policy is removed, this setting is also removed. ::::{important} -When `index.lifecycle.indexing_complete` is `true`, {{ilm-init}} verifies that the index is no longer the write index for the alias specified by `index.lifecycle.rollover_alias`. If the index is still the write index or the rollover alias is not set, the index is moved to the [`ERROR` step](../../../troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md). +When `index.lifecycle.indexing_complete` is `true`, {{ilm-init}} verifies that the index is no longer the write index for the alias specified by `index.lifecycle.rollover_alias`. If the index is still the write index or the rollover alias is not set, the index is moved to the [`ERROR` step](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md). :::: diff --git a/manage-data/lifecycle/index-lifecycle-management/tutorial-automate-rollover.md b/manage-data/lifecycle/index-lifecycle-management/tutorial-automate-rollover.md index cc72a65818..4639787fd0 100644 --- a/manage-data/lifecycle/index-lifecycle-management/tutorial-automate-rollover.md +++ b/manage-data/lifecycle/index-lifecycle-management/tutorial-automate-rollover.md @@ -35,7 +35,7 @@ For example, you might define a `timeseries_policy` that has two phases: * A `delete` phase that sets `min_age` to remove the index 90 days after rollover. ::::{note} -The `min_age` value is relative to the rollover time, not the index creation time. [Learn more](../../../troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md#min-age-calculation). +The `min_age` value is relative to the rollover time, not the index creation time. [Learn more](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md#min-age-calculation). :::: diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md index fcc4587388..c50c30e02f 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md @@ -51,7 +51,7 @@ You can also search and filter the table based on affected resources, such as in :alt: {{es}} Health page with details and troubleshooting ::: -For each issue you can either use a troubleshooting link or get a suggestion to contact support, in case you need help. The [troubleshooting documentation](../../../troubleshoot/elasticsearch/elasticsearch-reference.md) for {{es}} provides more details on specific errors. +For each issue you can either use a troubleshooting link or get a suggestion to contact support, in case you need help. The [troubleshooting documentation](../../../troubleshoot/elasticsearch/elasticsearch.md) for {{es}} provides more details on specific errors. ## {{es}} cluster performance [ech-es-cluster-performance] diff --git a/raw-migrated-files/cloud/cloud/ec-monitoring.md b/raw-migrated-files/cloud/cloud/ec-monitoring.md index 12a9e06d3e..0d0ac69f2e 100644 --- a/raw-migrated-files/cloud/cloud/ec-monitoring.md +++ b/raw-migrated-files/cloud/cloud/ec-monitoring.md @@ -57,7 +57,7 @@ You can also search and filter the table based on affected resources, such as in :alt: {{es}} Health page with details and troubleshooting ::: -For each issue you can either use a troubleshooting link or get a suggestion to contact support, in case you need help. The [troubleshooting documentation](../../../troubleshoot/elasticsearch/elasticsearch-reference.md) for {{es}} provides more details on specific errors. +For each issue you can either use a troubleshooting link or get a suggestion to contact support, in case you need help. The [troubleshooting documentation](../../../troubleshoot/elasticsearch/elasticsearch.md) for {{es}} provides more details on specific errors. ## {{es}} cluster performance [ec-es-cluster-performance] diff --git a/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md b/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md index 270d9fdd0f..7cc8f381be 100644 --- a/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md +++ b/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md @@ -12,8 +12,8 @@ Throughout the Elastic docs we have a number of troubleshooting and frequently a **{{es}}** -* [{{es}} troubleshooting](../../../troubleshoot/elasticsearch/elasticsearch-reference.md) -* [Troubleshooting index lifecycle management errors](../../../troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md) +* [{{es}} troubleshooting](../../../troubleshoot/elasticsearch/elasticsearch.md) +* [Troubleshooting index lifecycle management errors](../../../troubleshoot/elasticsearch/index-lifecycle-management-errors.md) **{{ecloud}}** diff --git a/troubleshoot/elasticsearch/clusters.md b/troubleshoot/elasticsearch/clusters.md index e3c4a9ab2b..501e3410b3 100644 --- a/troubleshoot/elasticsearch/clusters.md +++ b/troubleshoot/elasticsearch/clusters.md @@ -15,7 +15,7 @@ Use the topics in this section to troubleshoot {{es}} clusters: * [](/troubleshoot/elasticsearch/clusters.md) * [](/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md) * [](/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md) -* [](/troubleshoot/elasticsearch/elasticsearch-reference/remote-clusters.md) +* [](/troubleshoot/elasticsearch/remote-clusters.md) * [](/troubleshoot/elasticsearch/diagnose-unassigned-shards.md) * [](/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md) * []() diff --git a/troubleshoot/elasticsearch/elasticsearch-reference/security.md b/troubleshoot/elasticsearch/elasticsearch-reference/security.md deleted file mode 100644 index f4db2c4409..0000000000 --- a/troubleshoot/elasticsearch/elasticsearch-reference/security.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -navigation_title: Security -mapped_pages: - - https://www.elastic.co/guide/en/elasticsearch/reference/current/security-troubleshooting.html ---- - -% marciw: this page needs to move to the security folder - -# Troubleshoot {{es}} security [security-troubleshooting] - -Use the information in this section to troubleshoot common problems and find answers for frequently asked questions. - -* [Some settings are not returned via the nodes settings API](../security/security-trb-settings.md) -* [Authorization exceptions](../security/security-trb-roles.md) -* [Users command fails due to extra arguments](../security/security-trb-extraargs.md) -* [Users are frequently locked out of Active Directory](../security/trouble-shoot-active-directory.md) -* [Certificate verification fails for curl on Mac](../security/trb-security-maccurl.md) -* [SSLHandshakeException causes connections to fail](../security/trb-security-sslhandshake.md) -* [Common SSL/TLS exceptions](../security/trb-security-ssl.md) -* [Common Kerberos exceptions](../security/trb-security-kerberos.md) -* [Common SAML issues](../security/trb-security-saml.md) -* [Internal Server Error in Kibana](../security/trb-security-internalserver.md) -* [Setup-passwords command fails due to connection failure](../security/trb-security-setup.md) -* [Failures due to relocation of the configuration files](../security/trb-security-path.md) - -For issues that you cannot fix yourself … we’re here to help. If you are an existing Elastic customer with a support contract, please create a ticket in the [Elastic Support portal](https://support.elastic.co/customers/s/login/). Or post in the [Elastic forum](https://discuss.elastic.co/). - - - - - - - - - - - - - diff --git a/troubleshoot/elasticsearch/elasticsearch-reference.md b/troubleshoot/elasticsearch/elasticsearch.md similarity index 98% rename from troubleshoot/elasticsearch/elasticsearch-reference.md rename to troubleshoot/elasticsearch/elasticsearch.md index e0d992f644..670399e3f6 100644 --- a/troubleshoot/elasticsearch/elasticsearch-reference.md +++ b/troubleshoot/elasticsearch/elasticsearch.md @@ -37,7 +37,7 @@ If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your ## Management [troubleshooting-management] * [Troubleshoot index and snapshot lifecycle management](start-ilm.md) -* [Fix index lifecycle management errors](/troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md) +* [Fix index lifecycle management errors](/troubleshoot/elasticsearch/index-lifecycle-management-errors.md) ## Capacity [troubleshooting-capacity] diff --git a/troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md b/troubleshoot/elasticsearch/index-lifecycle-management-errors.md similarity index 90% rename from troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md rename to troubleshoot/elasticsearch/index-lifecycle-management-errors.md index cae953341f..cd37589217 100644 --- a/troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md +++ b/troubleshoot/elasticsearch/index-lifecycle-management-errors.md @@ -9,7 +9,7 @@ mapped_pages: # Fix index lifecycle management errors [index-lifecycle-error-handling] -When [{{ilm-init}}](../../../manage-data/lifecycle/index-lifecycle-management.md) executes a lifecycle policy, it’s possible for errors to occur while performing the necessary index operations for a step. When this happens, {{ilm-init}} moves the index to an `ERROR` step. If {{ilm-init}} cannot resolve the error automatically, execution is halted until you resolve the underlying issues with the policy, index, or cluster. +When [{{ilm-init}}](../../manage-data/lifecycle/index-lifecycle-management.md) executes a lifecycle policy, it’s possible for errors to occur while performing the necessary index operations for a step. When this happens, {{ilm-init}} moves the index to an `ERROR` step. If {{ilm-init}} cannot resolve the error automatically, execution is halted until you resolve the underlying issues with the policy, index, or cluster. See [this video](https://www.youtube.com/watch?v=VCIqkji3IwY) for a walkthrough of troubleshooting current {{ilm-init}} health issues, and [this video](https://www.youtube.com/watch?v=onrnnwjYWSQ) for a walkthrough of troubleshooting historical {{ilm-init}} issues. @@ -142,7 +142,7 @@ POST /my-index-000001/_ilm/retry ### How `min_age` is calculated [min-age-calculation] -When setting up an [{{ilm-init}} policy](../../../manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) or [automating rollover with {{ilm-init}}](../../../manage-data/lifecycle/index-lifecycle-management.md), be aware that `min_age` can be relative to either the rollover time or the index creation time. +When setting up an [{{ilm-init}} policy](../../manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) or [automating rollover with {{ilm-init}}](../../manage-data/lifecycle/index-lifecycle-management.md), be aware that `min_age` can be relative to either the rollover time or the index creation time. If you use [{{ilm-init}} rollover](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-rollover.html), `min_age` is calculated relative to the time the index was rolled over. This is because the [rollover API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-rollover) generates a new index and updates the `age` of the previous index to reflect the rollover time. If the index hasn’t been rolled over, then the `age` is the same as the `creation_date` for the index. @@ -154,7 +154,7 @@ You can override how `min_age` is calculated using the `index.lifecycle.originat Here’s how to resolve the most common errors reported in the `ERROR` step. ::::{tip} -Problems with rollover aliases are a common cause of errors. Consider using [data streams](../../../manage-data/data-store/data-streams.md) instead of managing rollover with aliases. +Problems with rollover aliases are a common cause of errors. Consider using [data streams](/manage-data/data-store/data-streams.md) instead of managing rollover with aliases. :::: @@ -208,12 +208,12 @@ See this [resolving `does not match pattern` video](https://www.youtube.com/watc This indicates that the cluster is hitting resource limits. -Before continuing to set up {{ilm-init}}, you’ll need to take steps to alleviate the resource issues. For more information, see [Circuit breaker errors](../circuit-breaker-errors.md). +Before continuing to set up {{ilm-init}}, you’ll need to take steps to alleviate the resource issues. For more information, see [Circuit breaker errors](circuit-breaker-errors.md). ### High disk watermark [x] exceeded on [y] [_high_disk_watermark_x_exceeded_on_y] -This indicates that the cluster is running out of disk space. This can happen when you don’t have {{ilm}} set up to roll over from hot to warm nodes. For more information, see [Fix watermark errors](../fix-watermark-errors.md). +This indicates that the cluster is running out of disk space. This can happen when you don’t have {{ilm}} set up to roll over from hot to warm nodes. For more information, see [Fix watermark errors](fix-watermark-errors.md). ### security_exception: action [] is unauthorized for user [] with roles [], this action is granted by the index privileges [manage_follow_index,manage,all] [_security_exception_action_action_name_is_unauthorized_for_user_user_name_with_roles_role_name_this_action_is_granted_by_the_index_privileges_manage_follow_indexmanageall] diff --git a/troubleshoot/elasticsearch/elasticsearch-reference/remote-clusters.md b/troubleshoot/elasticsearch/remote-clusters.md similarity index 95% rename from troubleshoot/elasticsearch/elasticsearch-reference/remote-clusters.md rename to troubleshoot/elasticsearch/remote-clusters.md index 94d749ede7..82cbc6fddb 100644 --- a/troubleshoot/elasticsearch/elasticsearch-reference/remote-clusters.md +++ b/troubleshoot/elasticsearch/remote-clusters.md @@ -21,7 +21,7 @@ A successful call to the cluster settings update API for adding or updating remo GET /_remote/info ``` -The API should return `"connected" : true`. When using [API key authentication](../../../deploy-manage/remote-clusters/remote-clusters-api-key.md), it should also return `"cluster_credentials": "::es_redacted::"`. +The API should return `"connected" : true`. When using [API key authentication](../../deploy-manage/remote-clusters/remote-clusters-api-key.md), it should also return `"cluster_credentials": "::es_redacted::"`. ```console-result { @@ -41,7 +41,7 @@ The API should return `"connected" : true`. When using [API key authentication]( ``` 1. The remote cluster has connected successfully. -2. If present, indicates the remote cluster has connected using [API key authentication](../../../deploy-manage/remote-clusters/remote-clusters-api-key.md) instead of [certificate based authentication](../../../deploy-manage/remote-clusters/remote-clusters-cert.md). +2. If present, indicates the remote cluster has connected using [API key authentication](../../deploy-manage/remote-clusters/remote-clusters-api-key.md) instead of [certificate based authentication](../../deploy-manage/remote-clusters/remote-clusters-cert.md). @@ -83,7 +83,7 @@ org.elasticsearch.transport.ConnectTransportException: [][192.168.0.42:9443] **c #### Resolution [_resolution] * Check the host and port for the remote cluster are correct. -* Ensure the [remote cluster server is enabled](../../../deploy-manage/remote-clusters/remote-clusters-troubleshooting.md#remote-clusters-troubleshooting-enable-server) on the remote cluster. +* Ensure the [remote cluster server is enabled](../../deploy-manage/remote-clusters/remote-clusters-troubleshooting.md#remote-clusters-troubleshooting-enable-server) on the remote cluster. * Ensure no firewall is blocking the communication. @@ -109,7 +109,7 @@ Note that with some network configurations it could take minutes or hours for th * Ensure that the network between the clusters is as reliable as possible. * Ensure that the network is configured to permit [Long-lived idle connections](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#long-lived-connections). -* Ensure that the network is configured to detect faulty connections quickly. In particular, you must enable and fully support TCP keepalives, and set a short [retransmission timeout](../../../deploy-manage/deploy/self-managed/system-config-tcpretries.md). +* Ensure that the network is configured to detect faulty connections quickly. In particular, you must enable and fully support TCP keepalives, and set a short [retransmission timeout](../../deploy-manage/deploy/self-managed/system-config-tcpretries.md). * On Linux systems, execute `ss -tonie` to verify the details of the configuration of each network connection between the clusters. * If the problems persist, capture network packets at both ends of the connection and analyse the traffic to look for delays and lost messages. @@ -244,7 +244,7 @@ A local cluster uses the presence of a cross-cluster API key to determine the mo GET /_remote/info ``` -The API should return `"connected" : true`. When using [API key authentication](../../../deploy-manage/remote-clusters/remote-clusters-api-key.md), it should also return `"cluster_credentials": "::es_redacted::"`. +The API should return `"connected" : true`. When using [API key authentication](../../deploy-manage/remote-clusters/remote-clusters-api-key.md), it should also return `"cluster_credentials": "::es_redacted::"`. ```console-result { @@ -264,7 +264,7 @@ The API should return `"connected" : true`. When using [API key authentication]( ``` 1. The remote cluster has connected successfully. -2. If present, indicates the remote cluster has connected using [API key authentication](../../../deploy-manage/remote-clusters/remote-clusters-api-key.md) instead of [certificate based authentication](../../../deploy-manage/remote-clusters/remote-clusters-cert.md). +2. If present, indicates the remote cluster has connected using [API key authentication](../../deploy-manage/remote-clusters/remote-clusters-api-key.md) instead of [certificate based authentication](../../deploy-manage/remote-clusters/remote-clusters-cert.md). Besides checking the response of the remote cluster info API, you can also check the logs. diff --git a/troubleshoot/elasticsearch/security.md b/troubleshoot/elasticsearch/security.md new file mode 100644 index 0000000000..341f734f16 --- /dev/null +++ b/troubleshoot/elasticsearch/security.md @@ -0,0 +1,39 @@ +--- +navigation_title: Security +mapped_pages: + - https://www.elastic.co/guide/en/elasticsearch/reference/current/security-troubleshooting.html +--- + +% marciw: this page needs to move to the security folder + +# Troubleshoot {{es}} security [security-troubleshooting] + +Use the information in this section to troubleshoot common problems and find answers for frequently asked questions. + +* [Some settings are not returned via the nodes settings API](security/security-trb-settings.md) +* [Authorization exceptions](security/security-trb-roles.md) +* [Users command fails due to extra arguments](security/security-trb-extraargs.md) +* [Users are frequently locked out of Active Directory](security/trouble-shoot-active-directory.md) +* [Certificate verification fails for curl on Mac](security/trb-security-maccurl.md) +* [SSLHandshakeException causes connections to fail](security/trb-security-sslhandshake.md) +* [Common SSL/TLS exceptions](security/trb-security-ssl.md) +* [Common Kerberos exceptions](security/trb-security-kerberos.md) +* [Common SAML issues](security/trb-security-saml.md) +* [Internal Server Error in Kibana](security/trb-security-internalserver.md) +* [Setup-passwords command fails due to connection failure](security/trb-security-setup.md) +* [Failures due to relocation of the configuration files](security/trb-security-path.md) + +For issues that you cannot fix yourself … we’re here to help. If you are an existing Elastic customer with a support contract, please create a ticket in the [Elastic Support portal](https://support.elastic.co/customers/s/login/). Or post in the [Elastic forum](https://discuss.elastic.co/). + + + + + + + + + + + + + diff --git a/troubleshoot/index.md b/troubleshoot/index.md index ccf5f83ef7..c2b18348d0 100644 --- a/troubleshoot/index.md +++ b/troubleshoot/index.md @@ -19,7 +19,7 @@ The documentation team is actively working on structure, user focus, and more. Use the topics in this section to troubleshoot Elastic products, features, and deployments. -* [](/troubleshoot/elasticsearch/elasticsearch-reference.md) +* [](/troubleshoot/elasticsearch/elasticsearch.md) * [](/troubleshoot/kibana.md) * [](/troubleshoot/observability.md) * [](/troubleshoot/security.md) diff --git a/troubleshoot/toc.yml b/troubleshoot/toc.yml index 741dcb1032..4233ecc435 100644 --- a/troubleshoot/toc.yml +++ b/troubleshoot/toc.yml @@ -1,7 +1,7 @@ project: 'Troubleshoot' toc: - file: index.md - - file: elasticsearch/elasticsearch-reference.md + - file: elasticsearch/elasticsearch.md children: - file: elasticsearch/clusters.md children: @@ -18,7 +18,7 @@ toc: - file: elasticsearch/hotspotting.md - file: elasticsearch/troubleshooting-unstable-cluster.md - file: elasticsearch/troubleshooting-unbalanced-cluster.md - - file: elasticsearch/elasticsearch-reference/remote-clusters.md + - file: elasticsearch/remote-clusters.md - file: elasticsearch/diagnose-unassigned-shards.md - file: elasticsearch/troubleshooting-shards-capacity-issues.md - file: elasticsearch/data.md @@ -50,8 +50,8 @@ toc: - file: elasticsearch/repeated-snapshot-failures.md - file: elasticsearch/troubleshooting-searches.md - file: elasticsearch/start-ilm.md - - file: elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md - - file: elasticsearch/elasticsearch-reference/security.md + - file: elasticsearch/index-lifecycle-management-errors.md + - file: elasticsearch/security.md children: - file: elasticsearch/security/security-trb-settings.md - file: elasticsearch/security/security-trb-roles.md