Hi Robert, 
Can you check on CloudMan's Admin page if the following is shown (towards the bottom of the page): "Switch master to not run jobs" 
If it says, "Switch master to run jobs", just click on the text and the master will become an execution host on the cluster, which should then give Galaxy some resources to run the jobs on. 

Sorry for the trouble and let us know if this does not fix it,
Enis

On Wed, Oct 8, 2014 at 6:34 PM, Petit III, Robert A. <robert.petit@emory.edu> wrote:
Hello Galaxy Team!

I've set up a vanilla CloudMan instance using AWS.  I've set the head node to not handle jobs and have set AutoScaling to a minimum of 0 and a maximum of 4 worker nodes.

Upon submitting a job, it fails with the following error: Unable to run this job due to a cluster error, please retry it later

Now if I set AutoScaling to a minimum of 1 worker node it works fine. But I would rather not always have 1 worker node up.

Any recommendations?

Thank you very much,
Robert



This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/