You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not able to start a MXQI session requesting 180 GiB of memory despite over 500 GiB being available:
$ ssh -t pmenzel@geniux.molgen.mpg.de mxqi -j 24 -m 180G --whitelist hotelcalifornia
Requested Resources:
processors: 24
max memory: 184320 MB
max runtime: 600 min
whitelist: hotelcalifornia
Note, that your job is killed without warning, if you exceed the reserved memory or runtime.
Waiting for callback from job 54807216 (group 574595)
Sorry, failed to get a free slot with your requested resources in 30 seconds.
You may continue to wait or abort with ^C.
Please send email to helpdesk@molgen.mpg.de if your demand is not satisfied.
Continue waiting...
^C
job 54807216 cancelled
Connection to geniux.molgen.mpg.de closed.
$ ssh -t pmenzel@geniux.molgen.mpg.de mxqi -j 24 -m 179500M --whitelist hotelcalifornia
Requested Resources:
processors: 24
max memory: 179500 MB
max runtime: 600 min
whitelist: hotelcalifornia
Note, that your job is killed without warning, if you exceed the reserved memory or runtime.
Waiting for callback from job 54807217 (group 574599)
Last login: Wed Apr 9 14:38:19 2025 from geniux.molgen.mpg.de
# # ### # # hotelcalifornia
## ## ## ##### # # # # # system Supermicro 2023US-TR4
# # # # # # # # # # # # # cpu 128x AMD EPYC 7551
# # # # # # # # # # # 64 ram 1031.7 GB
# # ###### ##### # # # # # arch x86_64 / 64-bit
# # # # # # # # # # # glibc 2.36
# # # # # # ### #### # # kernel 5.15.131.mx64.457 #1
tags: amd confidential hitparade mx64 mxqd server
* MXQ cluster node - only to be used via mxqsub/mxqi
* Access to confidential data enabled
pmenzel@hotelcalifornia:~$ logout
Connection to hotelcalifornia.molgen.mpg.de closed.
Connection to geniux.molgen.mpg.de closed.
The text was updated successfully, but these errors were encountered:
With
I am not able to start a MXQI session requesting 180 GiB of memory despite over 500 GiB being available:
The text was updated successfully, but these errors were encountered: