Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data and Jupyter notebooks are inaccessible from Azure Notebook VM #5148

Open
lawrence-lachman opened this issue Jan 9, 2020 · 0 comments
Open

Comments

@lawrence-lachman
Copy link

I created a STANDARD_E16S_V3 notebook VM in my Azure Machine Learning service on December 11. After running ML experiments on it for the past month, I have not been able to access the data or Jupyter notebooks stored on the Azure blob for the past two days. I can start and stop the VM successfully, but clicking on Jupyter (or JupyterLab) to launch the Jupyter notebook view of my storage always results in:

"Timed out attempting to connect to this notebook VM. Check to make sure the notebook VM is started. If you just started it, try again in a minute or two.

The browser tab just displays the spinning icon while nothing is ever successfully accessed.

Three times in the past 48 hours, the data and notebooks on the VM became accessible for about a 10 minute window; once yesterday, and twice today, but then promptly went back down.

Since this is just a virtual machine, I also tried to create another STANDARD_E16S_V3 and specified a different region, but I clearly wasn't successful because I get the same behavior/result with this new VM.

I paid the $29 to get Microsoft technical support - and basically tell them that their service isn't working - and spoke with one of their representatives today, but he knows nothing about the Machine Learning platform. He tried to contact the Azure ML Service program manager and product group, but has not gotten a reply. Can anyone help me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant