500: Internal Server Error

Currently, we cannot fully locate this issue, but we are in contact with the ZIH.

It appears to be an issue with the initialization through prepared configuration. Once you see this issue, any further attempt to start the server through the spawn link will fail.

Background Here's a little bit more background on what happens if you click on the spawn link.
  • The spawn link provides several configuration parameters
  • These will be used to start your server
  • Among those are Number of CPUs, Memory, but also the project reference
  • and a link to a Gitlab Repository that is cloned to local user space on startup
  • Without this repository, you will not have no notebooks in your jupyter lab instance
  • Under certain circumstances, this setup-link fails,
  • and it leaves the environment in a broken state, preventing any further startups

Workaround

One workaround is to "spawn" the server with default configurations, shut it down afterwards and click the spawn link again.

Follow the steps below.

1. On the screen where it says "500: Internal Server Error"

  • go to Home
  • Click on the Blue Button that says "Start my Server"

2. You'll get to the manual configuration screen. Select the following:

  • Advanced
  • Enter p_lv_mobicart_2021 in Project (-A, --account) field
  • Select 2 CPU in CPUs per task (-c, --cpus-per-task)
  • Click on "Spawn"

3. Wait until the server started, and shut it down afterwards

  • the explorer/files will be empty because no repsitory has been cloned on startup
  • However, after you shut down this server, the spawn link should work again
  • to shutdown the server, click on File / Shut Down in Jupyter and on the next page click on "Stop my Server"
  • you should not see "500: Internal Server Error" this time
  • if it appears again, the process above must be repeated

IOER RDC Jupyter Base Template v0.11.0