Hi,
We had this behavior when we used the default SQLite.
Since we switched on MySQL, it fixed this :P
Maybe a clue for you ?
Gildas
Le 18/06/2014 18:33, Carlos del Ojo a écrit :
Hi All,
I am using the API (posting to 'http://localhost:8080/api/workflows' )
and running 8 workflows in a
Hi,
Yes I found a workaround.
Initially I had problems because I was using SQLite and I had lock problems
that led to ugly SQLAlchemy errors.
After changing to Postgres SQL I got rid of lock errors but I had same
issue.
So I tried to create a simple script (my workflow has 14 processes)
from
Hi !
I have a big workflow and sometime when I launched it, I got an error message
for some of my tools : unable to finish job.
I think it's maybe Galaxy ran multiple job so I get this error message.
I'm looking to run my workflow step by step.
For example this workflow:
Hi all,
I have been trying to wrap a test r script into my local galaxy install
using r_wrapper.sh but have been running with problems. When I run the
tool, I get the following error in the side bar. For reference, I've pasted
the xml file below.
Error:
Error in file(file, rt) : cannot open the
I've just upgraded a galaxy instance from the Nov 2013 release to the
current. I had a few issues, mostly related to tool migration.
1) The entires in the tool_conf.xml file were not deleted as they should
have been. This is a pain, but I can fix it (though it will take some time)
2) The
This syntax
*write.table(data1, file={$out_data}, *
might not do what you expect. The $ has to be outside the braces, but
they're not needed there anyway - something like this might work better:
*write.table(data1, file=$out_data,..*
When things don't work, it's always useful to check the
Its looks like you were going to post an error message but didn't.
That might help debug problem.
There is no way currently at the workflow level to force one job to
wait for another before completion (other than assigning an explicit
input/output relationship between the steps). There is a
