From 64fd70e5e0fa26949fb43d53944e12c8865d720a Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Wed, 29 Jan 2025 15:58:02 +0100 Subject: [PATCH 1/9] fix(rdb): troubleshooting --- menu/navigation.json | 12 ++ .../database-instance-connectivity-issues.mdx | 149 ++++++++++++++++++ .../database-instance-performance-issues.mdx | 37 +++++ .../database-instance-unavailable.mdx | 34 ++++ 4 files changed, 232 insertions(+) create mode 100644 pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx create mode 100644 pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx create mode 100644 pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx diff --git a/menu/navigation.json b/menu/navigation.json index 9542f0135c..0d341dd605 100644 --- a/menu/navigation.json +++ b/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" diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx new file mode 100644 index 0000000000..fb1c4c5a8f --- /dev/null +++ b/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 +- You have a high memory usage + +### 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 does not reach 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 advances 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 regular. 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 +- Your allowed IPs are not properly configured +- You have reached the maximum number of connections +- You have a high memory usage + +### Solution + +You can carry out the following actions: + +1. Check if you are you able to connect to the Database Instance from the public endpoint, if one is available. +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=" + exit 1 +fi + +if [ -z "$INSTANCE_PORT" ]; then + echo "INSTANCE_PORT is a mandatory environment variable." + echo "e.g. export INSTANCE_PORT=" + 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= +export INSTANCE_PORT= +./troubleshoot.sh +``` diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx new file mode 100644 index 0000000000..94bc64594e --- /dev/null +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx @@ -0,0 +1,37 @@ +--- +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 + +## 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 regular. 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 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 might add significant latency. + +3. Upgrade your storage volume solution. New Block Storage volumes provide improved performance compared to the Block Storage Legacy, for example. \ No newline at end of file diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx new file mode 100644 index 0000000000..3151632e9e --- /dev/null +++ b/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 Database Instance logs and look for anything else that could explain the issue \ No newline at end of file From 0d049ca85fe3544a05894eacc0b82f13f02ac737 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Wed, 29 Jan 2025 17:23:53 +0100 Subject: [PATCH 2/9] fix(rdb): review bastien Co-authored-by: Bastien Wirtz --- .../troubleshooting/database-instance-connectivity-issues.mdx | 4 ++-- .../troubleshooting/database-instance-performance-issues.mdx | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx index fb1c4c5a8f..c6734a2d30 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx @@ -25,7 +25,7 @@ I cannot connect to my Database Instance through the public network. - The Database Instance TLS certificate is outdated - Your allowed IPs are not properly configured - You have reached the maximum number of connections -- You have a high memory usage +- The Database Instance experiences instabilities due to a high load ### Solution @@ -36,7 +36,7 @@ You can check the following points to identify and act on what might be causing 3. Make sure your Database Instance does not reach 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 advances 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 regular. High memory usage could trigger OOM Kills and cause disconnection + - 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 diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx index 94bc64594e..85880ad51a 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx @@ -29,8 +29,8 @@ 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 regular. 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 fill up all the memory and trigger OOM kills + - 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 might add significant latency. From 34cc5b1f9d4828b32521e53017af8188653d9280 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Wed, 29 Jan 2025 17:24:34 +0100 Subject: [PATCH 3/9] fix(rdb): review bastien 2 Co-authored-by: Bastien Wirtz --- .../troubleshooting/database-instance-connectivity-issues.mdx | 3 +-- .../troubleshooting/database-instance-performance-issues.mdx | 3 ++- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx index c6734a2d30..00607fff68 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx @@ -47,8 +47,7 @@ I cannot connect to my Database Instance through a Private Network. ### Possible causes -- The Database Instance TLS certificate is outdated -- Your allowed IPs are not properly configured +- Client network issue - You have reached the maximum number of connections - You have a high memory usage diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx index 85880ad51a..6233880e3e 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx @@ -22,6 +22,7 @@ My Database Instance is not performing as expected. - High data loads - High incoming traffic from specific apps or websites +- Huge or sub-optimized SQL queries ## Solution @@ -32,6 +33,6 @@ You can carry out the following actions: - 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 might add significant latency. +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. It 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. \ No newline at end of file From 55385aabab6fc98df2352872d554c80c47f3c545 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 30 Jan 2025 14:13:15 +0100 Subject: [PATCH 4/9] fix(rdb): review ro Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- .../database-instance-connectivity-issues.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx index 00607fff68..92579e6ca2 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx @@ -25,15 +25,15 @@ I cannot connect to my Database Instance through the public network. - 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 experiences instabilities due to a high load +- 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. +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 does not reach 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 advances settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) to accept a higher number of connections. +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 advances 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 From e207aaf6a3a389d0cf0f0d512749b0993ac20211 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 30 Jan 2025 14:25:47 +0100 Subject: [PATCH 5/9] fix(rdb): date faq --- faq/databases-for-postgresql-and-mysql.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/faq/databases-for-postgresql-and-mysql.mdx b/faq/databases-for-postgresql-and-mysql.mdx index 12f7598829..7cc22eef42 100644 --- a/faq/databases-for-postgresql-and-mysql.mdx +++ b/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 --- From 035b9fdc8cffee79eb6b036f38003f6858f847b9 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 30 Jan 2025 14:47:19 +0100 Subject: [PATCH 6/9] fix(rdb): review ro 2 --- .../troubleshooting/database-instance-performance-issues.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx index 6233880e3e..a85b55b643 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx @@ -33,6 +33,6 @@ You can carry out the following actions: - 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. It also ensures better security, which makes it the recommended way to connect to a Managed Database. +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. \ No newline at end of file From 843f0def8f7be7f7dc528c886961dd7c8d3d16a7 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Fri, 31 Jan 2025 10:46:16 +0100 Subject: [PATCH 7/9] fix(rdb): reviews Co-authored-by: Bastien Wirtz --- .../troubleshooting/database-instance-connectivity-issues.mdx | 4 ++-- .../troubleshooting/database-instance-unavailable.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx index 92579e6ca2..45815030aa 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx @@ -49,13 +49,13 @@ I cannot connect to my Database Instance through a Private Network. - Client network issue - You have reached the maximum number of connections -- You have a high memory usage +- The Database Instance is experiencing instabilities due to a high load ### Solution You can carry out the following actions: -1. Check if you are you able to connect to the Database Instance from the public endpoint, if one is available. +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: diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx index 3151632e9e..b66d69e8d4 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-unavailable.mdx @@ -31,4 +31,4 @@ You can monitor your Database Instance activity to be able to quickly identify a - 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 Database Instance logs and look for anything else that could explain the issue \ No newline at end of file + - Check the Database Instance logs for any unusual or suspicious activity \ No newline at end of file From 75e9baf339ff5c48c8888563e421382f33941384 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Fri, 31 Jan 2025 10:48:35 +0100 Subject: [PATCH 8/9] fix(rdb): reviews 2 --- .../troubleshooting/database-instance-connectivity-issues.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx index 45815030aa..e0ae734700 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx @@ -47,6 +47,7 @@ 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 From 4a95dfbe014214070e7d03125f72efe002da83c7 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Fri, 31 Jan 2025 15:21:40 +0100 Subject: [PATCH 9/9] fix(rdb): review bene Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- .../troubleshooting/database-instance-connectivity-issues.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx index e0ae734700..4442c727cc 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx @@ -33,7 +33,7 @@ You can check the following points to identify and act on what might be causing 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 advances settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) to accept a higher number of connections. +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