38,760
edits
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
Line 33: | Line 33: | ||
= Cedar only = | = Cedar only = | ||
* Some I/O operations on /project yield the error, "Cannot send after transport endpoint shutdown". We are working with the vendor to resolve this. | |||
* <del>Slurm operations will occasionally time out with a message such as ''Socket timed out on send/recv operation'' or ''Unable to contact slurm controller (connect failure)''. As a temporary workaround, attempt to resubmit your jobs/commands; they should go through in a few seconds. </del> | * <del>Slurm operations will occasionally time out with a message such as ''Socket timed out on send/recv operation'' or ''Unable to contact slurm controller (connect failure)''. As a temporary workaround, attempt to resubmit your jobs/commands; they should go through in a few seconds. </del> | ||
** Should be resolved after a VHD migration to a new backend for slurmctl. | ** Should be resolved after a VHD migration to a new backend for slurmctl. | ||
* | *Some people are getting the message ''error: Job submit/allocate failed: Invalid account or account/partition combination specified''. | ||
** For users with only one account, this should be resolved in the latest version of the job submission script (Nathan Wielenga 2017-08-18). | ** For users with only one account, this should be resolved in the latest version of the job submission script (Nathan Wielenga 2017-08-18). | ||
** If you still see this, specify <tt>--account=<accounting group></tt> in you job submission. See [https://docs.computecanada.ca/wiki/Running_jobs#Accounts_and_projects https://docs.computecanada.ca/wiki/Running_jobs] | |||
= Graham only = | = Graham only = |