jodyphelan / NTM-Profiler

Profiling NTM WGS data
GNU General Public License v3.0
10 stars 2 forks source link

ntm-profiler running failed in docker container #33

Open yujun2017 opened 9 months ago

yujun2017 commented 9 months ago

We can't run NTM-profiler 0.3.0 due to update_db failed.

when we tried to run NTM-profiler 0.2.0 inside docker container, we got the error. I have attached error text file in the tickets. Could you please let us know how to fix the issues?

Running command: set -u pipefail; kmc -t1 -sf1 -sp1 -sr1 -k31 @171cd1ce-30eb-4cff-b32f-2a8032c51490.list 171cd1ce-30eb-4cff-b32f-2a8032c51490 171cd1ce-30eb-4cff-b32f-2a8032c51490 Traceback (most recent call last): File "/opt/conda/envs/ntm-profiler/bin/ntm-profiler", line 322, in args.func(args) File "/opt/conda/envs/ntm-profiler/bin/ntm-profiler", line 89, in main_profile species_prediction = pp.speciate(args) File "/opt/conda/envs/ntm-profiler/lib/python3.10/site-packages/pathogenprofiler/cli.py", line 64, in speciate kmer_dump = fastq_class.get_kmer_counts(args.files_prefix,threads=args.threads) File "/opt/conda/envs/ntm-profiler/lib/python3.10/site-packages/pathogenprofiler/fastq.py", line 127, in get_kmer_counts run_cmd(f"kmc {bins} -t{threads} -sf{threads} -sp{threads} -sr{threads} -k{klen} @{tmp_file_list} {tmp_prefix} {tmp_prefix}") File "/opt/conda/envs/ntm-profiler/lib/python3.10/site-packages/pathogenprofiler/utils.py", line 391, in run_cmd raise ValueError("Command Failed:\n%s\nstderr:\n%s" % (cmd,stderr.decode())) ValueError: Command Failed: set -u pipefail; kmc -t1 -sf1 -sp1 -sr1 -k31 @171cd1ce-30eb-4cff-b32f-2a8032c51490.list 171cd1ce-30eb-4cff-b32f-2a8032c51490 171cd1ce-30eb-4cff-b32f-2a8032c51490

61ae2b93-2dc9-4966-8101-f64c6158c40f.errlog.txt

jodyphelan commented 9 months ago

Hi @yujun2017 ,

Do you have the error report for v0.3.0?

yujun2017 commented 9 months ago

Jody: Yes. Here is the error file when I tried to run update_db in 0.3.0 in my mac pro. We would like to use the 0.3.0 version in our application. but we run into errors and try to solve it before we can push to prod. I have another question regarding the ntm-db location. When we push an application to our prod, where should we put the ntm-db? I just noticed ntm-db will be created in the location that we are running the update_db command. When we are using AWS, how do we solve this problem?

Thanks!

John

On Thu, 14 Dec 2023 at 18:10, Jody Phelan @.***> wrote:

Hi @yujun2017 https://github.com/yujun2017 ,

Do you have the error report for v0.3.0?

— Reply to this email directly, view it on GitHub https://github.com/jodyphelan/NTM-Profiler/issues/33#issuecomment-1856908002, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDIGTFJ7BDDCPAB6G4YDV3YJOBM3AVCNFSM6AAAAABAVJXANCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJWHEYDQMBQGI . You are receiving this because you were mentioned.Message ID: @.***>

--

John Yu

ntm-profiler error report

Cleaning up after failed run

yujun2017 commented 9 months ago

Jody: I also tried to install ntm-profiler 0.3.0 in the miniconda3 docker image, ntm-profiler can't be updated db. here is the part of dockerfile, You can try

Miniconda Image: Install Conda package

FROM continuumio/miniconda3:latest as conda

RUN conda config --add channels defaults && \ conda config --add channels bioconda && \ conda config --add channels conda-forge && \ conda create -n mykrobe -y -c bioconda mykrobe && \ conda install -c conda-forge zip && \ conda create -n tb-profiler tb-profiler=4.4.2 cryptography=39.0.1 && \

conda create -n ntm-profiler ntm-profiler=0.2.0 cryptography=39.0.1

conda create -n ntm-profiler ntm-profiler=0.3.0

ENV PATH="$PATH:/opt/conda/envs/ntm-profiler/bin" RUN /opt/conda/envs/ntm-profiler/bin/ntm-profiler update_db

John

On Thu, 14 Dec 2023 at 18:10, Jody Phelan @.***> wrote:

Hi @yujun2017 https://github.com/yujun2017 ,

Do you have the error report for v0.3.0?

— Reply to this email directly, view it on GitHub https://github.com/jodyphelan/NTM-Profiler/issues/33#issuecomment-1856908002, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDIGTFJ7BDDCPAB6G4YDV3YJOBM3AVCNFSM6AAAAABAVJXANCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJWHEYDQMBQGI . You are receiving this because you were mentioned.Message ID: @.***>

--

John Yu

yujun2017 commented 9 months ago

Jody: This is John Yu from BCBB/NIH and I just want to check with you what's the status for the NTM profiler? We plan to move NTM profiler to Prod in February and hope you can fix the issue before we move on.

Thanks!

John

On Fri, 15 Dec 2023 at 06:56, John Yu @.***> wrote:

Jody: I also tried to install ntm-profiler 0.3.0 in the miniconda3 docker image, ntm-profiler can't be updated db. here is the part of dockerfile, You can try

Miniconda Image: Install Conda package

FROM continuumio/miniconda3:latest as conda

RUN conda config --add channels defaults && \ conda config --add channels bioconda && \ conda config --add channels conda-forge && \ conda create -n mykrobe -y -c bioconda mykrobe && \ conda install -c conda-forge zip && \ conda create -n tb-profiler tb-profiler=4.4.2 cryptography=39.0.1 && \

conda create -n ntm-profiler ntm-profiler=0.2.0 cryptography=39.0.1

conda create -n ntm-profiler ntm-profiler=0.3.0

ENV PATH="$PATH:/opt/conda/envs/ntm-profiler/bin" RUN /opt/conda/envs/ntm-profiler/bin/ntm-profiler update_db

John

On Thu, 14 Dec 2023 at 18:10, Jody Phelan @.***> wrote:

Hi @yujun2017 https://github.com/yujun2017 ,

Do you have the error report for v0.3.0?

— Reply to this email directly, view it on GitHub https://github.com/jodyphelan/NTM-Profiler/issues/33#issuecomment-1856908002, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDIGTFJ7BDDCPAB6G4YDV3YJOBM3AVCNFSM6AAAAABAVJXANCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJWHEYDQMBQGI . You are receiving this because you were mentioned.Message ID: @.***>

--

John Yu

--

John Yu

yujun2017 commented 8 months ago

Jody: I just want to update the issue we have found for latest ntm-profiler. The issue is only "ntm-profiler update_db" command. As soon as we created db, we can run ntm-profiler without any issue.