Open rotoscan opened 5 years ago
Thanks for the report! MetaWRAP v1.1.8 comes loaded with more streamlined dependencies for easier integration and CONCOCT v1.0 dependency conflicts, but there will likely be issues at first. Keep them coming.
As for the checkm errror, this could be just a matter of your path being too long (see https://github.com/bxlab/metaWRAP/issues/35), or if you are using the same directories as before this could also stem from the newer CheckM v1.0.13. I cannot replicate the error, so can I ask you to test this for me, please?
Make a new conda environment, then install the metawrap dependancies only:
conda config --add channels defaults
conda config --add channels conda-forge
conda config --add channels bioconda
conda config --add channels ursky
conda install --only-deps -c ursky metawrap-mg=1.1.8
Then clone/download this repository, and put all the metawrap/bin/
contents into somewhere in PATH (such as /usr/bin/
for example), or just add metawrap/bin/
to PATH (if you know how). This way you still have metawrap v1.1.8, but now you have control over the dependancies, so you can downgrade CheckM, and try running metawrap binning again.
conda install checkm-genome=1.0.12
Can you report back if this fixes the issue?
Dear Gherman,
just to clarify: I createD the conda environment and ran conda config commands and conda install. Then I cloned this repository. Now should copy and paste the content of this repository:
($ ls metaWRAP/bin/
config-metawrap metawrap metaWRAP metawrap-modules metawrap-scripts)
into the conda environment bin folder? I work in a cluster so I don't have access to the /usr/bin folder.
Yes, that would be the easiest!
Dear Gherman,
unfortunately I came across the exact same error. `*** [CheckM - tree] Placing bins in reference genome tree.
Identifying marker genes in 14 bins with 10 threads:
Process SyncManager-1:
Traceback (most recent call last):
File "/data/msb/tools/metawrap/THIRD_INSTALL/metawrap_env_3/lib/python2.7/multiprocessing/process.py", line 267, in _bootstrap
self.run()
File "/data/msb/tools/metawrap/THIRD_INSTALL/metawrap_env_3/lib/python2.7/multiprocessing/process.py", line 114, in run
self._target(*self._args, *self._kwargs)
File "/data/msb/tools/metawrap/THIRD_INSTALL/metawrap_env_3/lib/python2.7/multiprocessing/managers.py", line 550, in _run_server
server = cls._Server(registry, address, authkey, serializer)
File "/data/msb/tools/metawrap/THIRD_INSTALL/metawrap_env_3/lib/python2.7/multiprocessing/managers.py", line 162, in init
self.listener = Listener(address=address, backlog=16)
File "/data/msb/tools/metawrap/THIRD_INSTALL/metawrap_env_3/lib/python2.7/multiprocessing/connection.py", line 132, in init
self._listener = SocketListener(address, family, backlog)
File "/data/msb/tools/metawrap/THIRD_INSTALL/metawrap_env_3/lib/python2.7/multiprocessing/connection.py", line 256, in init
self._socket.bind(address)
File "/data/msb/tools/metawrap/THIRD_INSTALL/metawrap_env_3/lib/python2.7/socket.py", line 228, in meth
return getattr(self._sock,name)(args)
error: AF_UNIX path too long
Traceback (most recent call last):
File "/data/msb/tools/metawrap/THIRD_INSTALL/metawrap_env_3/bin/checkm", line 708, in
real 4m34.304s user 25m6.791s sys 0m56.264s `
I wonder if the path is too long. I will change my working directory to something "less deep" and see what happens. I will report here afterwards.
Sounds good. Thats what https://github.com/bxlab/metaWRAP/issues/35 did...
I was getting the same error, and can confirm reducing the length of the file path allowed the checkM portion to correctly begin in the reassemble_bins
module. Thanks.
Hey guys,
I know it's been a while, but I came across the same "OSError: AF_UNIX path too long" error. This may sound silly, but I am wondering how can I change the length of a file path?
BTW I am running Metawrap using a virtual python environment in a cluster, rather than Conda.
Here are the error messages I received:
[2021-06-27 22:26:11] INFO: [CheckM - tree] Placing bins in reference genome tree. [2021-06-27 22:26:13] INFO: Identifying marker genes in 57 bins with 160 threads: Process SyncManager-1: Traceback (most recent call last): File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx512/Core/python/3.8.10/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap self.run() File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx512/Core/python/3.8.10/lib/python3.8/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx512/Core/python/3.8.10/lib/python3.8/multiprocessing/managers.py", line 608, in _run_server server = cls._Server(registry, address, authkey, serializer) File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx512/Core/python/3.8.10/lib/python3.8/multiprocessing/managers.py", line 154, in init self.listener = Listener(address=address, backlog=16) File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx512/Core/python/3.8.10/lib/python3.8/multiprocessing/connection.py", line 448, in init self._listener = SocketListener(address, family, backlog) File "/cvmfs/soft.computecanada.ca/easybuild/software/2020/avx512/Core/python/3.8.10/lib/python3.8/multiprocessing/connection.py", line 591, in init self._socket.bind(address) OSError: AF_UNIX path too long
Unexpected error: <class 'EOFError'>
Traceback (most recent call last):
File "/gpfs/fs0/scratch/c/careg421/ruizhang/metawrap_py2/bin/checkm", line 611, in
Thanks for helping!
Rui
Dear Rui,
this is a problem easy to work around. You might need to move our input and output directories to a 'shorter' path. Basically create a folder not so deep inside your home or data folder and restart the process. Instead of path/to/my//folder/folder/folder/folder/folder/data, you want to move your data to /path/to/my/data
I hope it works! Best Rodolfo
Hi Rodolfo,
Thank you for the clarification, it worked! My original data was trapped in a dungeon 😂
Just for future reference, both input and output data paths have to be changed to a "not too deep" directory.
Rui
I am glad it worked!
Wish you a prosper computing =)
Dear Gherman,
again, thanks a lot for this amazing tool!
Lately, however, I've been having problems when using checkm related modules, such as binning or binning refinement.
Please see my log below:
error.out:
and std.out
I didn't have this before on versions 1.1.4 and previous ones...It started happening on the 1.1.5. This one I am working with now is the latest 1.1.8.
In order to keep things working, I willl attempt to install the 1.1.4 with: $ conda install metawrap-mg=1.1.4
I hope my message was clear and I appreciate any sort of help!
Thanks a lot! Cheers, Rodolfo