I am having problem on creating of S3 Bucket for Amazon Athena Query Results. I have done this lab 1 two times by following every steps in the video.Still I am not able to get more than 70 points because of this problem. Could any of you please help by telling me how to solve this issue?
Thank you @paryal2 for reporting this issue! After running the glue job, did you make sure to run the cells in the jupyter notebook?
Thank you. The problem was that I did not run the file. The problem is solved thank you!
The Jupyter notebook won’t load the kernel for whatever reason in this lab.
Hi @randomforster , would you be able to share a screenshot of what you see so we can help troubleshoot this?
Test 4 failed: Expected S3 bucket for Amazon Athena Query Results to be created. Please try again. For some reason I cannot get to run C1_W2_Dashboard.ipynb file. Did some manipulations but still showing as attached
I have even converted to .py file and once run the following error raise NoRegionError()
botocore.exceptions.NoRegionError: You must specify a region. I saw the previous topic and most likely the solution is in running the .ipynb file. But how?
Hello @amiguel you need to use the link from the source output to access this notebook, it shows how in Vocarerum step 7. Afterwards you can run the queries in this lab environment. Thanks
Not sure a screenshot would provide much context. I loaded the url for the Jupyter notebook after running the instructions in Cloud9 and then none of the cells from that file would run. I attempted to restart the kernel, but nothing seemed to get it to connect or run the code. My lab timed out so I’ll attempt to rerun again this week and see if that fixes this issue
Sorry that you experienced some issues with the Jupyter notebook part of the lab. Unfortunately I was not able to reproduce that problem. Please re-try the lab and let us know if you are still running into this issue.
The same issue appears again as the command source scripts/setup.sh runs as expected and terraform appears to install without any issue. The Jupyter lab public link opens up but the kernel never connects to be able to run the workbook. Installing the frameworks cell never will run
Hi @randomforster , sorry that you’re experiencing this issue. Did you complete the rest of the lab before running the cells in the Jupyter notebook?
I just tried out the lab, and I was able to run the cells in the notebook after completing the other steps outlined in the assignment instructions. Note: No output is displayed after you run the first cell with all the imports. Also, running the second cell will result in an error if the Glue job you started in step 4.11 has not completed yet. Once the Glue job has successfully completed, you should be able to run the rest of the cells in the Jupyter notebook.
I’ve tried it both ways and neither gets my jupyter notebook to work. Importing frameworks shouldn’t have any dependencies on that other work anyway. My kernel never seems to connect no matter what I do. S3 clearly shows that the job worked fine so I think its a jupyter notebook issue although the terminal appears to show successful installation of python frameworks on source sethup.sh. Just want to reiterate that my cells never run and I’m not even getting an error. If that occurred that would feel like progress but I’m not entirely sure why the kernel won’t run correctly. From doing research perhaps there is a dependency conflict on Anaconda?
Hi @randomforster, I’ve reached out to our engineering team to see if they have any suggestions for how to troubleshoot this. Stay tuned! Thank you for your patience.
1 Like
Okay thanks Jessica! This is the only thing keeping me from completing this first course in this series so please keep me in the loop once the team has had a chance to review further.
Our engineers were not able to reproduce this issue either. We’re in the process of trying to gain learner access to the AWS account you used to see if we can spot any issues there. If we’re not able to do that, I’ll send you some instructions for you to try the lab again, access the log files, and share them with us. I’ll keep you posted on our progress.
Hi @randomforster, our engineer was able to try the lab with the AWS account you used, but unfortunately was not able to reproduce the issue (he was able to start the kernel and the logs seemed ok). Would you be able to try the lab again and share the docker logs from the Jupyter container?
I’m tagging @darivadi here so he can help further troubleshoot this.
Thanks @jessica-dlai. @randomforster, as Jessica mentioned we have tried to run this lab but couldn’t reproduce your issue. Could you try the lab again and follow these steps, so maybe we can see the logs?
- In Cloud9, make sure to execute the
source scripts/setup.shscript. - Once you have the Jupyter URL, execute those commands:
a.docker ps. From this command, take theCONTAINER_IDassociated with the jupyterlab image
b.docker logs <CONTAINER_ID>. Please attach the output that you get from this command. If everything works well, it should look similar to the image that I attach; that way we can see what could be failing with the Jupyter image:
Thanks!
[I 2024-10-17 19:36:39.228 ServerApp] jupyter_lsp | extension was successfully linked.
[I 2024-10-17 19:36:39.239 ServerApp] jupyter_server_terminals | extension was successfully linked.
[I 2024-10-17 19:36:39.273 ServerApp] jupyterlab | extension was successfully linked.
[I 2024-10-17 19:36:39.293 ServerApp] notebook | extension was successfully linked.
[I 2024-10-17 19:36:39.298 ServerApp] Writing Jupyter server cookie secret to /root/.local/share/jupyter/runtime/jupyter_cookie_secret
[I 2024-10-17 19:36:40.739 ServerApp] notebook_shim | extension was successfully linked.
[I 2024-10-17 19:36:40.816 ServerApp] notebook_shim | extension was successfully loaded.
[I 2024-10-17 19:36:40.826 ServerApp] jupyter_lsp | extension was successfully loaded.
[I 2024-10-17 19:36:40.836 ServerApp] jupyter_server_terminals | extension was successfully loaded.
[I 2024-10-17 19:36:40.842 LabApp] JupyterLab extension loaded from /usr/local/lib/python3.9/site-packages/jupyterlab
[I 2024-10-17 19:36:40.842 LabApp] JupyterLab application directory is /usr/local/share/jupyter/lab
[I 2024-10-17 19:36:40.844 LabApp] Extension Manager is ‘pypi’.
[I 2024-10-17 19:36:40.888 ServerApp] jupyterlab | extension was successfully loaded.
[I 2024-10-17 19:36:40.902 ServerApp] notebook | extension was successfully loaded.
[I 2024-10-17 19:36:40.904 ServerApp] Serving notebooks from local directory: /app
[I 2024-10-17 19:36:40.904 ServerApp] Jupyter Server 2.14.2 is running at:
[I 2024-10-17 19:36:40.905 ServerApp] http://0ccca676bd36:8888/lab?token=720d999021807fe1ef57ccaf71525220e1e939f2ffa9f459
[I 2024-10-17 19:36:40.905 ServerApp] http://127.0.0.1:8888/lab?token=720d999021807fe1ef57ccaf71525220e1e939f2ffa9f459
[I 2024-10-17 19:36:40.905 ServerApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 2024-10-17 19:36:40.918 ServerApp]
To access the server, open this file in a browser:
file:///root/.local/share/jupyter/runtime/jpserver-1-open.html
Or copy and paste one of these URLs:
http://0ccca676bd36:8888/lab?token=720d999021807fe1ef57ccaf71525220e1e939f2ffa9f459
http://127.0.0.1:8888/lab?token=720d999021807fe1ef57ccaf71525220e1e939f2ffa9f459
[I 2024-10-17 19:36:40.969 ServerApp] Skipped non-installed server(s): bash-language-server, dockerfile-language-server-nodejs, javascript-typescript-langserver, jedi-language-server, julia-language-server, pyright, python-language-server, python-lsp-server, r-languageserver, sql-language-server, texlab, typescript-language-server, unified-language-server, vscode-css-languageserver-bin, vscode-html-languageserver-bin, vscode-json-languageserver-bin, yaml-language-server
[W 2024-10-17 19:37:38.557 LabApp] Could not determine jupyterlab build status without nodejs
[I 2024-10-17 19:37:47.919 ServerApp] Writing notebook-signing key to /root/.local/share/jupyter/notebook_secret
[W 2024-10-17 19:37:47.923 ServerApp] Notebook C1_W2_Dashboard.ipynb is not trusted
[I 2024-10-17 19:37:48.835 ServerApp] Kernel started: bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd
[I 2024-10-17 19:37:50.115 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:50.120 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:50.125 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[W 2024-10-17 19:37:50.189 ServerApp] Got events for closed stream <zmq.eventloop.zmqstream.ZMQStream object at 0x7f31b50a6d90>
[W 2024-10-17 19:37:50.200 ServerApp] Got events for closed stream <zmq.eventloop.zmqstream.ZMQStream object at 0x7f31b4fbdf10>
[I 2024-10-17 19:37:50.206 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:37:50.594 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:50.596 ServerApp] Discarding 11 buffered messages for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:37:50.605 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[W 2024-10-17 19:37:50.635 ServerApp] Got events for closed stream <zmq.eventloop.zmqstream.ZMQStream object at 0x7f31b4fe8ee0>
[I 2024-10-17 19:37:50.642 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:37:50.694 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:50.695 ServerApp] Discarding 7 buffered messages for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:37:50.729 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:37:51.309 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:51.310 ServerApp] Restoring connection for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:37:51.346 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:37:51.516 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:51.548 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:37:51.753 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:51.790 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:37:52.125 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:52.125 ServerApp] Restoring connection for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:37:52.160 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:37:53.594 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:53.628 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:37:55.690 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:55.733 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:37:56.873 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:37:56.879 ServerApp] Discarding 3 buffered messages for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:37:56.932 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:38:00.795 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:00.795 ServerApp] Discarding 3 buffered messages for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:38:00.847 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:38:03.248 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:03.249 ServerApp] Discarding 3 buffered messages for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:38:03.284 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:38:04.093 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:04.142 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:38:13.800 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:13.800 ServerApp] Restoring connection for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:38:13.817 ServerApp] Replaying 3 buffered messages
[I 2024-10-17 19:38:13.835 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:38:15.249 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:15.292 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:38:15.795 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:15.796 ServerApp] Discarding 3 buffered messages for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:38:15.829 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:38:19.784 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:19.827 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:38:20.499 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:20.502 ServerApp] Discarding 3 buffered messages for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
[I 2024-10-17 19:38:20.546 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:38:26.507 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:26.508 ServerApp] Discarding 3 buffered messages for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:38:26.542 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:03f4eaa4-aa68-41c9-ab2e-69f809f97fd5
[I 2024-10-17 19:38:34.507 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:34.542 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:5deaeeb9-6903-41a2-9a07-d305f6a752aa
[I 2024-10-17 19:38:47.293 ServerApp] Connecting to kernel bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd.
[I 2024-10-17 19:38:47.331 ServerApp] Starting buffering for bcd08b75-e1d7-41c4-84f4-cd9b4efb26bd:401a3cc5-5180-446b-b782-faf7f5ae8fb4
@jessica-dlai is there a way to grant me access to the second course in this series as the bug is the only thing keeping me from progressing. My deadline for completion is technically tomorrow and I was hoping to not have to extend all the due dates if possible.