This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
hpc:faq [2021/09/30 14:26] Luca Capello [I'm lost, where can I find support ?] add "Citation, publication and ackowledgments" |
hpc:faq [2023/12/13 08:37] (current) Yann Sagon [Can I run interactive tasks ?] |
||
---|---|---|---|
Line 23: | Line 23: | ||
What to do: be sure you aren't the cause. Check with '' | What to do: be sure you aren't the cause. Check with '' | ||
+ | ===== Account ===== | ||
+ | |||
+ | ==== When does my account expire ==== | ||
+ | * If you have a non student account (Phd, postdoc, researcher), | ||
+ | * If you have an outsider account, you need to check the expiration date you received when you filled the invitation. | ||
+ | * If you have an unige student account, you can check the expiration date with the '' | ||
+ | < | ||
+ | (baobab)-[yourusername@login2 ~]$ chage -l yourusername | ||
+ | Last password change | ||
+ | Password expires | ||
+ | Password inactive | ||
+ | Account expires | ||
+ | Minimum number of days between password change | ||
+ | Maximum number of days between password change | ||
+ | Number of days of warning before password expires | ||
+ | </ | ||
+ | |||
+ | ==== I'm leaving UNIGE, can I continue to use Baobab HPC service? ==== | ||
+ | Yes it is possible as long as you collaborate tightly with your former research group. Your PI must invite you as [[hpc: | ||
+ | We'll then reactivate your account. You'll keep your data. | ||
===== Storage ===== | ===== Storage ===== | ||
Line 94: | Line 114: | ||
See [[hpc/ | See [[hpc/ | ||
+ | ==== I'm not able to use all the cores of a compute node ==== | ||
+ | Indeed, we are reserving two cores per node for system tasks such as data transfer, and os stuff. | ||
+ | |||
+ | < | ||
+ | (yggdrasil)-[root@admin1 ~]$ scontrol show node cpu001 | ||
+ | NodeName=cpu001 Arch=x86_64 CoresPerSocket=18 | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | </ | ||
+ | |||
+ | If you really need to use all the cores of a compute node, you can override this parameter: '' | ||
+ | |||
+ | ref: https:// | ||
===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
+ | ==== Check ssh key ==== | ||
+ | If you connect to the cluster with an ssh key as authentication mechanism and you have trouble: | ||
+ | |||
+ | * check you have the correct private key: '' | ||
+ | | ||
==== Illegal instruction ==== | ==== Illegal instruction ==== | ||