Closed brittonstrickland closed 2 years ago
Hi @brittonstrickland , thanks for reporting and sorry for the very late reply!
As you mention that at least one genome was successfully analyzed I guess that this might be a mere technical issue. The max waiting period (86400000 s) exceeded!
check/error was introduce to forestall ASA³P from running forever in case a certain analysis hangs. For instance, this sometimes happens on HPC systems with attached storage. A lack of sufficient storage within the Docker container might also be in issue you could maybe check?
Could you please simply retry the analysis and see if the exact error remains?
Hi @brittonstrickland, how is it going with your analysis? Any progress? Does this issue remain? Since this is open for quite a qhile, I'm going to close this for now. However, please, do not hesitate to re-open is just in case the issue remains or you have further questions. Best regards!
Hi all,
I successfully ran 1 genome through ASA3P and planned to run 3 more genomes through the pipeline. The 1 genome that had previously been run was successful. However, when the pipeline got to genomes 2 and 3, there are several steps that resulted in the warning "max waiting period (86400000 s) exceeded!". For both of these 2 failed genomes, the pipeline was able to complete the QC, Mapping, and SNP step. However, the VFDetection, Taxonomy, MLST, ABR, Annotation, and Scaffolding step all failed due to the max waiting period warning, which resulted in several other steps being skipped.
Could this be due to a memory issue or machine issue? I don't expect this, since one genome was successfully pushed through the pipeline. I am currently running on an iMac with Docker Container with an allocated 6 CPUs and 12gb memory.
I have also attached my ASAP.log file for reference.