Hello everyone!
Today and tomorrow we will try to improve Galaxy tools to consume and
create collections.
You are welcome to join and contribute in any way. For example code
contributions, not matter how small, but also in improving
documentations and our [best-practice
guide](https://github.com/g
Hello gents,
I hope everyone is doing ok...
I'm in need of your help so badly it's a little bit urgent:
So my galaxy wasn't used in a while but the last time everything was working
well:
1. The web-site was functional
2. The local handler upload the files locally on the master
3.
Hello gents,
I figured out something: it has nothing to do with galaxy but maybe one of you
could explain me why I'm having this behavior :
I connect ssh on the torque master (where the galaxy web service is running)
and:
1. su - galaxy
2. cd /home/galaxy/galaxy-prod/database/job_w
Hello Josh,
Thank you so much for the answer.
I thought of that but it doesn’t solve my problem.
I need to create a routine that looks inside the new job’s directory :
So for example, a process that runs every second and looks inside
/home/galaxy/galaxy-prod/database/job_working_directory/000
And
Hi Edgar,
I am a pretty big newbie to Galaxy but I have had similar problems on my
Dev build with grabbing outputs from the working directories. Its a
temporary fix but I have put routines in a bash wrapper that uses a working
directory that I made and know. If your cluster has access to a shared
Hi Edgar,
Hm, I haven't gotten it to work but galaxy is supposed to support looking
in the working directory for the file. Its likely for reasons similar to
your error. If you have access to the program's script you could try to
force it to write the results somewhere else. I would be surprised if
Thank you again for the precisions.
On another note, I have a user that when he goes into his History Options -->
Saved Histories -->Advanced Search -->status: all, and he views one of his
deleted histories, he sees a job with those spinning dots. However, everything
is deleted: history, datase
Hi Edgar,
I vote for a permission problem. I had to recently debug a volume/file
permission problem and the symptoms are identical: Galaxy claims it can't find
a file that actually does exist. Given that you said /home/galaxy is an NFS
mount I strongly suspect something there has changed. U
