fix(rdb): new troubleshooting pages

faq/databases-for-postgresql-and-mysql.mdx

@@ -5,7 +5,7 @@ meta:
 content:
   h1: Managed Database for PostgreSQL and MySQL
 dates:
-  validation: 2024-01-29
+  validation: 2025-01-29
 category: managed-databases
 productIcon: PostgresqlMysqlProductIcon
 ---

menu/navigation.json

@@ -2286,6 +2286,18 @@
               },
               {
                 "items": [
+                  {
+                    "label": "Dealing with Database Instance unavailability",
+                    "slug": "database-instance-unavailable"
+                  },
+                  {
+                    "label": "Dealing with Database Instance connectivity issues",
+                    "slug": "database-instance-connectivity-issues"
+                  },
+                  {
+                    "label": "Dealing with Database Instance performance issues",
+                    "slug": "database-instance-performance-issues"
+                  },
                   {
                     "label": "Dealing with disk_full state in a Database Instance",
                     "slug": "disk-full"

pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx

@@ -0,0 +1,149 @@
+---
+meta:
+  title: Dealing with Database Instance connectivity issues
+  description: Troubleshoot Database Instance connectivity issues for Managed Databases for MySQL and PostgreSQL.
+content:
+  h1: Dealing with Database Instance connectivity issues
+  paragraph: Troubleshoot Database Instance connectivity issues for Managed Databases for MySQL and PostgreSQL.
+tags: disk-full databases
+dates:
+  validation: 2025-01-29
+  posted: 2025-01-29
+categories:
+  - managed-databases
+  - postgresql-and-mysql
+---
+
+## Public access
+
+### Problem
+
+I cannot connect to my Database Instance through the public network.
+
+### Possible causes
+
+- The Database Instance TLS certificate is outdated
+- Your allowed IPs are not properly configured
+- You have reached the maximum number of connections
+- The Database Instance is experiencing instabilities due to a high load
+
+### Solution
+
+You can check the following points to identify and act on what might be causing the issue:
+
+1. If TLS is enabled on the Database Instance, make sure the certificate is up to date, and that your client application is properly configured.
+2. Make sure your [ACLs](/managed-databases-for-postgresql-and-mysql/concepts/#allowed-ips) are [properly configured](/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses).
+3. Make sure your Database Instance has not reached the maximum number of connections stipulated in the advanced settings of the Database Instance. You can monitor the number of connections on [Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit). You can also [adjust the advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) to accept a higher number of connections.
+4. [Monitor other usage metrics on Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit) to:
+
+    - Check if the memory usage is nominal. High memory usage could trigger OOM Kills and cause disconnection
+    - Check Database Instance logs and look for anything else that could explain the issue
+
+## Private access
+
+### Problem
+
+I cannot connect to my Database Instance through a Private Network.
+
+### Possible causes
+
+- The Database Instance TLS certificate is outdated
+- Client network issue
+- You have reached the maximum number of connections
+- The Database Instance is experiencing instabilities due to a high load
+
+### Solution
+
+You can carry out the following actions:
+
+1. Try to connect to the Database Instance from the public endpoint, if one is available, to identify the possible origin (network or instance). This information can help you or the support team to identify the issue.
+2. [Use Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit) to check database logs and look for any activity or behavior that could explain the issue.
+3. Create a support ticket if the first two steps do not help troubleshoot the issue. In the body of the ticket, make sure you provide:
+
+    - The resource ID of resource from which the connection was attempted
+    - The output of the `rdb_troubleshoot.sh` script, indicated below. Make sure you execute the script on the machine from which the connection was attempted.
+
+#### Database Instance connectivity check script
+
+`rdb_troubleshoot.sh`:
+
+```sh
+#!/bin/bash
+
+set -o nounset
+
+if [ -z "$INSTANCE_IP" ]; then
+    echo "INSTANCE_IP is a mandatory environment variable."
+    echo "e.g. export INSTANCE_IP=<xxx.xxx.xxx.xxx>"
+    exit 1
+fi
+
+if [ -z "$INSTANCE_PORT" ]; then
+    echo "INSTANCE_PORT is a mandatory environment variable."
+    echo "e.g. export INSTANCE_PORT=<xxxxx>"
+    exit 1
+fi
+
+function header() {
+    echo -e "\n # ${1}"
+    echo -e "---------------------------------\n"
+}
+
+echo -e "\nRDB troubleshooting script\nThis script will run for several minutes to get enough information."
+header "Host information"
+if ! [ -x "$(command -v uname)" ]; then
+  echo 'Skipped: uname command is not availabe.'
+else
+  uname -a
+fi
+
+header "Host connectivity check"
+if ! [ -x "$(command -v ping)" ]; then
+  echo 'Skipped: ping command is not availabe.'
+else
+  ping -c 5 ${INSTANCE_IP}
+fi
+
+header "Database connectivity check"
+if ! [ -x "$(command -v telnet)" ]; then
+  # try to fallback on curl telnet
+  if ! [ -x "$(command -v curl)" ]; then
+    echo "Skipped: neither telnet nor curl command are availabe."
+  else
+    echo "(using curl)"
+    timeout 2 curl -v telnet://$INSTANCE_IP:$INSTANCE_PORT
+  fi
+else
+  echo "(using telnet)"
+  echo -n | telnet ${INSTANCE_IP} ${INSTANCE_PORT}
+fi
+
+header "Ip configuration check"
+if ! [ -x "$(command -v ip)" ]; then
+  echo 'Skipped: ip command is not availabe.'
+else
+  echo -e "Interfaces:\n- \n"
+  ip a
+  echo -e "\nNeighbour:\n- \n"
+
+  TEST_ITERATION=30
+  TEST_INTERVAL=10 # seconds
+
+  # Iterate a few times to try to catch relevant info
+  for ((i=1;i<=$TEST_ITERATION;i++)); do
+    echo -e "\nIteration $i:\n"
+    ip neighbour show
+    echo -e "\nWaiting ${TEST_INTERVAL}s...\n"
+    sleep $TEST_INTERVAL
+  done
+  echo -e "\nRoute:\n-\n"
+  ip route
+fi
+```
+Run the script in a terminal:
+
+```
+export INSTANCE_IP=<xxx.xxx.xxx.xxx>
+export INSTANCE_PORT=<xxxxx>
+./troubleshoot.sh
+```

pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx

@@ -0,0 +1,38 @@
+---
+meta:
+  title: Dealing with Database Instance performance issues
+  description: Troubleshoot Database Instance performance issues in Managed Databases for MySQL and PostgreSQL.
+content:
+  h1: Dealing with Database Instance performance issues
+  paragraph: Troubleshoot Database Instance performance issues in Managed Databases for MySQL and PostgreSQL.
+tags: disk-full databases
+dates:
+  validation: 2025-01-29
+  posted: 2025-01-29
+categories:
+  - managed-databases
+  - postgresql-and-mysql
+---
+
+## Problem
+
+My Database Instance is not performing as expected.
+
+## Possible causes
+
+- High data loads
+- High incoming traffic from specific apps or websites
+- Huge or sub-optimized SQL queries
+
+## Solution
+
+You can carry out the following actions:
+
+1. [Monitor usage metrics on Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit) to:
+
+    - Check if the usage is nominal. The Database Instance can be impacted by high data loads or unexpected high traffic from an app or website, for example. You can [upgrade your Instance](/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database) if necessary.
+    - Check if there are slow queries in the Database Instance log. Huge or sub-optimized queries can slow down the instance significantly, or even fill up all the memory and trigger OOM kills.
+
+2. Try connecting to the Database Instance in a [Private Network](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network). Public endpoint traffic for Managed Databases for MySQL and PostgreSQL goes through a load balancer, which adds significant latency. Using a Private Network also ensures better security, which makes it the recommended way to connect to a Managed Database.
+
+3. Upgrade your storage volume solution. New Block Storage volumes provide improved performance compared to the Block Storage Legacy, for example.

pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx

@@ -0,0 +1,34 @@
+---
+meta:
+  title: Dealing with Database Instance unavailability
+  description: Troubleshoot Database Instance unavailability for Managed Databases for MySQL and PostgreSQL.
+content:
+  h1: Dealing with Database Instance unavailability
+  paragraph: Troubleshoot Database Instance unavailability for Managed Databases for MySQL and PostgreSQL.
+tags: disk-full databases
+dates:
+  validation: 2025-01-29
+  posted: 2025-01-29
+categories:
+  - managed-databases
+  - postgresql-and-mysql
+---
+
+## Problem
+
+My Database Instance is unavailable.
+
+## Possible causes
+
+- High data loads
+- High incoming traffic from specific apps or websites
+
+## Solution
+
+You can monitor your Database Instance activity to be able to quickly identify and act on irregular activities that might be causing the instability/unavailability.
+
+[Monitor usage metrics on Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit) to:
+
+    - Check if the usage is regular. Database Instance can be impacted by high data loads or unexpected high traffic from an app or website, for example
+    - Check if there are slow queries in the Database Instance log. Huge or sub-optimized queries can fill up all the memory and trigger OOM kills
+    - Check the Database Instance logs for any unusual or suspicious activity