Skip to content

Log Viewer

When your server starts, you are taken to a loading screen that shows the progress of the startup. At the bottom of this screen, you will find a link to your server logs.

Server spawn progress screen

The loading screen showing server startup progress with a link to the logs at the bottom.

If your server fails to start or takes longer than expected, clicking the logs link opens a page with detailed log messages from your server. These logs can help you understand what went wrong. For example, whether the server ran out of memory, encountered a storage issue, or failed to pull the selected notebook image.

The logs page updates automatically every 10 seconds, so you do not need to refresh the browser page manually.

How to use it

  1. On the loading screen, look for the message at the bottom: "If you have a problem with your server, you can check your logs for more information."
  2. Click the logs link. A new page opens showing recent log entries from your server pod.
  3. The logs page updates automatically every 10 seconds, so you do not need to refresh it manually.
  4. The newest logs are shown at the bottom. By default, the page automatically scrolls to the latest log entry.
  5. If you want to inspect older logs, uncheck "Auto-scroll to latest log".
  6. At the top of the page, you will find your username and the server pod name. Please include the server pod name when contacting support.
  7. Look for lines containing ERROR or Warning that might explain the issue. Some log lines are infrastructure-level and can be safely ignored.

Common issues you can identify

  • Image pull errors: The selected notebook image could not be downloaded. Try again later or choose a different image.
  • Storage issues: Your home directory may be full. Free up space and try again. For this specific issue, you can use the Rescue mode
  • Resource limits: The server could not be scheduled due to insufficient resources. If available on the spawn page, try selecting fewer CPUs or less memory.

Good to know

  • Logs cover the last 50 minutes, so they are available even if your server has already stopped.
  • If the logs page shows "No logs found for this pod in the selected time window", your server may not have started far enough to produce output. Try starting it again and check the logs after a few seconds.
  • If the logs page shows "Could not query the log backend", the logs may currently be unavailable. This does not necessarily mean your server produced no logs.
  • If you cannot resolve the issue yourself, include the server pod name and relevant log output when contacting support. This helps us help you faster.