Troubleshooting and Debugging
Troubleshooting
If you’re having issues with your ICRN JupyterLab environment, try these basic troubleshooting steps first. If the issue persists, submit a support request and NCSA staff will work to help you resolve it.
“0/<X> Nodes are Available” Error
As your server is starting, if you receive an error message that includes “0/<X> nodes are available”, the associated system node(s) have reached capacity. There are two options to resolve this:
Try again later. Once a node is below capacity, you will be able to start your server.
Try a different server. You may be able to start one of the other server options if the associated system node(s) have available capacity.
The system administrators monitor system utilization and advocate for increases in system capacity as utilization dictates. If you are consistently unable to log into the system due to node availability, please submit a support request.
How to Stop Your Server
If your code is acting in an unexpected way, the first troubleshooting step to try is to stop and re-start your server.
Warning
This will stop any processes running in your JupyterLab environment.
In the File menu, select Hub Control Panel.
Click Stop My Server.
Click Start My Server. This will redirect you to the server options list.
Select a server and click Start to re-enter your JupyterLab environment.
How to Uninstall a Recently Installed Extension
If you recently installed an extension (see Extensions) prior to experiencing issues with your code, uninstall the extension to see if that resolves the issue.
Click on the Extension Manager (puzzle piece) icon.
Open the INSTALLED pane in the extension manager.
Find your recently installed extension in the list and click Uninstall.
Refresh your webpage when prompted.
Warning
This will stop any processes running in your JupyterLab environment.
How to Access Built-in Help Tools
Python and R have built-in help commands that you can use to learn more about other commands. To access help, enter help()
in a console or notebook and follow the prompts.
The Help menu in the JupyterLab environment also includes Jupyter, Python, and Markdown references.
Debugging
This section includes information to help debug common code issues that ICRN users have. If the issue persists, submit a support request and NCSA staff will work to help you resolve it.
“The kernel for <>.ipynb appears to have died. It will restart automatically.”
If Python code in your notebook returns this error, copy the code to a Terminal and run it there as a script.
Notebooks are limited to 8GB of memory. If your notebook uses more memory than that, this is the error message you will see. Running the code in a terminal will return more informative error messages to help you diagnose the issue and/or confirm it’s a memory usage issue.