I hope John can give some more input on this,
but if you're really short on time you could try the ssh runner
directly from galaxy without pulsar. I'm very happy with this driving a
Torque 4 cluster.
The relevant part of my job_conf.xml looks like this:
```
Hi Folks,
I'm working on a time-sensitive project (just a day or two left to sort it
out) that requires I be able to submit jobs from a remote resource (TACC)
to my resources (Pittsburgh Supercomputing Center) using a shared
filesystem for data rather than staging via Pulsar. I've tried to set it
On 12/01/2016 12:08 PM, Maximilian Friedersdorff wrote:
>PS: and a completely unrelated piece of advice: Once you have fixed
>this issue, I strongly recommend switching to PostgreSQL.
>
I gather SQLAlchemy prefers this! What kind of issues can I expect when
using MySQL?
As far as
Hi Lance
I don't remember seeing the problem you describe with our servers. If I
do your query, I get:
...
count
---
55
(1 row)
looking at the actual ids, they are all in the lower three digits range
and many years old.
Regards, Hans-Rudolf
On 11/30/2016 08:20 PM, Lance
Hi Max
This does look bizarre indeed. I have no answer, and I can just
recommend a few things to test:
- delete your cookies
- how do you authenticate your users? can you log in as someone else?
what happens if you set 'require_login = False'
- what happens if you simplify your
