Hello everyone,
I believe you can learn how to deal with DBSS instance failure from my case.
Symptom
Logging in to a DBSS instance fails.
Troubleshooting Procedure
1. Log in to Service OM.
2. Choose Computing > ECS, and locate DBSS instances.
3. Check the IP addresses of the instance, usually including the following:
IP address used for tenant service connection
Internal public network IP address
Elastic IP address (EIP)
IP address of an internal VPC of the DBSS
4. Check whether the IP address of the internal VPC of the DBSS conflicts with that of the related network in the environment (usually, the IP address conflicts with the CIDR of the external network or EIP). If a conflict exists, modify the DBSS configuration and create an instance again.
5. The CIDR of the internal network created by DBSS overlaps that of the related network in the environment (generally, the CIDR of the internal network overlaps that of the external network or EIP).
To resolve this problem, log in to the DBSS instance through Service OM and manually add a static route.
route add -host (Local IP address) gw (Gateway of the instance eth1)
For example:
route add -host 192.168.0.222 gw 192.168.0.1
Solution
1. Modify the /etc/scc/conf/dbss/dbss_config.properties configuration file of all SCC-Service nodes. Modify or add the configurations dbss.cidr.typeA.flag and dbss.cidr.typeA, for example, dbss.cidr.typeA.flag = 192.198.198, and dbss.cidr.typeA = 192.198.198.0/24.
2. Run the following command to restart the Tomcat service:
systemctl restart systemd-tomcat
3. Create a new VPC for creating the DBSS instance (the original VPC has been mapped to the faulty VPC in the DBSS. Therefore, the tenant needs to create a new VPC for the DBSS to generate a new internal VPC).
4. Verify the creation of the DBSS instance again.
You are welcome to ask me any questions about this case!
