404 issues with Voila on SageMaker

[illinineverdie]

I have a notebook in AWS SageMaker that I would like to launch with voila. After installing voila in the default JupyterSystemEnv conda env.. and have installed voila. The notebook launches with a 404.. and I see the following logs.

Masked\stripped copy of logs. 404 GET /static/components/react/react-dom.production.min.js (..an ip..) 1.46ms referer=https://<URL>/notebooks 404 GET /static/components/react/react-dom.production.min.js (..an ip..) 1.43ms referer=https://<URL>/notebooks 404 GET /static/components/react/react-dom.production.min.js (..an ip..) 1.43ms referer=https://<URL>/notebooks/my.ipynb 404 GET /static/components/react/react-dom.production.min.js (..an ip..) 1.37ms referer=https://<URL>/notebooks/my.ipynb Kernel started: .... No session ID specified Saving file at .....ipynb 404 GET /voila/render/notebooks/my.ipynb (10.0.0.201) 2.36ms referer=https://<notebooks URL>/notebooks/qms_user_interface.ipynb 404 GET /static/components/react/react-dom.production.min.js (10.0.0.125) 2.25ms referer=https://<URL>/voila/render/my.ipynb

I don't see the /static/components/react/ path off the root directory.

Some key package versions jupyter-client 6.1.7 jupyter-console 6.2.0 jupyter-core 4.7.0 jupyter-server 0.1.1 jupyterlab 1.2.18 jupyterlab-git 0.11.0 jupyterlab-pygments 0.1.1 jupyterlab-server 1.2.0 ... nb-conda 2.2.1 nb-conda-kernels 2.3.1 nbconvert 5.6.1 nbdime 1.1.0 nbexamples 0.0.0 nbformat 5.0.8 nbserverproxy 0.3.2 ... notebook 5.7.10

UPDATE: I am launching voila from Jupyter Notebook classic "voila" extension.

UPDATE2: To add to this, I am not seeing a kernel-<some_guid>json file being created under /tmp/voila_

[jtpio]

After installing voila in the default JupyterSystemEnv conda env

Does installing a new package restart the notebook server in AWS Sage maker?

Normally restarting the notebook server would be required for the new Voila endpoints to be exposed.

[dreams-and-thoughts]

voila/extension is listed as 'Possibly incompatible' in the nbextensions tab after installing:

These are the commands I use:

pip install voila
jupyter serverextension enable voila --sys-prefix
sudo initctl restart jupyter-server --no-wait

[aelouassif]

Having the same problem, this is the solution that works for me :

If your instance is on Amazon Linux 1, use

sudo initctl restart jupyter-server --no-wait If your instance is on Amazon Linux 2, use

sudo systemctl restart jupyter-server, which is equivalent to sudo service jupyter-server restart.