Neptune Graph Explorer responding with status 500

0

This is similar to an earlier issue I reported, but today opening Graph Explorer on any cluster in Neptune is presenting me with 500 Internal Server Error. Is this a known issue?

David
질문됨 5달 전291회 조회
1개 답변
0

Hello and thanks for posting. We are currently investigating why this issue happens but it is typically a result of the SageMaker instance upon which the notebook and Graph Explorer reside having undergone some maintenance actions. Simply restarting (stop followed by start) the SageMaker notebook instance should resolve the issue. Please note that during a restart some of the Graph Explorer and Graph Notebook software may be updated. As part of that the sample notebooks included with the Graph Notebook will get replaced with the latest ones. If you have made any edits to those sample notebooks that you wish to keep please make backup copies before restarting the SageMaker instance. You can do the restart from either the Neptune or SageMaker AWS Web console. After the restart the HTTP 500 issue should go away. We are investigating ways to prevent this from happening but in the meantime hopefully that gets you going again.

UPDATED 2023-01-10

Adding an update to mention that a new version of Graph Explorer was just released this week (version 1.5.0). Restarting the instance again should pick up this new version. There are several fixes in the new release that should help in the area of graph synchronization.

AWS
AWS-KRL
답변함 5달 전
  • Stopped and started the instance and it will now boot into Graph Explorer, but its stuck in a loop where it asks to synchronize its database then fails.

  • Thanks for the update. Just to clarify, before you started getting the 500 errors, had you been able to successfully explore a graph?

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠