【问题标题】:Installation is getting failed while installing MSSQL cluster in Kubernetes setup (Ubuntu-18.04)在 Kubernetes 设置中安装 MSSQL 集群时安装失败 (Ubuntu-18.04)
【发布时间】:2019-09-18 17:56:24
【问题描述】:

在 Kubernetes 设置中安装 MSSQL 集群时遇到以下错误。

错误:

开始集群部署。

集群控制器端点在 XX.XX.XX.XX:30080 可用。 集群控制平面已准备就绪。

[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.

集群“mssql-cluster”的配置失败

集群部署失败。集群状态:错误。

收集集群“mssql-cluster”的日志。 正在为容器收集日志...

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):

能否请您帮助解决此问题。

【问题讨论】:

    标签: sql-server docker kubernetes


    【解决方案1】:

    那些错误:Cluster mssql-cluster does not exist. The server was not found or was not accessible 看起来像是部署和配置问题。

    所以请遵循以下准则:

    希望对您有所帮助。

    【讨论】:

    • 这些文件解决了我最初的问题。但是现在集群设置已经等待了很长时间。 BDC & Master 池等待时间长(超过 2 小时)
    • 请提供更多信息。你当时做了什么部署和配置yaml)
    猜你喜欢
    • 2019-08-20
    • 1970-01-01
    • 1970-01-01
    • 2020-12-13
    • 1970-01-01
    • 2016-06-07
    • 1970-01-01
    • 1970-01-01
    • 2020-01-24
    相关资源
    最近更新 更多