Support | Datahub & PARASOL Documentation

Contacts

Who to Ask

Start with the contact for your topic. Students in a course should ask their instructor or TA first.

A course you are enrolled in

Your instructor or TA, first.

PARASOL or Datahub itself

Access, images, launching, and quotas.

Research work, or Universal Scale Storage

Which platform suits a research project

One-on-one consultation

For instructors, TAs, and Technical Points of Contact.

A whole class is affected

Escalate a problem that affects a whole class or more than one person through the ITS Service Desk. Say what is affected and how many people it affects. See Incidents Affecting More Than One Person and Response Targets.

Before you contact support

Many problems have a documented fix. These pages cover the ones people report most.

Missing courses, "Spawn failed", a full disk quota, a busy cluster, and the manual resetter.

Launch errors, pod statuses, booking refusals, and CUDA out-of-memory errors.

Runtime limits, idle culling, missed reservations, and preemption.

Check the Datahub status page to see whether the cluster is busy before you report a slow start.

Writing a ticket

A ticket that names the workspace, the time, and the exact message is usually resolved without a follow-up question.

The course or workspace, by name or ID
Where you were working, Datahub in a browser or dsmlp-login at a terminal, and the environment you chose
The exact command and error, copied with a screenshot
Roughly when it happened, and whether it happens every time

Contents of a Support Ticket has the full list. Some behavior is expected and not a fault. See Expected Behaviors Reported as Faults.