What Should I Do If a Database Server Problem Causes a Connection Failure to a TaurusDB for PostgreSQL Instance?

Check whether any of the following problems occur on the TaurusDB for PostgreSQL instance:

1. The TaurusDB for PostgreSQL instance is not properly connected.

   Solution: Check the connection. If you connect to the TaurusDB for PostgreSQL instance over a private network, the ECS and the TaurusDB for PostgreSQL instance must be in the same VPC and the TaurusDB for PostgreSQL instance can be accessed only through an ECS in the same VPC. If you connect to the TaurusDB for PostgreSQL instance over a public network, the ECS and the TaurusDB for PostgreSQL instance can be in different VPCs.

2. The maximum number of connections has been reached.

   Solution: Use TaurusDB for PostgreSQL resource monitoring to check if the CPU usage and the number of connections are within the allowed ranges. If either of them has reached the maximum, reboot or disconnect the TaurusDB for PostgreSQL instance.

3. The TaurusDB for PostgreSQL instance is abnormal. For example, the TaurusDB for PostgreSQL instance fails to be rebooted, the system is faulty, or the instance or table is locked.

   Solution: Reboot the TaurusDB for PostgreSQL instance. If the problem persists, contact post-sales technical support.