- Newest
- Most votes
- Most comments
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.
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 ?)
Relevant content
- asked 3 years ago
- asked 9 months ago
- asked 9 months ago
- Accepted Answer
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thanks for your support. However, the problem was that I was using the MultiLogin Chrome extension, which I have stopped using.