Hi I have large dataset and I want to get the differential expression but the tophat is not responding, its not running, it has been now 3 days. In one of the dataset the colour changed from grey to yellow (the dataset is running) but green color never appeared - I delete it and re run the same file, now it is grey in colour (new dataset and not all of its data are available yet). I have other datasets I ran them and I got the same problem either (new dataset and not all of its data are available yet) or (This job is waiting to run) but doesnt run. THE TOPHAT IS NOT RESPONDING
Heads up! This is a static archive of our support site. Please go to help.galaxyproject.org if you want to reach the Galaxy community. If you want to search this archive visit the Galaxy Hub search
Question: tophat is not responding
2.1 years ago by
azadjali • 0
azadjali • 0 wrote:
ADD COMMENT • link •modified 2.1 years ago by Jennifer Hillman Jackson ♦ 25k • written 2.1 years ago by azadjali • 0
2.1 years ago by
Jennifer Hillman Jackson ♦ 25k
Jennifer Hillman Jackson ♦ 25k wrote:
Update: The cluster fix has been made and jobs are dispatching normally. Queued jobs will execute - no need to delete/rerun. Tools that require more resources are sent to a busier cluster. That queue is expected to have some continued delays until the backlog of jobs is processed (up to a few days).
Thanks for reporting the problem and for your patience, Jen, Galaxy team
ADD COMMENT • link written 2.1 years ago by Jennifer Hillman Jackson ♦ 25k
Please log in to add an answer.
Powered by Biostar version 16.09
Traffic: 181 users visited in the last hour
Sorry guys it start working again but as usual slow and late respond. what I did after 3 days of waiting, I deleted my complete history and re run my datasets and it works
This is a known issue our team is actively working to correct. Right now, the advice is to allow queued jobs to remain queued. These will execute once the issue is resolved. More feedback after the fix, to let you and others having the same issue know what is going on.
It is recommended to not stop/restart jobs as this generally extends wait times even more. But is sounds as if you got lucky (not all jobs are impacted by the current issue). For others reading, use your best judgment. Restarted jobs have just as much of a chance of hitting the delay problem as currently queued jobs.
Thanks! Jen, Galaxy team
Thank you dear Jennifer, I got your point. Just to tell you that the tophat issue appeared again (its really annoying) as I ran new dataset that stuck with tophat since morning-hope it wont take days like last time and I hope the team can solve the issue as soon as possible.
Thank you again.