Hi Dave, Sorry to hear you're having trouble and no, the behavior you describe is not the expected behavior.

From the description, unfortunately it does not sound like adding more nodes will help the case.

Could you take a look at the log files for Galaxy and see if anything there is indicating as to what may be happening? Feel free to paste the log in your reply so we can take a look too. The Galaxy log is accessible on CloudMan's Admin page (link is in top right hand corner of the CloudMan console). What specific tool(s) were you using when this happened? Does the same tool work with the smaller files? On Tue, Jan 24, 2012 at 8:57 PM, Dave Lin <dave@verdematics.com> wrote:

Dear Galaxy Team,

I seem to get quite a few "Cluster could not complete job" error messages when trying to process larger solid files. In some cases, re-running the same job does the trick.

Is this due to something I've misconfigured (i.e. some time-out setting) or is this expected behavior? Any suggestions (i.e. increase number of nodes)?

Details - Running own instance of Galaxy using Cloudman - Galaxy code is updated (within 1 week) - Only have 1 node running. - Nobody else is using the system yet.

Thanks, Dave

P.S. New to galaxy and pretty impressed so far.

Running the Galaxy

___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:

http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists, please use the interface at:

http://lists.bx.psu.edu/