-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drmaa.errors.InvalidAttributeValueException #102
Comments
You haven't included the error, however have you set up your .cgat file correctly? cluster config documentation will help. |
Sorry I did a mistake with keyboard shorcut when I started writing the message and I've been editing it since then ;-) |
I've also tried adding
to my pipeline.yml but it doesn't change anything (cluster_queue_manager:sge and same error message) |
Can you try using |
I just tried with
which is copied from Kevin Rue-Albrecht .cgat.yml and it gave the exact same output... |
Not sure if it matters but the version of slurm installed on our cluster is 14.11.11 (quite old one I think). |
ok, your .cgat.yml looks ok to me. Oh thats quite an old version, that was released 26th Nov 2014, looks like slurm is 19.05 as the most stable release. Its quite difficult to debug on my end, but looking at the original error message However, given that the options at the beginning of the pipeline suggesting that it is defaulting still to sge and not slurm this is most likely not an issue with slurm and with cgatcore. I will have a think. Just checking the obvious your ~/cgat.yml is in your home folder and not elsewhere? |
I just googled I assume that's the DRMAA I'm using? According to release notes, it supports
so I guess our version doesn't support the |
Yes .cgat.yml is in my home folder |
We are sharing our cluster with a diagnostic team from the hospital, which is why we can't update slurm :-( Having said that, the slurm-drmaa library 1.0.6 is from 2017, so that may be something we could update... |
Ah yeh, it seems like your slurm-drmaa is too old then and you will need >1.1.0. |
Hi Adam, It's now working and I even don't have to specify the queue manager and the queue in the command line :-) Just FYI, in the log file, it's still written
For me it's not a problem as it's actually using slurm and the partition specified in the Thanks for your help! |
PS: I'm so happy it works and to finally be able to write proper pipelines for my analysis :-) |
Ah great! Very happy its working. Also thanks for the points you make. Happy scienceing. |
Hello,
I'm trying to set up cgat-core on a slurm cluster and can't make it send jobs to the nodes. I have the feeling it's something stupid I'm missing...
I wrote a very simple pipeline (attached) that's running perfectly well with the command
However if I remove the
no-cluster
option, I have the following error (see logs of Test5 attached for more detailed error message):I also noticed in the log file that the cluster queue et queue manager were wrong
despite the fact that my
~/.cgat.yml
file specifiesI know the
~/.cgat.yml
file is read because the log file also specifiesAnd further down in the same log file, I find
--partition=all.q
which confuses me quite a lot (I think it's the default partition on cgat cluster but not the one specified in the ~/.cgat.yml or in the pipeline.yml).Of note, if I specify the queue and queue manager in the python command and run the pipeline with
the log file (Test6, attached) now indicates the right cluster queue and queue manager but the partition is still
all.q
inand I still have the same drmaa error
I've attached the
pipeline_test.py.txt
, thepipeline.yml.txt
(.txt
needed to be allowed to upload here) and the log files ofTest5
withmake full -v5
andTest6
with--cluster-queue-manager=slurm --cluster-queue=ptfgen
. Happy to provide more info if needed or to test everything you think may help.Thank you very much!
All the best,
Alice
pipeline_test.py.txt
pipeline-yml.txt
cgatcore_Test5_4374626.log
cgatcore_Test6_4374627.log
The text was updated successfully, but these errors were encountered: