On Oct 25, 2011, at 2:43 AM, Andrew Warren wrote:

> Hello,
> I recently encountered a problem when trying to run Cufflinks on eight BAM 
> files on our galaxy instance (via the multi-input toggle) and received the 
> error: "Unable to run job due to a misconfiguration of the Galaxy job running 
> system" for some, but not all, of the cufflinks jobs that appear in the 
> history. These particular BAM files were copied over from the history of a 
> larger workflow where they were successfully run through cufflinks. In the 
> case of the problem workflow run, the cufflinks jobs are all successfully 
> submitted to Torque PBS and continue to run and finish but many have this 
> error displayed in the History. The jobs with the error displayed fail to 
> copy files from the working directory to the database directory despite 
> running to completion. We recently updated to galaxy-central changeset 
> 6131:be6c89c33639. I have seen this error multiple times for this workflow, 
> even after restarting galaxy. Does anyone have any ideas of what might be 
> going wrong?

Hi Andrew,

The error you're receiving indicates that there should also be a traceback 
logged to the Galaxy server log file or output when this occurs.  Could you 
check the log/output for such a traceback?

Thanks,
--nate

> 
> Thanks for any help,
> Andrew Warren
> ___________________________________________________________
> 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/


___________________________________________________________
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/

Reply via email to