qlaunch to a named qsub queue

[jkuck]

Hi,

I use qsub to submit jobs to a named queue, e.g.:

$ qsub -q atlas -l nodes=1:ppn=1 submit_script.sh

Where '-q atlas' specifies that qsub should submit my job to the queue named 'atlas.'  Following the queue tutorial (https://pythonhosted.org/FireWorks/queue_tutorial.html) I'm having trouble running "$ qlaunch singleshot" with the following error:

2017-01-23 11:39:42,254 INFO moving to launch_dir /atlas/u/jkuck/fireworks/fw_tutorials/queue/queue_tests

2017-01-23 11:39:42,256 INFO submitting queue script

2017-01-23 11:39:44,341 ERROR ----|vvv|----

2017-01-23 11:39:44,342 ERROR Error in job submission with PBS file FW_submit.script and cmd [u'qsub', u'FW_submit.script']

The error response reads: qsub: submit error (Unknown queue MSG=requested queue not found)

2017-01-23 11:39:44,342 ERROR ----|^^^|----

2017-01-23 11:39:44,342 ERROR ----|vvv|----

2017-01-23 11:39:44,343 ERROR Error writing/submitting queue script!

2017-01-23 11:39:44,343 ERROR Traceback (most recent call last):

  File "/opt/rh/python27/root/usr/lib/python2.7/site-packages/fireworks/queue/queue_launcher.py", line 135, in launch_rocket_to_queue

    raise RuntimeError('queue script could not be submitted, check queue '

RuntimeError: queue script could not be submitted, check queue script/queue adapter/queue server status!

2017-01-23 11:39:44,343 ERROR ----|^^^|----

I think the problem may be I haven't specified that my job should be run on the 'atlas' queue.  Please let me know how to make this specification, or if the error message might indicate a different problem.

Thanks,
Jonathan

[David Dotson]

Hi Jonathan,

I'd recommend making your own template submission script and including everything you need in there. It's not clear from the output below whether you are already doing this (looks like `qlaunch` is grabbing the default template included in fireworks), but I think it's rare that qlaunch "just works" on a given cluster without needing to create a template script for that specific machine.

David

--
You received this message because you are subscribed to the Google Groups "fireworkflows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fireworkflow...@googlegroups.com.
To post to this group, send email to firewo...@googlegroups.com.
Visit this group at https://groups.google.com/group/fireworkflows.
To view this discussion on the web visit https://groups.google.com/d/msgid/fireworkflows/94e9eaed-b6bd-4c85-af23-5cacb0764baa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Joseph Montoya]

Hi Jonathan,

If you’re following the queue tutorial, you should have a queue adapter file (e. g. my_qadapter.yaml).  In that file, there’s a line that reads 'queue: debug'.  Changing it to ‘queue: atlas’ should appropriately modify the script written by the queue launcher when it runs.  Note that there are several other parameters which can be specified by modifying the queue adapter file.

Best,

Joey

[jkuck]

Thanks Joey!  Replacing 'queue: debug' with ‘queue: atlas’ solved my problem.

Jonathan

[jkuck]

Appreciate the help David.  Replacing 'queue: debug' with ‘queue: atlas’ in the queue adapter file turned out to solve this issue, but will keep your advice in mind for the future!

Jonathan