在Kubernetes安装程序中安装MSSQL群集时安装失败（Ubuntu-18.04）

Question

I am facing the below error while installing MSSQL cluster in Kubernetes setup.

Error:

Starting cluster deployment.

Cluster controller endpoint is available at XX.XX.XX.XX:30080. Cluster control plane is ready.

[Request 112e9901-602d-4400-89cf-203df5db34f1] Cluster mssql-cluster does not exist. 
Data pool resources cleanup failed System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) ---> System.ComponentModel.Win32Exception (0x80004005): An existing connection was forcibly closed by the remote host
[Pod: master][Container: mssql-server] The provisioner has timed out.

Provisioning for cluster 'mssql-cluster' has failed

Cluster deployment failed. Cluster State: Error.

Collecting the logs for cluster 'mssql-cluster'. Collecting logs for containers...

Data pool resources cleanup failed System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=10; handshake=14994;  ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out

Data pool resources cleanup failed System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=10; handshake=14994;  ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out

Data pool resources cleanup failed System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.) ---> System.ComponentModel.Win32Exception (0x80004005): No such host is known

Data pool resources cleanup failed System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.) ---> System.ComponentModel.Win32Exception (0x80004005): No such host is known

[Errno 111] Connection refused : Failed to collect cluster logs after retrying for 2 minute(s).. More detail can be found in the mssqlctl.log file
Failed to copy cluster logs
Traceback (most recent call last):

Can you please provide you help to resolve this issue.

Answer 1

Those errors: Cluster mssql-cluster does not exist. The server was not found or was not accessible Cluster mssql-cluster does not exist. The server was not found or was not accessible looks like problem with deployment and configuration.

So please follow those guidelines like:

• During deploying you can use one of the default configuration/custom configuration ,
• Monitor the deployment ,
• Retrieve endpoints ,
• Verify the cluster status ,
• Kubernetes troubleshooting ,

Hope this help.