Known issues

From CC Doc
Revision as of 21:41, 27 November 2017 by Mboisson (talk | contribs)

Jump to: navigation, search
Other languages:
English • ‎français

Report an issue

Shared issues

Scheduler issues

  • The CC Slurm configuration encourages whole-node jobs. When appropriate, users should request whole-node rather than per-core resources. See Job Scheduling - Whole Node Scheduling.
  • By default, the job receives environment settings from the submitting shell. This can lead to irreproducible results if it's not what you expect. To force the job to run with a fresh-like login environment, you can submit with --export=none or add #SBATCH --export=NONE to your job script.

Quota and filesystem problems

Quota errors on /project filesystem


Missing symbolic links to project folders

Cedar only

Nothing to report at this time.

Graham only

  • /home is on an NFS appliance that does not support ACLs, so setfacl/getfacl doesn't work there.
    • Workaround: use the /project or /scratch filesystems instead.
    • Might be resolved by an update or reconfiguration.
  • diskusage_report (and alias 'quota') do not report on Graham /home (FIXED as of 2017-11-27)
  • Compute nodes cannot access Internet
    • Solution: Contact technical support to request exceptions to be made; describe what you need to access and why.
  • Crontab is not offered on Graham.

Other issues

  1. Modules don't work for shells other than bash(sh) and tcsh.
    • Workaround: (this appears to work but not tested extensively)
      • source $LMOD_PKG/init/zsh
      • source $LMOD_PKG/init/ksh