aiidalab-launch status not showing the URL information

[unkcpz]

reported by @ramirezfranciscof, he is running the old aiidalab/aiidalab-docker-stack image but the URL information is not shown by aiidalab-launch status. Neither the jupyter notebook list inside the container shows no such information.

[danielhollas]

Surely if the jupyter notebook list doesn't show anything the notebook server is actually not running right?
Could he send the output of aiidalab-launch logs.

[unkcpz]

Sure, he sent the screenshots to me. Here they are:

The status are exceptional status.

(aurora-aiidalab) framirez@theospc1:aurora$ aiidalab-launch status
A new version of aiidalab-launch is available: 2023.1017 (installed: v2022.1016)
Run `pipx upgrade aiidalab-launch` to update.
Profile    Container         Status    Mount                  URL
---------  ----------------  --------  ---------------------  -----
default    aiidalab_default  down      aiidalab_default_home
aurora     aiidalab_aurora   exited    aiidalab_aurora_home

And nothing show in jupyter notebook list:

(aurora-aiidalab) framirez@theospc1:aurora$ docker ps
CONTAINER ID   IMAGE                                   COMMAND              CREATED        STATUS      PORTS                                       NAMES
d575c7afef91   aiidalab/aiidalab-docker-stack:22.8.1   "/sbin/my_my_init"   3 months ago   Up 4 days   0.0.0.0:8888->8888/tcp, :::8888->8888/tcp   aiidalab-16_aiidalab_1
(aurora-aiidalab) framirez@theospc1:aurora$ docker exec -it d575c7afef91 /bin/bash
root@d575c7afef91:/opt# jupyter notebook list
Currently running servers:
root@d575c7afef91:/opt# 

However, the docker ps and docker logs show that container in running without issues.
Maybe aiidalab-launch didn't update the status correctly.

aiidalab_1  | [I 09:55:37.943 NotebookApp] Serving notebooks from local directory: /home/aiida
aiidalab_1  | [I 09:55:37.943 NotebookApp] Jupyter Notebook 6.4.12 is running at:
aiidalab_1  | [I 09:55:37.943 NotebookApp] http://d575c7afef91:8888/?token=76b6b1699e1a771af4deb69056d6404d56aa547363c50cf7
aiidalab_1  | [I 09:55:37.943 NotebookApp]  or http://127.0.0.1:8888/?token=76b6b1699e1a771af4deb69056d6404d56aa547363c50cf7
aiidalab_1  | [I 09:55:37.943 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
aiidalab_1  | [C 09:55:37.946 NotebookApp] 
aiidalab_1  |     
aiidalab_1  |     To access the notebook, open this file in a browser:
aiidalab_1  |         file:///home/aiida/.local/share/jupyter/runtime/nbserver-560-open.html
aiidalab_1  |     Or copy and paste one of these URLs:
aiidalab_1  |         http://d575c7afef91:8888/?token=76b6b1699e1a771af4deb69056d6404d56aa547363c50cf7
aiidalab_1  |      or http://127.0.0.1:8888/?token=76b6b1699e1a771af4deb69056d6404d56aa547363c50cf7

[danielhollas]

Well, first please update aiidalab-launch with pipx upgrade aiidalab-launch, as the message says.

Secondly, can he actually reach the notebook on 8888/?token=76b6b1699e1a771af4deb69056d6404d56aa547363c50cf7?

I don't remember how it was done in the old stack, but perhaps the container lifetime is not tied to the jupyter notebook. So the notebook could have died, but the container keeps running. This would explain the exited status that aiidalab-launch reports.

Thirdly, what is the output of verdi status inside the container? Also, I think we need the whole output of aiidalab-launch logs -p aurora. (are we talking about the default profile or aurora profile. We also need output of aiidalab-launch profiles show <profile>