Closed bhimbbiswa closed 3 years ago
Can you check if ruby is installed on your system? According to your log file, an executable with the name 'ruby' seems to exist but it's interesting that it does not return the version information. Try to run:
ruby --version
The output should be something like:
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]
Hi.
Thank you very much for your reply.
It shows
ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-linux]
I again updated ATLAS and again ran the analysis. But same error. Please find the logs attached below. DASTool.log S13_DASTool.log Atlas_all.sh.e11245365.txt
As ATLAS create its own conda environment, please find a copy of JSON file attached about Ruby.
I think this problem is similar to #5 #11 #13 and #48 as I got similar output in(see DASTool.log)
I dearly wanted to use DASTool for my analysis. Can you please help me. Regards,
Bhim
Hi Bhim,
Thanks for your log files and environment information. Your ruby looks fine to me. Can run the single copy gene prediction script directly using the following command and see if there are any error messages (you may have to adjust some paths)?
./DAS_Tool/src/scg_blank_diamond.rb diamond S13/annotation/predicted_genes/S13.faa DAS_Tool/db/bac.all.faa DAS_Tool/db/bac.scg.faa DAS_Tool/db/bac.scg.lookup 1
While running some tests, I've noticed that diamond has an issue with writing temporary files when the database is located on a mounted volume. I'm not sure if that's the problem in your case. However, the error message looks like this:
Searching alignments... Device not configured
Device not configured
Error: Error writing file diamond-tmp-2RAS0b Error: Error writing file diamond-tmp-nH2nTe
libc++abi.dylib: terminating with uncaught exception of type File_write_exception: Error writing file diamond-tmp-nH2nTe
libc++abi.dylib: terminating with uncaught exception of type File_write_exception: Error writing file diamond-tmp-2RAS0b
Cheers, Chris
Hi.
I am really sorry for my very late reply. Was stuck in some other work.
I used the following command but again core dump happened.
/lustre7/home/bhimbiswa/New_micro/databases/conda_envs/92a32d4b/share/das_tool-1.1.2-1/src/scg_blank_diamond.rb diamond /lustre7/home/bhimbiswa/New_micro/S13/annotation/predicted_genes/S13.faa /lustre7/home/bhimbiswa/New_micro/databases/conda_envs/92a32d4b/share/das_tool-1.1.2-1/db/bac.all.faa /lustre7/home/bhimbiswa/New_micro/databases/conda_envs/92a32d4b/share/das_tool-1.1.2-1/db/bac.scg.faa /lustre7/home/bhimbiswa/New_micro/databases/conda_envs/92a32d4b/share/das_tool-1.1.2-1/db/bac.scg.lookup 1
This is the output I got
/var/spool/uge/m06/job_scripts/11282269: line 8: 63698 Segmentation fault (core dumped) /lustre7/home/bhimbiswa/New_micro/databases/conda_envs/92a32d4b/share/das_tool-1.1.2-1/src/scg_blank_diamond.rb diamond /lustre7/home/bhimbiswa/New_micro/S13/annotation/predicted_genes/S13.faa /lustre7/home/bhimbiswa/New_micro/databases/conda_envs/92a32d4b/share/das_tool-1.1.2-1/db/bac.all.faa /lustre7/home/bhimbiswa/New_micro/databases/conda_envs/92a32d4b/share/das_tool-1.1.2-1/db/bac.scg.faa /lustre7/home/bhimbiswa/New_micro/databases/conda_envs/92a32d4b/share/das_tool-1.1.2-1/db/bac.scg.lookup 1
Reagrds,
Bhim
As suggested by @yanhui09 in #13, removing Ruby from my conda environment solved the problem.
As suggested, I used the following command in the conda environment in which this program was running.
conda remove ruby --force
Closing this issue as the problem is solved.
Hi.
I am doing metagenomic analysis in Atlas (https://github.com/metagenome-atlas/atlas) pipeline.
I am getting this error again and again. Please help to solve.
I tried increasing the ram as well as changing the number of threads but same problem.
It stops with a core dump. core.25573.txt
Please find the required logs attached. DASTool.log Main_log.txt S13_DASTool.log