Getting help¶

Problem: When a cluster is attached, nextPYP streams information from SLURM through and HTTP-socket connection. If the connection is dropped, the information will not longer be updated on the web page. When this happens, the icon will appear at the top of the page.

Solution: Click the icon and select Reconnect. The icon should then change into , indicating that the connection has been reestablished.

Problem: The Jobs panel shows that processes are running (spinning cogs) even after processing has finished.

Solution: Cancel the jobs using the red button in the jobs panel. If the problem persist, consult the troubleshooting section and report any problems using the Github’s discussion board.

Problem: When the menu option to Navigate to latest logs on a block is selected, the following toast message appears: No logs to highlight, job run is too old.

Solution: Go to the Jobs panel, open the Older branch and click on Load older runs. If you go back and select the Navigate to latest logs option, the correct log should be highlighted.

Problem: This can be caused by the JVM running out of memory. You may see the following error message: 502 Proxy Error. The proxy server received an invalid response from an upstream server. The proxy server could not handle the request. Reason: Error reading from remote server., and the server log may show the error: Caused by: java.lang.OutOfMemoryError: Java heap space.

Solution: Increase the memory of the JVM to 8192 MB by adding the option heapMiB = 8192 to the config.toml configuration file in the [web] section. Restart nextPYP for the changes to take effect.

Problem: Website components are missing, pages don’t load properly, etc.

Solution: We are not sure what could cause this, but here are a few things you can try: 1) reload the page, 2) clear your browser’s cache, 3) update your browser, or 4) try using a different browser.