Jupyterhub Ubuntu 24

Hallo, I’m new here. I set up jupyterhub on a local server for our lab more than a year agon on ubuntu 22 LTS. I followed the instructions on
github “jupyterhub-the-hard-way”, which worked out of the box. However - last week we upgraded the server to Ubuntu 24 LTS, set up RStudio again (which works) and tried to set up Jupyterhub again. Most things survived the system udate (folders and links created during initial install, now not a clean install of ubuntu 24 but upgrade by “do-release-upgrade”) but now I’m not able to start the jupyterhub service. If I understand the output of systemd status right, there may be a conflict in the database version. I’m not able to run ‘jupyterhub upgrade-db’ because the daemon is not running… I attached a screenshot. Can you help me please? How can I resolve this?
Best, Christian

It sounds like your python environment isn’t correctly setup when using sudo. Try starting a shell as the correct user, and if necessary set any environment variables that are set in your systemd file, before running the database upgrade.

Hi,
thank you for the reply. I manged to get jupyterhub service running by renaming the database file. The service is running now and a new database present. But it seems I messed up authentication settings, because I can’t log in now. The system users are not recognized anymore. Jupyterhub service is running as root, when I use “sudo systemctl show -pUser jupyterhub.service” I get “User=root”.
Maybe reboot?

Can you turn on debug logging, and share your JupyterHub logs?

I used journalctl to look into the logs yesterday and it seems I messed up my python installation and still have issues with spawn / pam. I’m able to login but the server doesn’t start. Maybe now it’s a good time for a clean install since I also have minor issues with rstudio server.

After a fresh install I followed

However - I had to set
c.Authenticator.allow_all = True
in jupyterhub_config.py, otherwise I was not able to login. I always got pam authentication failures. I can now log in and pyhton kernel starts.