Launcher Troubleshooting

Workbench

The /status endpoint of the Job Launcher can be used to get the current health status and other connection information. Unlike other Job Launcher endpoints, this endpoint does not require authorization and may be queried by any monitoring or load balancing software to determine the health of a specific Job Launcher node.

The status field indicates whether a node is experiencing:

It is recommended that you reroute traffic to another launcher node if you receive a “Yellow” or “Red” status, or if the page fails to load.

If additional is troubleshooting is needed, please follow the troubleshooting steps outlined below.

Title Category Description
Step 1. Check the log files Log files & diagnostic tools Inspect the content of the RStudio Server Pro service, the Launcher service, the Kubernetes plugin, and individual sessions log files.
Step 2. Verify Installation Log files & diagnostic tools Run the verification process and identify any configuration issues in your environment.
Step 3. Check Service Status Launcher configuration issues You’re unable to access the Workbench home page unable to start new remote sessions in Kubernetes.
Step 4. Verify License Status Launcher configuration issues Verify that your license is authorized to use Launcher.
Step 5. Verify that clocks between the rserver node and Kubernetes cluster’s clocks are synced Launcher configuration issues You’re unable to start new remote sessions in Kubernetes.
Step 6. Verify Configuration Files Launcher configuration issues You’re unable to access the Workbench home page and/or unable to start new remote sessions in Kubernetes.
Step 7. Skip Certificate Verification Kubernetes plugin configuration issues You’re unable to start new remote sessions in Kubernetes.
Step 8. Verify Certificate Configuration Kubernetes plugin configuration issues You’re unable to start new remote sessions in Kubernetes.
Step 9. Verify Kubernetes Certificate Configuration Kubernetes plugin configuration issues You’re unable to start new remote sessions in Kubernetes.
Step 10. Verify Kubernetes Token Configuration Kubernetes plugin configuration issues You’re unable to start new remote sessions in Kubernetes.
Step 11. Verify Kubernetes API Access Kubernetes configuration and environment issues You’re unable to start new remote sessions in Kubernetes.
Step 12. Verify Docker Image Configuration and Access Kubernetes configuration and environment issues New remote sessions in Kubernetes appear to start, but are stuck in PENDING status.
Step 13. Verify Kubernetes Worker Nodes Kubernetes configuration and environment issues New remote sessions in Kubernetes appear to start, but are stuck in PENDING status.
Step 14. Verify Kubernetes Worker Node Resources Kubernetes configuration and environment issues New remote sessions in Kubernetes appear to start, but are stuck in PENDING status.
Step 15. Verify NFS Server Configuration Kubernetes configuration and environment issues New remote sessions in Kubernetes appear to start, but are stuck in PENDING status.
Step 16. Verify NFS Server Connectivity Kubernetes configuration and environment issues New remote sessions in Kubernetes appear to start, but are stuck in PENDING status.
No matching items
Back to top