I’m trying to use the ARE-JupyterLab on gadi - a regular occurrence and one that usually presents no issues.
This morning (19/12/2025) it’s throwing an exit code 135 error - and looking at the debug log it’s giving
Loading conda/analysis3-25.11
Loading requirement: singularity
/home/599/inh599/ondemand/data/sys/dashboard/batch_connect/sys/jupyter/ncigadi/output/1e110a82-b3b1-42c0-be69-81b78789b0d8/script.sh: line 73: /g/data/xp65/public/modules/bin/activate: No such file or directory
/g/data/xp65/public/apps/med_conda_scripts/analysis3-25.11.d/bin/jupyter
/g/data/xp65/public/apps/med_conda_scripts/analysis3-25.11.d/bin/jupyter
which seems to indicate that it can’t find one of the NRI hosted conda environment files.
Could you provide any advice?
I’m using /g/data/xp65/public/modules as a module directory and python virtual environment base, and conda/analysis3 in the modules line when starting jupyterlab
Using /g/data/x65/public as the module directory allows the JupyterLab to start but then didn’t pick up any analysis3 conda environments (notably access to xarray).
Using /g/data/x65/public /g/data/xp65/public/modules on the module directory line appears to have worked.
Yes, you do need to include the /modules directory in your path on the module directory line, and you don’t need to include the path without /modules at all.
In case it’s helpful, the full instructions for using the xp65 conda environment with ARE JupyterLab can be found here: conda/analysis3 Python Environment - ACCESS-Hive Docs (screenshot of the relevant part below).
My initial problem was that using /g/data/xp65/public/modules alone wasn’t able to start the JupyterLab - and gave the exit code above. This is how I’ve usually done things so I was a surprised when it didn’t work this morning.
Possibly something on gadi wasn’t picking up the simlink?
Ah sorry @inh599 - I misunderstood. I thought you initially tried /g/data/x65/public and then it didn’t work, but I see that that was one of your attempts to find a solution. My apologies!
We’ve got @CharlesTurner digging into this for you. Glad you found a work-around for now, and we will post any updates here.
Might be an unrelated issue at this point, but seeing as you can get into a jupyterlab session but no kernels are showing up, can you try running rm -r ~/.local/share/jupyter/kernels.
I’ve personally had a few instances where this directory has caused issues like this for me, deleting it should fix the problem in most cases. Not 100% sure it will in this one unfortunately, but well worth a crack.
Hi - I got a combination of settings when starting the ARE-jupyter labs that worked back in December - see the work around given above - and didn’t go back to identify the core problem.
I haven’t had any further instances of the issue - but haven’t used the ARE that much to be honest since December and I am likely still using the work around.
