This is an old revision of the document!


Helpdesker's Guide to the Foundry

User Access Requests

Students requesting access to the Foundry should be added to it-foundry-general This will trigger an email to be sent to their UM email account with links to the user documentation and a form that they must fill out before they will be able to use the Foundry. Do not put students or faculty in it-foundry-access this group is for a distribution list for external access requests.

Faculty members may also be added when requested. For general information regarding what we offer to Faculty above general access please reference the Foundry information page.

User group management

If a faculty member or department decides to go with a priority queue on specific hardware they get their own netgroup, which they may add whoever they wish. Please see the table below for valid netgroups and the administrative entity on the account. Please note you must get authorization from the administrative entity to add a student to a netgroup other than forge-cluster-general.

NetgroupAdministratorAdmin EmailDetails
it-foundry-sgaoStephen Gaosgao@mst.eduPurpose built node access
it-foundry-dawesrRichard Dawesdawesr@mst.eduPurpose built node access
it-foundry-hosdersSerhat Hosderhosders@mst.eduPurpose built node access
it-foundry-vasp-5many usersbefore granting access proof of license is requiredVasp version 5 software access, license are version specific
it-foundry-medvedevaJulia Medvedevajuliaem@mst.eduPurpose built node access
it-foundry-vojtatThomas Vojtavojtat@mst.eduPurpose built node access

Software Installations

All software requests should be sent to Research Support's queue

Connection problem troubleshooting

  1. Make sure user is on campus and is trying to connect to foundry.mst.edu, if user is off campus they need to either be using public key authentication or be connected to the campus VPN.
  2. If the user can't use the VPN please direct them to our instructions for public key auth in the user documentation under logging in.
  3. Make sure to reference the connection documentation at the Foundry user documentation to insure the user is using the correct settings.
  4. Make sure the user is in it-foundry-general, ask them if they have received the account activation email.
  5. make sure the user isn't using the UM-AD prefix to log in.

Job Errors

“sbatch: error: Batch job submission failed: Invalid account or account/partition combination specified” This error is commonly caused because the user's account has not been activated yet, this is usually because they haven't followed the instructions in their welcome email asking them to fill out our new user form. Provide them with the link to the form and remind them they must sign in with their @umsystem.edu google account, sometimes that requires them to open the form in an incognito window to get google forms to prompt them to sign in. New User Form

A lot of times the user simply doesn't understand the error message. Simple submission errors are usually self explanatory. Errors like “more processors requested than permitted” simply means that for one reason or another the resource manager can't meet the processor requirement for the job, usually a look at the users job file can provide answers as to what is going wrong. Software errors are a bit more software specific, these will usually require a bit of investigation based on what the software title is. If it hasn't been addressed in the Foundry user documentation, or can't specifically be found by a quick google search please assign a ticket to IT Research Support.