Question: Cufflinks never start??
0
gravatar for 柴田 弘紀
23 months ago by
柴田 弘紀20 wrote:

I am still a newbie on Galaxy.

I mapped my RNA-seq reads by TopHat without problem (I believe), then I fed the output "accepted hits"to Cufflinks. Four jobs popped up on the history window, then they have been "grey" for several days. I canceled the job and retried but it never work.

Some other jobs I queued after the Cufflinks jobs finished without problem. So my Galaxy hasn't been stuck.

What is the problem?

Please help.

Thanks.

ADD COMMENTlink modified 23 months ago by Jennifer Hillman Jackson25k • written 23 months ago by 柴田 弘紀20
0
gravatar for Jennifer Hillman Jackson
23 months ago by
United States
Jennifer Hillman Jackson25k wrote:

Hello,

The server http://usegalaxy.org is most likely just busy or you had many jobs associated with your account queued. That said, this long of a wait is unusual. If something more is going on server-side - we will write back with an update.

Please know that other issues can be a factor. Inputs (incorrect format, empty inputs, metadata issues), custom reference genome formatting, many compute intensive jobs queued .. these usually result in job failures or unexpected results. Should job delays continue and you can't find the source of the problem or simply want feedback, please feel free to send in a bug report. Include a link to this post in the comments. We'll check the entire history, not just the specific problem reported. Make sure the data to be examined is undeleted. Or, you can use the self-help troubleshooting list linked below that covers the basic checks - these are the same checks we do here for reported problems.

Thanks for reporting the issue. Different jobs are sent to different clusters. This is probably why other jobs started while the Cufflinks jobs were still in queue (these are dispatched to a busier cluster). I suggest allowing these to run, even if it takes a few days. If that advice changes, will include help in the updated reply (should server issues or longer-than-normal queues are present right now).

If you are not using http://usegalaxy.org, reply with details: Local or cloud Galaxy? Some other public server (URL)? Private Galaxy? (For the last two - contacting the admins of that instance is the path toward finding out what is going on.

Best, Jen, Galaxy team

ADD COMMENTlink written 23 months ago by Jennifer Hillman Jackson25k

Hi Jen,

Thanks for your reply. I am working on http://usegalaxy.org. I am using built-in mm9 for the reference genome. The size of my "accept hits" is only 212.2MB. I guess it's not too big. Still the jobs are "grey". How can I get bug reports??

Best,

Hiroki

ADD REPLYlink modified 23 months ago • written 23 months ago by 柴田 弘紀20
0
gravatar for Jennifer Hillman Jackson
23 months ago by
United States
Jennifer Hillman Jackson25k wrote:

Hello,

Update: The problem was on our side. 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 COMMENTlink written 23 months ago by Jennifer Hillman Jackson25k

Thanks for your help! Still my jobs haven't started running. But I will wait a bit more:)

Hiroki

ADD REPLYlink modified 23 months ago • written 23 months ago by 柴田 弘紀20
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 93 users visited in the last hour