creating jupyter notebook in watson - jupyter-notebook

while creating jupyter notebook I am getting this error. I have also created the api key. Kindly help me please I am sharing the error screenshot1

Related

GCP Notebook Instance: Error 524 unable to open Jupyter lab

I am currently new to the GCP ecosystem. Over the past week, I have successfully created a notebook instance and have been using it. However, recently I encounter an issue whereby I am unable to open jupyter lab. Upon looking at the health status (image below). I realise the Juypter Lab API Status and Jupyterlab status are unhealthy.
Things I have tried and did not work:
Restarting the notebook instance
Restarting the Jupyter API
Restarting the Docker
Wondering if anyone has faced similar issues before? Any guidance on fixing this would be highly appreciated. Thank you in advance!
Notebook Health Status
Have you tried to run the troubleshooting 'diagnostic tool' as mentioned here:
https://cloud.google.com/vertex-ai/docs/general/troubleshooting#opening_a_notebook_results_in_a_524_a_timeout_occurred_error ?
Take a look at the output log of it and it might give you some hint what is the problem.

Kubeflow: Notebook server stuck on loading

Whenever I try to create a Kubeflow notebook server to build a pipeline from a jupyter notebook, it keeps loading forever without displaying any error.
I'm currently using a Kubeflow dashboard that's already up and running on a server, so I didn't deploy it myself and I'm not working on a local instance to use the terminal.
Any idea what the origin of the problem might be and how to solve it?
Here's a screenshot that might explain better.

Using Viola with jupyter notebook on Binder gives error

I am doing the fast.ai v2 course on deep learning and on deploying my first app (as suggested in chapter 2 of the book, I am using viola on top of the jupyter notebook to make it run without showing the cells, therefore act as an app. When I run it on binder it gives the following error.
The related github (therefore the codes) is here and you can open the binder by clicking the logo in the readme. I would be grateful for your help

Cant connect to workspace

Im trying to complete the very first training module offered by MS. Something Im missing that isn't detailed on the documentation of the training.
These are the instructions I'm following
https://github.com/MicrosoftDocs/mslearn-aml-labs/blob/master/labdocs/Lab01.md
All good until I have to run the second command defined on the notebook called
"01-Getting_Started_with_Azure_ML.ipynb".
And yes I entered the device login code as the instructions indicate.
Look at the attached screenshot of the error returned after running the command of the notebook.
Opened a case with Microsoft. They noticed is an issue affecting their VM servers.
This is their reply:
Hi Marbin,
Hope you are doing good. I had discussed this with our team as well. This was a known issue with workspace names with capital letters. So, the workspace name ‘ML_Battlefield’ was creating the issue. This is fixed in SDK version 1.3.0.
In the compute instance notebook, we can update the SDK version to: pip install --upgrade azureml-sdke

How to activate a debugger or access logs in Jupyter notebooks?

I am trying to run a R notebook on Microsoft's Azure notebooks cloud service.
When I am trying to run all cells, it displays a Loading required package: ggplot2 in the last cell and then the Kernel systematically crashes. I get:
The kernel appears to have died. It will restart automatically.
But the Kernel does not restart automatically.
How can I get a log describing the encountered issue? Is there a way to activate a debugger?
When you're running Jupyter usually you'll see messages about kernel issues in standard I/O of the console that you launch. In Azure Notebooks this gets redirected to a file at ~/.nb.log. You can open a new terminal by clicking on the Jupyter icon, and then doing New->Terminal, and doing cat ~/.nb.log. You could also start a new Python notebook for this purpose and do "!cat ~/.nb.log" - but unfortunately you can't just do that from an R notebook, they don't support the "magic" ! commands.
Usually that gives you a good starting point. If that doesn't help much you could try invoking R directly from the terminal and trying the repro steps there and see if that's more useful.

Resources