This page contains frequently asked questions. If users have any trouble, questions, concerns, or suggestions, feel free to contact ARCC.
Contents
General ARCC Troubleshooting
For general issues please see our Known Issues page to see if the problem could be caused by something that we already are aware of and recommended solutions or work arounds.
General Problems
Questions Related to Migration: Beartooth to MedicineBow
I’m having trouble logging into Medicinebow OnDemand
Please reference the ARCC Login Page and how to log in here.
I’m having trouble SSH’ing to Medicinebow
New users trying to ssh for the first time without configuring SSH authentication will recieve an error message as follows: ssh <username>@medicinebow.arcc.uwyo.edu: Permission denied (publickey)
ARCC has changed the way users authenticate over SSH to Medicinebow and authentication must be configured with SSH keys. See this page on configuring SSH keys to SSH into Medicinebow.
How do I move my data from Beartooth to Medicinebow?
The easiest method for moving data from Beartooth to Medicinebow is to use Globus. Instructions for logging into and configuring Globus and moving data between Beartooth and Medicinebow may be found here.
Alternative methods for moving data are detailed here.
Questions Related to Migration: Alcova to ARCC Data Portal Migration
I can’t access my alcova data post migration.
What is the location in which you’re attempting to access your data? If you’re accessing data at: alcova.arcc.uwyo.edu\<projectname> this was the prior location for Alcova data. Alcova projects were migrated effective June 2024 to data.arcc.uwyo.edu\cluster\alcova\<projectname> and users should access data at the new location.
If you are attempting to access your data at the new location and unable to get to it, this may be dependent on your network configuration. If you’re off campus you must connect to the UWYO network using Wyosecure VPN. Information for Wyosecure is available here.
If you’ve attempted to access the new alcova location and are connected to Wyosecure, but are still unable to do so, please contact arcc-help@uwyo.edu for assistance.
Beartooth
I am no longer able to access Beartooth when I could previously
Beartooth is scheduled for end of life/decommission effective January 2, 2025. Users should no longer be able to access Beartooth after this date.
Users with old projects on Beartooth should migrate to Medicinebow. Migration Request forms may be filled out for projects here, on our portal.
How do I access Beartooth when I am not on the UWyo network?
Beartooth's login nodes are on the Science DMZ network outside of UWyo firewalls. Meaning you can log into Beartooth from anywhere as long as you have an internet connection and a terminal or ssh client.
How do I run my code on Beartooth?
You must submit your code to the job scheduler. Running code on login nodes is not permitted.
For more information about the job scheduler please see our page on Slurm.
How do I find out which software packages are installed/available on Beartooth?
While logged into Beartooth, executing the command "module spider" will list all modules installed on Beartooth.
$ module spider To learn more about a package execute: $ module spider Foo where "Foo" is the name of a module. To find detailed information about a particular package you must specify the version if there is more than one version: $ module spider Foo/11.1
Alcova
I can’t access my alcova data at alcova.arcc.uwyo.edu/<projectname>
Alcova was migrated to the ARCC Data Portal effective June 2024. Please see this page for information on accessing the your new project space.
How do I access my Alcova allocation when I am not on the UWyo network?
Users will need to use the UWyo VPN (wyosecure) to get onto the UWyo network.