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.

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 timestamped log entries from your server.
  3. 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", your server may not have started far enough to produce any output. Try starting it again and check the logs after a few seconds.
  • If you cannot resolve the issue yourself, include the log output when contacting support, it helps us help you faster.