Known issues/en: Difference between revisions
Jump to navigation
Jump to search
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 7: | Line 7: | ||
== Scheduler issues == | == Scheduler issues == | ||
* Interactive jobs started via <tt>salloc</tt> do not support X11 forwarding. (''reported 13 December 2017 18: | * Interactive jobs started via <tt>salloc</tt> do not support X11 forwarding. (''reported 13 December 2017 18:37 UTC'') | ||
* The CC Slurm configuration encourages whole-node jobs. When appropriate, users should request whole-node rather than per-core resources. See [[Job_scheduling_policies#Whole_nodes_versus_cores;|Job Scheduling - Whole Node Scheduling]]. | * The CC Slurm configuration encourages whole-node jobs. When appropriate, users should request whole-node rather than per-core resources. See [[Job_scheduling_policies#Whole_nodes_versus_cores;|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 <tt>--export=none</tt> or add <tt>#SBATCH --export=NONE</tt> to your job script. | * 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 <tt>--export=none</tt> or add <tt>#SBATCH --export=NONE</tt> to your job script. | ||
Revision as of 19:35, 13 December 2017
Report an issue
- Please report issues to the technical support team.
- The status page at http://status.computecanada.ca/ is not updated automatically yet, so may lag in showing current status.
Scheduler issues
- Interactive jobs started via salloc do not support X11 forwarding. (reported 13 December 2017 18:37 UTC)
- 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
- This topic has been moved to Frequently Asked Questions.
Nearline
- Nearline capabilities are not yet available; see https://docs.computecanada.ca/wiki/National_Data_Cyberinfrastructure for a brief description of the intended functionality.
- July 17 update: still not working. If you need your nearline RAC2017 quota, contact technical support.
Missing symbolic links to project folders
- Upon login to the new clusters, symbolic links are not always created in the user's account, as described in Project layout. If this is the case, please verify that your access to the cluster is enabled on this page https://ccdb.computecanada.ca/services/resources.
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. (FIXED as of 2017-12-13)
- 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
- 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
- Workaround: (this appears to work but not tested extensively)