使用 Microsoft 登入
登入或建立帳戶。
您好:
選取其他帳戶。
您有多個帳戶
選擇您要用來登入的帳戶。
英文
很抱歉,此文章目前沒有您所使用語言的版本。

Symptoms

You try to deploy Microsoft SQL Server 2019 Big Data Cluster (BDC) Cumulative Update 5 (CU5) or Cumulative Update 6 (CU6) (regardless of the azdata version) on a Kubernetes cluster that's running on RHEL host OS. In this scenario, you notice that the deployment fails and returns the following error message:

DateTime [LAUNCH] The process "grafana" exists and returns error: The process exited with code '1' and error: exit status 1

DateTime [LAUNCH] Starting to force stop process "grafana"

DateTime The process launcher "grafana" exited: Failed to force stop the process "grafana": no such process

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Resolution

This issue is fixed in the following cumulative update for SQL Server:

About cumulative updates for SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Workaround

To work around this issue, you can add “security”: { “allowRunAsRoot”: true } in the Control.json file to unlock the deployment.

References

Learn about the terminology that Microsoft uses to describe software updates.

需要更多協助嗎?

想要其他選項嗎?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

這項資訊有幫助嗎?

以下何者是您會在意的事項?
按下 [提交] 後,您的意見反應將用來改善 Microsoft 產品與服務。 您的 IT 管理員將能夠收集這些資料。 隱私權聲明。

感謝您的意見反應!

×