Known issues/en: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
(Updating to match new version of source page)
(Updating to match new version of source page)
 
(30 intermediate revisions by the same user not shown)
Line 1: Line 1:
<languages />
<languages />
= Report an issue =
* Please report issues to the [[Technical Support|technical support]] team.


= Shared issues =
Problems that affect many users and are being investigated, such as a cluster-wide malfunction or outage, are on [https://status.alliancecan.ca/ the Alliance Status page]. This "Known issues" page describes problems that affect many users but that may take some time to repair, or are not planned for repair at this time. Problems that only affect a specific software package are described on the wiki page for that software package.  
* The status page at http://status.computecanada.ca/ is not updated automatically yet, so may lag in showing current status.


== Scheduler issues ==
==Report an issue==
* Interactive jobs started via <tt>salloc</tt> require X11 forwarding to be enabled when you connect to the cluster. On Linux and MacOS, you can typically enable X11 forwarding by adding the option <tt>-X</tt> or <tt>-Y</tt> to your <tt>ssh</tt> command. If you do not have X11 forwarding capabilities, you can use <tt>srun --pty bash</tt> as the command to be run by <tt>salloc</tt>. For example: <tt>salloc --time=1:00:00 --ntasks=1 srun --pty bash</tt>. (''Reported at 12:26, 13 December 2017 (UTC)'')
Please report issues to the [[Technical Support|technical support]] team.
* 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.


== Quota and filesystem problems ==
==Shared issues==
=== Quota errors on /project filesystem ===
The [https://status.alliancecan.ca/ status page] is updated manually, so there may be a delay between when a problem begins and when it is posted to the status page.
* This topic has been moved to [[Frequently Asked Questions]].


=== Nearline ===
===Scheduler issues===
* 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|technical support]].


=== Missing symbolic links to project folders ===
No known issues.
* 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 https://ccdb.computecanada.ca/services/resources].


= Cedar only =
===Quota and filesystem issues===
Nothing to report at this time.


= Graham only =
====Missing project folder====
* /home is on an NFS appliance that does not support ACLs, so setfacl/getfacl doesn't work there.
Upon creation of a new account for a Principal Investigator, the [[Project layout|<code>/project</code>]] storage space might not be allocated until the next business day.
** Workaround: use the /project or /scratch filesystems instead.
** Might be resolved by an update or reconfiguration.
* <span style="color: red; text-decoration: line-through;"> diskusage_report (and alias 'quota') do not report on Graham /home </span> (FIXED as of 2017-11-27)
* Compute nodes cannot access Internet
** Solution: Contact [[Technical Support|technical support]] to request exceptions to be made; describe what you need to access and why.


* Crontab is not offered on Graham.
==Cluster-specific issues==


= Other issues =
===Béluga===
#Modules don't work for shells other than bash(sh) and tcsh.
No known issues.
#*Workaround: (this appears to work but not tested extensively)
 
#**<tt>source $LMOD_PKG/init/zsh</tt>
===Cedar===
#**<tt>source $LMOD_PKG/init/ksh</tt>
No known issues.
 
===Graham===
Graham's /scratch is often slow; it will be replaced soon.
 
===Narval===
No known issues.

Latest revision as of 22:23, 28 October 2024

Other languages:

Problems that affect many users and are being investigated, such as a cluster-wide malfunction or outage, are on the Alliance Status page. This "Known issues" page describes problems that affect many users but that may take some time to repair, or are not planned for repair at this time. Problems that only affect a specific software package are described on the wiki page for that software package.

Report an issue

Please report issues to the technical support team.

Shared issues

The status page is updated manually, so there may be a delay between when a problem begins and when it is posted to the status page.

Scheduler issues

No known issues.

Quota and filesystem issues

Missing project folder

Upon creation of a new account for a Principal Investigator, the /project storage space might not be allocated until the next business day.

Cluster-specific issues

Béluga

No known issues.

Cedar

No known issues.

Graham

Graham's /scratch is often slow; it will be replaced soon.

Narval

No known issues.

Retrieved from "https://docs.alliancecan.ca/mediawiki/index.php?title=Known_issues/en&oldid=163505"