This is likely due to some recent python package installation in your
$HOME/.local directory. You could try to rename your $HOME/.local to
$HOME/OLD.local on the cluster with:
# log into Hoffman2 via a terminal and SSH and issue at the cluster command prompt or
# open a terminal from a jupyter notebook session:
mv $HOME/.local $HOME/OLD.local
and see if you can again open a jupyter notebook. We would then need to understand which package caused the issue.
One way to go to prevent compromising your ability to start jupyter
notebook is to install packages in virtual environments, for example,
if you are using python/3.9.6:
# log into Hoffman2 via a terminal and SSH and issue at the cluster command prompt or
# open a terminal from a jupyter notebook session:
qrsh -l h_data=5G
module load python/3.9.6
mkdir $HOME/.venv
python -m venv $HOME/.venv/MYENV-3.9.6
source $HOME/.venv/MYENV-3.9.6/bin/activate
# install the ipykernl into this environment:
pip install ipykernel
python -m ipykernel install --user --name=MYENV-3.9.6 --display-name "MYENV-3.9.6"
# install any other needed package
# pip install ...
# IF INSTALLING ANY PACKAGE THAT WILL PULL IN urllib3 YOU WILL NEED TO DOWNGRADE:
# python3 -m pip install urllib3==1.26.1
Now when you open a new notebook you should be seeing in the list
of possible kernels your newly created "MYENV-3.9.6" python virtual
environment which you could go ahead and select.