Sagemaker Studio default server failing

Question

Hello,
I am trying to start Amazon SageMaker Studio today but without success.
The default server is failing to start. On CloudWatch I only see SIGKILL messages as errors:

```
2022-06-07T10:55:01.523+02:00	2022-06-07 08:55:00,466 WARN killing 'jupyterlabserver' (11) with SIGKILL
2022-06-07T10:55:04.524+02:00	2022-06-07 08:55:01,470 INFO waiting for jupyterlabserver-listener, jupyterlabserver to die
```

On the Apps section I see the default server in status "Failed", and I cannot do anything, not even delete it.

I cannot use the service right now. Is it maybe related to the new release of Jupyter Lab v3.0?

Thanks

Answer

Hi, 
Could you try the steps from this documentation? https://docs.aws.amazon.com/sagemaker/latest/dg/studio-tasks-update-studio.html
You mention that you cannot delete it. How does the UI look like? Is the **Detele** button greyed out? Could you try shutting down all the services in the Studio and create a new one?

Answer

Hello.
Just as an update for this question, the final solution was to delete the entire SageMaker domain suing the AWS cli and recreate it from scratch.
Having done that the problem is no more there, so I encountered by chance some unexpected AWS internal error that stuck my entire domain.
Best

Sagemaker Studio default server failing

Contenus pertinents