Databricks

lndlzy · ‎09-10-2023

Hello everyone, I tried to change a Databricks Runtime Cluster from 12.2 LTS ML to 13.3 LTS ML, however I got this error:

Failed to add 1 container to the compute. Will attempt retry: false. Reason: Global init script failure

Global init script Install MSODBC failed: Script exit status is non-zero

Does anybody know why this is happening and would it be possible for you to help me resolve this issue? Thank you!

Kaniz · ‎09-11-2023

Hi @lndlzy, Based on the information, your error is related to a global init script failure when changing the Databricks Runtime Cluster from 12.2 LTS ML to 13.3 LTS ML. This error indicates that the worldwide init script failed with a non-zero exit status.

To resolve this issue, you can try the following steps:

1. Check the global init script: Review it and ensure it is correctly configured and contains no errors. You can access the global init script settings in the Databricks UI or through the API.

2. Retry the cluster creation: If the global init script is correct, you can try creating the cluster again and see if the error persists. Sometimes, the error could be transient and might not occur on subsequent attempts

3. If the issue persists, filing a support ticket with Databricks Support is recommended for assistance. They can guide troubleshooting of the specific error and help resolve any underlying problems.

View solution in original post

Kaniz · ‎09-11-2023

Hi @lndlzy, Based on the information, your error is related to a global init script failure when changing the Databricks Runtime Cluster from 12.2 LTS ML to 13.3 LTS ML. This error indicates that the worldwide init script failed with a non-zero exit status.

To resolve this issue, you can try the following steps:

1. Check the global init script: Review it and ensure it is correctly configured and contains no errors. You can access the global init script settings in the Databricks UI or through the API.

2. Retry the cluster creation: If the global init script is correct, you can try creating the cluster again and see if the error persists. Sometimes, the error could be transient and might not occur on subsequent attempts

3. If the issue persists, filing a support ticket with Databricks Support is recommended for assistance. They can guide troubleshooting of the specific error and help resolve any underlying problems.