uabrc.github.io
uabrc.github.io copied to clipboard
Rework account page
What would you like to see added?
Who can access Research Computing systems?
UAB Employees and Students
- Must have an active BlazerID
- Includes UAB Campus and UAB Medicine
- Includes Faculty, Staff, Postdocs, and Graduate Students
- Undergraduate student access is not available, apologies for any inconvenience.
- (link to broken-out page)
External Collaborators
- Must be sponsored by a UAB Employee.
- The sponsor assumes responsibility for any actions taken by the External collaborator on UAB systems.
- (link to XIAS index)
What are my responsibilities?
- Be aware of and perform account holder responsibilities: #541
How do I create a Research Computing account?
Cheaha
- UAB Employees and Students: (break out page, put link here)
- External Collaborators: (https://apps.idm.uab.edu/xias/top)
Gitlab
- UAB Employees and Students: (link to page)
- External Collaborators: (link to page)
Cloud.rc
- UAB Employees and Students: (link to page)
- External Collaborators: (link to page)
How do I login to Research Computing Services?
Cheaha
- Duo (for Open OnDemand)
- UAB Employees and Students: BlazerID
- External Collaborators: XIAS
Gitlab
- UAB Employees and Students: (link)
- External Collaborators: (link)
Cloud.rc
- Duo + VPN
- UAB Employees and Students: (link)
- External Collaborators: (link)
Important Links
- Duo (https://www.uab.edu/it/home/security/2-factor)
- VPN (requires Duo) (https://www.uab.edu/it/home/tech-solutions/network/vpn)
As part of this, let's build out a troubleshooting guide of common known issues, and what to do about them. The application is robust and, as I understand, idempotent, so errors will most often occur because our platform is having general issues with connections, or because a piece is missing.
Below are FAQs for the self-service Cheaha account creation.
- Which credentials should I use? Please see (new section above) for more information.
- What do I do if I'm waiting for it to finish for longer than a couple of minutes?
- Try closing and restarting your browser, then trying again.
- Try clearing site data for https://rc.uab.edu, then trying again.
- Try logging in on a Private Browsing window, then trying again.
- Try waiting a few hours, then trying again.
If all else fails, please (contact support link).
Perhaps the following should be a Github issue by itself, but starting the convo here as it relates to the troubleshooting comment above. Here's a recent comment added to a support ticket:
In order to pick up the new group membership they will have to do the following because they currently are SSH'd into Cheaha and have an active Open OnDemand session via https://rc.uab.edu :
- Exit out of any SSH connections they have to cheaha.rc.uab.edu and log back in
- In Open OnDemand (https://rc.uab.edu) Click the <Develop> menu in the upper right corner, then click Restart Web Server
- Restart any OnDemand virtual desktops
Q: What does a user need to do when added to a group on Cheaha? A:
- Do they have any processes / connections on cheaha.rc.uab.edu?
- If they have active SSH sessions, they will need to exit out and log back in
- Additional complication, if they have active Tmux/Screen sessions, they will need to terminate those, log out, log back in and start Tmux. This can be painful but can be helped with Tmux plugins that continually save the Tmux session state and allow it to be restored.
I use a combo of the following 2 plugins. However, I found a more modern Tmux Session Manager, TmuxP that I may switch to TmuxP HowTo - Tmux Resurrect - Continuum
- Do they have an active Open OnDemand session?
- In Open OnDemand (https://rc.uab.edu) Click the <Develop> menu in the upper right corner, then click Restart Web Server
- Do they have one or more OOD HPC Desktops running?
- Terminate the desktops and start new ones