No I was not running it as user "galaxy" (was running it as me). I suppose I 
will have to request our sys administrator to run the command.
So in general this would not be an end-user user accessible solution (easily) 
for us. 

We will try changing the "output_collection_parameter" as you had suggested  
first to see if we can avoid the "failed" job problem altogether.

Thanks again.

-----Original Message-----
From: Nate Coraor [mailto:n...@bx.psu.edu] 
Sent: Friday, May 11, 2012 4:20 PM
To: Kelkar, Hemant
Cc: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] Problem related to a job that "failed"

On May 11, 2012, at 4:18 PM, Kelkar, Hemant wrote:

> No I did not execute it on the "galaxy" server. I do not have shell access to 
> the blade that actually runs the galaxy server. 
> So I would need to get my sys admin to run this then?

Not necessarily, as long as you are running it as the same user and have access 
to the database from wherever you're running it.

--nate

> 
> 
>> That's pretty odd, you're executing this on the Galaxy server?  What happens 
>> if you run fetch_eggs.py in the same directory?
> 
> --nate
> 
> 
> 


___________________________________________________________
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