Re: [galaxy-user] Help!!!!!! with Galaxy Cloud!!!!!

2011-04-12 Thread Mike Dufault
Hello Galaxy Staff, My data has been running on the Amazon EC2 for just over 24hrs. I have not closed any windows and my Exome analysis made it all the way through to filter on Pile up. I have two tabs for this instance. One is the Galaxy Cloudman Console and the other is the tab where I

[galaxy-user] Reload .loc files without restarting the Galaxy server?

2011-04-12 Thread Luobin Yang
Hi all, I am wondering if it's possible to to reload a .loc file without restarting the Galaxy server? Thanks, Luobin ___ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at

Re: [galaxy-user] Help!!!!!! with Galaxy Cloud!!!!!

2011-04-12 Thread Enis Afgan
Hi Mike, Try accessing your Galaxy instance now. It should be ok. The link in your email contained the IP for your instance so I took the liberty of restarting Galaxy and that brought it back up. There seems to have been an issue with Galaxy accessing its database and that resulted in Galaxy

Re: [galaxy-user] Help!!!!!! with Galaxy Cloud!!!!!

2011-04-12 Thread Mike Dufault
Hi Enis, Thanks for looking into this. From the Galaxy Cloudman Console, I can see that it was restarted from the log (thanks), but the Access Galaxy choice is still grayed out and I don't know how to access the Analysis window. Is there a way back into my analysis? Thanks, Mike --- On

Re: [galaxy-user] Help!!!!!! with Galaxy Cloud!!!!!

2011-04-12 Thread Mike Dufault
Hi Enis, THANK YOU!!! I see that my filter pileup on data step is running. Is this the same analysis that was running before or did it relauch when you restarted Galaxy? I just don't know if the analysis would be compromised. Thanks again to you and the whole Galaxy team. Best, Mike --- On

Re: [galaxy-user] Help!!!!!! with Galaxy Cloud!!!!!

2011-04-12 Thread Enis Afgan
Galaxy has the functionality to recover any jobs that were running after it's restarted so it is quite possible to for the job to still be running. In addition, from the cloudman console, it appears that at least one instance is pretty heavily loaded so that can also mean that the job is still