Skip to content

Neptune Notebooks and Graph Explorer Fail to Launch

0

When trying to launch Juptyer, Jupyter Lab, Graph Explorer, Start, Stop or Delete Neptune Notebooks with the Status of 'Ready', I'm blocked by a pop-up disclaimer stating:

"Notebook status must be Ready while the current status is undefined"

I have rebooted, started, stopped these instances connected to the notebooks, gone into Sagemaker and started, stopped these notebooks, created new DB Clusters and instances w/ notebooks, to no avail.

Is there a solution to this problem? If this is simply a UI bug, is there any other way to access Graph Explorer?

asked 2 years ago1.1K views
2 Answers
0
Accepted Answer

This is a bug that we also discovered early this morning. A fix has been submitted and is currently rolling out to all regions.

To access Graph Explorer, for now, go to the SageMaker console and open the Notebook instance as if you're opening it to use Jupyter. After Jupyter is open, change the URL to:

https://<your_notebook_endpoint>/proxy/9250/explorer/

That should open Graph Explorer.

AWS
answered 2 years ago
EXPERT
reviewed 2 years ago
  • Hello, I was able to get into graph explorer. But it will try to synchronize and fail. Any help is appreciated. index-7a44db79.js:792

       POST https://aws-neptune-graph-explorer-wlvw.notebook.us-east-1.sagemaker.aws/proxy/9250/gremlin 500 (Internal Server Error)
    
  • Not much to go on with just the 500 error. Are you able to open Dev Tools in your browser and look in the console there to see exactly what is causing the 500 error?

  • Access to fetch at 'https://aws-neptune-graph-explorer.notebook.us-east-1.sagemaker.aws/proxy/9250/logger' from origin 'https://aws-neptune-graph-explorer-wlvw.notebook.us-east-1.sagemaker.aws' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. index-7a44db79.js:779 GET https://aws-neptune-graph-explorer.notebook.us-east-1.sagemaker.aws/proxy/9250/logger net::ERR_FAILED index-7a44db79.js:779

    Uncaught (in promise) TypeError: Failed to fetch at ewt._sendLog (index-7a44db79.js:779:2003) at ewt.error (index-7a44db79.js:779:1778) at index-7a44db79.js:965:168436 at async index-7a44db79.js:2536:1833 _sendLog @ index-7a44db79.js:779 error @ index-7a44db79.js:779 (anonymous) @ index-7a44db79.js:965

  • What version of Graph Explorer are you using? Version is in top right corner next to Connections button. If using Graph Notebook from the same instance, are you able to send queries and leverage the notebooks (validating network and permissions are correct)?

  • 1.8.0. I am using the same notebook for Jupyter and jupyter lab, querying the neptune database and getting results out.

0

I tried this, and it does boot into Graph Explorer, but I'm now stuck in a loop where its asking me to synchronize my database, then fails everytime.

answered 2 years ago
  • Looks like the original issue should be fixed now. If you pull up developer tools in your browser, which request do you see failing and what is the error response that you're seeing? Are you seeing any issues when using the Jupyter magics from the same instance (able to validate connectivity)?

  • Same issue here, it is failing to synchronize the database and failing.

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.