Sagemaker Studio's Terminals do not open up

0

When I open up the Git terminal ( or Kernel's terminal, both do not open up but instead just have ... in their tab's title. I have created a new domain from scratch, and the problem is the same there. I also shut down the kernel and restart again, but that didn't work either. This didn't happened before in another AWS environment, but since yesterday, this has happened in the current AWS environment that I am using.

I opened up the developer tools' console, and I see two error messages repeating indefinitely:

  1. Connection lost, reconnecting in x seconds
  2. WebSocket connection to '...' failed: Terminal websocket closed: undefined

I don't know what I could do to fix this issue. In case you are thinking maybe I don't have a Kernel running which a terminal needs to run, I do have a Kernel up and running.

asked 10 months ago509 views
2 Answers
0
Accepted Answer

My problem was that I was using MultiLogin Chrome Extension , which I use whenever there are multiple AWS environments between which I need to constantly switch. Anyway, I stopped using the Sagemaker studio from inside the tab created by that extension and everything worked properly. Thanks to everyone who tried to help.

answered 10 months ago
0

Can you test on a different browser ?

Otherwise, navigate to all active Terminal Sessions and shut down all Terminal Sessions by clicking on the Button Icon for shutdown

Can you try deleting the Kernel Gateway Apps from your SageMaker Console. From your SageMaker Console (Not the same as Studio environment) navigate to your User Profile for your Domain until you reach a page that looks similar to “Kernel Gateway Apps”. Once you navigated to the Kernel Gateway Apps, delete all Kernel Gateway Apps. After first deleting all of the Kernel Gateway Apps, then lastly delete the Jupyter Server App which has the App Name “default”. (This process will take some time). Finally once all of the Apps are deleted, relaunch your Studio Profile which will initialise, then select a Notebook and select any random Kernel (for e.g. Data Science). Once the Kernel is active, then you may try and launch your Studio Image Kernel Terminal. (Confirm whether you are still receiving an error?) Also test our launching the standard terminal by selecting “File”-> “New Terminal” (different from the Kernel Terminal) (Confirm whether this Terminal can launch ?)

AWS
answered 10 months ago
  • Thanks for your support. However, the problem was that I was using the MultiLogin Chrome extension, which I have stopped using.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions