Hi Hans-Rudolf, Thanks for your answer. I've launched lot of jobs since monday. And some jobs were finished and some jobs never started. In "Manage jobs" I can see jobs queued because they need inputs which are queued, so I think it's normal. But other jobs are described like this : 9554 user_login 0 hours ago samtools_flagstat new 23199 ok, 23243 ok None None None The two necessary inputs for this job (23199 and 2343) are ok and the job doesn't run. Another mysterious line is : 9561 user_login 0 hours ago fastqc new Unable to determine inputs None None None After check this job in my history, I'm sure that the input of this job is green and really available. Why can galaxy not determine inputs ? Finally, in "Manage Jobs" there are only jobs queued. No jobs running. Any idea ? Thanks Julie 2014-07-23 11:35 GMT+02:00 Hans-Rudolf Hotz <hrh@fmi.ch>:
Hi Julie
Are there any jobs running at all? What do you get when you click on "Manage jobs" in the admin menu? Maybe you have some old jobs 'running' which are now blocking your queue?
Hans-Rudolf
On 07/23/2014 11:14 AM, julie dubois wrote:
Hi all, I've seen several posts for jobs which stay queued and never start with an installation of galaxy on a cluster. But our installation is just a local instance of galaxy in 1 PC and I have more than 100 jobs which stay queued and never start.
How can I debug this problem (my version of galaxy is the latest 2june2014).
And is it possible to run those jobs without restart galaxy because it would be very long to rerun each job manually after reloading galaxy.
Thanks.
Julie ___________________________________________________________ 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/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/