Troubleshooting

Last updated: July 31, 2026Latest Frontend Version:

Common issues administrators may run into, and how to resolve them.

User stuck in pending state

• Confirm the user has completed the account activation workflow (email verification and key registration). See Onboarding.
• Check the escrow status for the user's key; a pending escrow approval will block activation.
• Confirm an administrator has approved the account if your institution requires manual approval.
• If the user remains stuck after these checks, review the audit log for activation errors.

Slurm job won't start

• Check that worker VMs are available and not all in use. See Slurm Configuration.
• Confirm the target compute node is enabled and not in a "Do Not Schedule" or disabled state.
• Verify the job's resource request does not exceed what any available worker VM can provide.
• If the job still won't start, check the Slurm controller logs for scheduling errors.

Storage pool full

• Review libvirt volumes to identify which images or drives are consuming the most space.
• Clean up old or unused VM images and orphaned volumes.
• Confirm no stale snapshots are retained from past VM sessions.
• If space remains constrained, expand the underlying storage pool or add an additional pool.