Skip to content

Commit a55fff4

Browse files
committed
so tired
1 parent f86f574 commit a55fff4

22 files changed

+137
-11
lines changed

troubleshoot/deployments.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,10 @@ navigation_title: "Deployments"
44

55
# Troubleshoot deployments
66

7+
:::{admonition} WIP
8+
⚠️ **This page is a work in progress.** ⚠️
9+
10+
The documentation team is working on restructuring this section. It currently reflects a legacy product-centric structure.
11+
:::
12+
713
% What needs to be done: Write from scratch

troubleshoot/deployments/cloud-enterprise/ask-for-help.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,12 @@ mapped_pages:
55

66
# Ask for help [ece-getting-help]
77

8+
:::{admonition} WIP
9+
⚠️ **This page is a work in progress.** ⚠️
10+
11+
The documentation team is working on moving this content to the [Troubleshooting overview](/troubleshoot/index.md).
12+
:::
13+
814
For issues with Elastic Cloud Enterprise that you cannot fix yourself …​ we’re here to help!
915

1016
If you are an existing Elastic customer with a support contract, please create a ticket in the [Elastic Support Portal](https://support.elastic.co) and provide an ECE [diagnostics package and log files](../../../deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md). By providing a diagnostics package, you make it easier for us to help you.

troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
navigation_title: "Zookeeper quorum"
23
mapped_pages:
34
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-zookeeper-quorum.html
45
---

troubleshoot/deployments/cloud-enterprise/remove-cloud-enterprise.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
---
2+
navigation_title: "Removing containers"
23
mapped_pages:
34
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-uninstall.html
45
---
56

6-
# Remove Elastic Cloud Enterprise [ece-uninstall]
7+
# Remove Elastic Cloud Enterprise containers [ece-uninstall]
78

89
You might need to remove Elastic Cloud Enterprise for one of the following reasons:
910

troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
navigation_title: "Diagnostics"
23
mapped_pages:
34
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-run-ece-diagnostics.html
45
---

troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
---
2+
navigation_title: "Container engines"
23
mapped_pages:
34
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-containers.html
45
---
56

6-
# Troubleshooting container engines [ece-troubleshooting-containers]
7+
# Troubleshoot container engines [ece-troubleshooting-containers]
78

89
This article describes how to troubleshoot container engine services in Elastic Cloud Enterprise. We refer to [Docker](https://www.docker.com/) by default, as it’s the most common container engine, but these steps are also valid for [Podman](https://podman.io/). You can simply replace `docker` in the commands with `podman` as needed.
910

troubleshoot/deployments/cloud-enterprise/use-emergency-roles-token.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
navigation_title: "Emergency roles token"
23
mapped_pages:
34
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-emergency.html
45
---

troubleshoot/deployments/cloud-enterprise/verify-zookeeper-sync-status.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
---
2+
navigation_title: "ZooKeeper sync status"
23
mapped_pages:
34
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-zookeeper-sync.html
45
---
56

6-
# Verify ZooKeeper Sync Status [ece-zookeeper-sync]
7+
# Verify ZooKeeper sync status [ece-zookeeper-sync]
78

89
It is recommended to check the ZooKeeper sync status before starting any maintenance on your Director nodes. This helps you prevent the following scenarios:
910

troubleshoot/deployments/cloud-on-k8s/common-problems.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,12 @@
11
---
2+
navigation_title: "Common issues"
3+
applies:
4+
eck: all
25
mapped_pages:
36
- https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-common-problems.html
47
---
58

6-
# Common problems [k8s-common-problems]
9+
# Troubleshoot common Elastic Cloud on Kubernetes issues [k8s-common-problems]
710

811

912
## Operator crashes on startup with `OOMKilled` [k8s-common-problems-operator-oom]

troubleshoot/deployments/cloud-on-k8s/jvm-heap-dumps.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,12 @@
11
---
2+
navigation_title: "JVM heap dumps"
3+
applies:
4+
eck: all
25
mapped_pages:
36
- https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-jvm-heap-dumps.html
47
---
58

6-
# JVM heap dumps [k8s-jvm-heap-dumps]
9+
# Troubleshoot JVM heap dumps [k8s-jvm-heap-dumps]
710

811
## Ensure sufficient storage [k8s_ensure_sufficient_storage]
912

0 commit comments

Comments
 (0)