HPC/FAQ

Login issues

When you ask "I cannot log in" or "My password does not work", consider the following sections:

Review host names

Make sure you connect to the correct host name, which is mega.cnm.anl.gov for the SSH gateway and carbon.cnm.anl.gov when connecting from an onsite work computer or over VPN. The previous name for the latter was clogin.cnm.anl.gov and will continue to work. -- See HPC/Network Access.

Verify your password

Visit https://credentials.anl.gov/ and verify that your username and password are correct.

Review User requirements

To access Carbon under the CNM User Program, a number of items are required, most of which are subject to an expiration date and require periodic renewal. I recommend that you set calendar entries about one year into the future to remind yourself to renew any of the items below.

• Review and update your User Registration.

  Your Argonne computer account will be disabled upon expiration of certain registration items. In particular, if you are not a US citizen, you will require a current US visa or related work permit to access Argonne computers, just as if you were to visit in person. This will very likely happen in the middle of your proposal's lifetime. No notice is being sent to you for a number of reasons, and you will suddenly find that you can no longer access mega.

  After you updated your user registration, contact the CNM User Office to have your Argonne account re-instated.

• Renew your User Courses.

  For remote users, the ESH223 course "Cybersecurity Annual Education and Awareness" is the one most likely in need of renewal.

• You must be a participant in at least one active or recently expired User Proposal.

  To review dates for your proposal, ask your PI to search their email archive for mails with "Work Approval Received" or "Proposal Expiration" in the subject.

  Compute jobs may be run while a proposal (specifically, a user work authorization) is active. For at least 30 days thereafter, users are entitled to data access only, following CNM's Data Retention Policy.

  It may take several hours to set up or renew user access under a given proposal on mega.

• Access to mega requires that the User Work Submittal for a proposal contain your badge number.

  This is a more arcane technical issue. If your badge number was left empty at the original submission of the UWS (typically when you are a newly registered user), ask the CNM User Office or your Scientific Contact to augment and resubmit the form.

Request a password reset

• To have your password reset, email the CNM User Office, at [email protected].
• When you connect to mega with still your temporary password in place, mega will ask for a new password. You can safely change your password at this point.
• You can also change your password at https://credentials.anl.gov/ - However, a change there will take a few hours to become active on mega.

Review instructions

• Read again HPC/Network Access, and follow the instructions for your platform.

To request support

Send your support request to NST IT help desk:

[email protected].

Before you hit "Send", check the following aspects of your message:

• Choose an appropriate subject line.

  Do not merely hit "Reply" on a previous unrelated message - doing so might cause the request to get lost or ignored.

• Be as specific as possible in the body of your message. Include the following:
  • The command you were trying to run or the menu item you chose.
  • The exact error message you get. Copy & Paste the message text, or take a screenshot and attach it to your mail.
  • The path and file name of relevant files. It is generally not necessary to include copies of files that reside on Carbon.
• For PBS jobs:
  • The job number.
  • The working directory of the job.
• For remote access issues, include the following:
  • The host name you ran the command on (generally shown in the command prompt).
  • The hostname you're trying to reach.
  • The username you use to connect.
  • The software name and version you use to connect (e.g. SSH, VNC, or a browser).
  • Your operating system and version.
• Review your subject line before you submit the message.

Receiving support

When you get our support response:

• Carefully read it.
• Follow all instructions and answer all questions.
• For account- and password-related issues: it may take several hours for changes to take effect. If your initial attempt fails, wait at least that long before retrying.

Additional considerations

To help us diagnose a problem:

• Read How to Report Bugs Effectively, by Simon Tatham, programmer.
• For deeper reading, consider How To Ask Questions The Smart Way, by Eric S. Raymond, open source pioneer.

I'd like to use application X

Check if the application is already available on Carbon

Either:

• Browse the Application Catalog, or
• View the catalog on the Carbon command line:

module avail
module -l avail 2>&1 | less

The second form gives you browsable output.

If you cannot find the application on Carbon

1. Describe the problem you are trying to solve – it may well be that we can suggest an alternative solution.
2. Provide one or more URLs relevant to software you have in mind – be specific.

How do I run application X?

• Customize your shell environment to load the application module.
• Learn about module conventions on Carbon.
• To determine the names of a package's executable scripts and binaries, inspect its $NAME_HOME/bin directory. For instance, for the Quantum-ESPRESSO package:

ls $QUANTUM_ESPRESSO_HOME/bin

How do I use application X?

Read the package's documentation, using one or more of the following:

• Inspect the package's $NAME_HOME/share or $NAME_HOME/doc directory on Carbon (see module conventions).
• Browse the package's web page, generally mentioned in the module help text or the application catalog entry.
• Consult a package's man pages. Few packages have them. Man page files are generally installed under $NAME_HOME/man or $NAME_HOME/share/man and if so, will be made available automatically to the man command.

What's my account balance?

Simple answer: mybalance

To find out how many core-hours you have available, the simplest command to run is:

mybalance -h

Project  Machines Balance    
-------- -------- ---------- 
user     ANY         993.26
cnm34567 ANY       158760.93
cnm31234 ANY      -148893.62

The table gives all the Projects you have access to (for use with the qsub -A argument), and their balance. Machine lists all systems that can book jobs against your allocations. Carbon is currently the only machine that can do so. Balance is your account balance, in core-hours, as selected by the -h command option. This is the most useful and recommended unit. Without -h, you get core-seconds, which are integers but rather more unwieldy numbers.

• The "user" project provides you with a small initial startup allocation of typically 1000 core-hours.
• When a Balance is reported as negative, that account typically has a CreditLimit assigned, which permits the balance to dip below zero. These details, however, are not shown by mybalance.

Complete answer: gbalance

To get allocation details for accounts that have CreditLimits, run the gbalance command. Pass on -u username or -p projectname to select your allocations:

gbalance -h -u $USER

Use the literal string $USER which makes the shell fill in your actual username.

The ouput looks like:

Id  Name     Amount     Reserved Balance    CreditLimit Available
--- -------- ---------- -------- ---------- ----------- --------- 
100 cnm31234 -148893.62     0.00 -148893.62   150000.00   1106.38
217 kpelzer      993.26     0.00     993.26        0.00    993.26 
123 cnm34567  166440.93  7680.00  158760.93        0.00 158760.93 

The most relevant column for you is Available. The units, given the -h option, are again core-hours.

The colums and their meanings are:

Id

an internal number for the account.

Name

The project name (for use with qsub -A or #PBS -A).

Amount

Amount for transactions completely on the books for the project account; does not include running jobs or credits. Deposits are allocated by the User Office and implemented by the Carbon administrator.

Reserved

Amounts held in reserve by all running jobs using this account. The reserve ensures that a job does not cause an overdraft when it finishes and when its actual use will be booked. The quantity is calculated by walltime * number of cores blocked. When a job terminates, the charge according to the actual time used will be subtracted from Amount, and the unused quantities will be re-added to Amount.

Balance

Available for new jobs; may go negative if CreditLimits are in place.

Balance = Amount - Reserved

CreditLimit

Amount by which Balance may go negative; assigned by the Carbon administrator.

Available

Relevant quantity for new jobs. Must be positive for a new job to start, and large enough to Reserve the entire job.

Available = Balance + CreditLimit