Question: Minia bug: max rehashes reached: 65536000 (notify a developer)
0
gravatar for fungopoo
2.4 years ago by
fungopoo10
South Africa
fungopoo10 wrote:

Hi,

Minia just crashed, error message reads,

"[DSK: Pass 1/1, Step 2: counting kmers  ]  51.1 %   elapsed:   0 min 60 sec    estimated remaining:   0 min 57 sec   cpu:  760.5 %   mem: [ 127,  127,    0] MB EXCEPTION: OAHash: max rehashes reached: 65536000 (notify a developer)".

Any suggestions as to how I may proceed?

This has happened on two independent runs of a 4.8 gb dataset.

Thanks,

Angus

 

bug minia assembly • 912 views
ADD COMMENTlink modified 20 days ago by Biostar ♦♦ 20 • written 2.4 years ago by fungopoo10
3

I suggest you do as it says, and notify one of the developers ...

They will probably also be able to best advise you on how to proceed.

ADD REPLYlink modified 2.4 years ago • written 2.4 years ago by george.ry1.0k

FYI, the minia authors follow the "minia" tag here (a number of tools use biostars as their official support forum).
 

ADD REPLYlink written 2.4 years ago by Devon Ryan71k
1

Indeed, we do. Biostar is a good way to reach us.

ADD REPLYlink written 2.4 years ago by Rayan Chikhi1.2k

Is this the latest minia 2.0.3?

ADD REPLYlink written 2.4 years ago by Rayan Chikhi1.2k

Hi,

Thanks, yes 2.0.3

I used kmergenie to find kmer size, and then -abundance-min 3, I have subsequently re-run it and it still crashes.

ADD REPLYlink written 2.4 years ago by fungopoo10
  • What's special about this input dataset.. is it whole-genome DNA Illumina data?
  • What's your system? (amount of memory, free disk space on working directory)
  • Please try adding "-max-memory 4000" to the command line, this might fix it for now
  • The ideal way for me to debug this problem would be if you could send me the whole dataset (compressed with gzip), or a subsample where the bug still occurs, to rayan.chikhi@univ-lille1.fr

 

ADD REPLYlink modified 2.4 years ago • written 2.4 years ago by Rayan Chikhi1.2k

hi,

a final thanks, "

  • Please try adding "-max-memory 4000" to the command line, this might fix it for now"
  • this worked like a charm. 
  • I have 16gb ram, quad-core 64 bit cpu, OSX 10.10 and it ran for 838 s; thanks for you advice and patience.
ADD REPLYlink written 2.4 years ago by fungopoo10

Good to know it worked.

If anyone else experiences it and sees this page, please let me know that it happened to you too, so that we'll know that it might not be an isolated case.

ADD REPLYlink modified 2.4 years ago • written 2.4 years ago by Rayan Chikhi1.2k
1

Hi, I experienced the same problem, Minia crashed a few times because of memory allocation. The above advice helped :-) I tried to assemble draft genome of not known size, one lane from HiSeq 125PE (2 files 80 GB unzipped) on workstation with 189GB memory, 19x2.4GHz running Ubuntu 14.04. Thanks for advice Marie Kraus

ADD REPLYlink written 22 months ago by marie.kraus710

Thanks for letting us know :) We're preparing a next release of minia and hopefully it will fix that bug.

ADD REPLYlink written 22 months ago by Rayan Chikhi1.2k
1
gravatar for fungopoo
2.4 years ago by
fungopoo10
South Africa
fungopoo10 wrote:

OK,

Trying -max-memory 4000; if it crashes again I'll get the data to you.

The data is low-coverage whole genome DNA, Illumina miseq platform. I used Galaxy to clean it up, join the paired ends and concatenate two separate runs. 

 

ADD COMMENTlink written 2.4 years ago by fungopoo10
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 2.3.0
Traffic: 1418 users visited in the last hour