-
Notifications
You must be signed in to change notification settings - Fork 57
Sporadically (but often) getting 404 GET error "/api/contents/var/colab/app.log (127.0.0.1): No such file or directory: var/colab/app.log" #27
Comments
The GET request to |
Okay, so how can I see what's the problem? |
adding import logging logging.basicConfig(format='%(asctime)s | %(levelname)s : %(message)s', level=logging.INFO, stream=sys.stdout) to the beginning of your notebook solves this problem. |
I have a similar problem, my OS is Ubuntu 22.10. Colab failed to connect local Docker runtime till I downgraded to jupyterlab==3.0.0 tornado==6.1, like others do. Then it's crashes due to unknown error on importing parts of a package inside a notebook. root@1a404a587288:/home# jupyter notebook --notebook-dir=/ --ip 0.0.0.0 --no-browser --allow-root --NotebookApp.allow_origin='https://colab.research.google.com' --port=8889 --NotebookApp.port_retries=0 | | | |_ __ | | | | ___ Read the migration plan to Notebook 7 to learn about the new features and the actions to take if you are using extensions. https://jupyter-notebook.readthedocs.io/en/latest/migrate_to_notebook7.html Please note that updating to Notebook 7 might break some of your extensions. jupyter_http_over_ws extension initialized. Listening on /http_over_websocket
[I 00:40:21.840 NotebookApp] 302 GET /?token=2e59f48ed4c5bb7e3355ce39c3ab50a2512d1e6e39e64f0c (127.0.0.1) 0.670000ms with messages like
Adding
to the beginning of your notebook didn't solve this problem for me. I even can't see any logging present. I created the dir /var/colab but it didn't change anything. On trying get log in the colab notebook in my browser it opens popup window with message
and how do the relate to /var/colab?
|
Hi!
I have a problem, my Colab notebook keeps crashing when connected to the local runtime (over two SSH tunnels, if it makes the difference) with the error
404 GET /api/contents/var/colab/app.log (127.0.0.1): No such file or directory: var/colab/app.log
. I pasted the cmd output below. Sometimes it happens immediately when I try to run the first cell in the notebook after successful connection to the local runtime and sometimes after some time mid-training (using TF v2). My OS is Ubuntu 18.04.Do you know this problem? Any ideas on how to fix it?
Thanks!
Piotr
The text was updated successfully, but these errors were encountered: