Hello,
I am having problems in activating the qiime2-2022.11 environment.
The follow message appears:
conda activate qiime2-2022.11
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per development.
Illegal instruction (core dumped)
I'm running it on Ubuntu, and no error was reported during instalation on the Miniconda3.
I didn't find any other topic that could help me.
Thank you.
@carolinnerdc,
Can you post the results of running conda info and conda list in your environment? We have received a handful of complaints like this and are working to resolve the issue.
Thanks for replying. Sure.
(base) root@Serv:~# conda info
active environment : base
active env location : /root/miniconda3
shell level : 1
user config file : /root/.condarc
populated config files :
conda version : 23.1.0
conda-build version : not installed
python version : 3.10.8.final.0
virtual packages : __archspec=1=x86_64
__glibc=2.27=0
__linux=4.15.0=0
__unix=0=0
base environment : /root/miniconda3 (writable)
conda av data dir : /root/miniconda3/etc/conda
conda av metadata url : None
channel URLs : main/linux-64
main/noarch
r/linux-64
r/noarch
package cache : /root/miniconda3/pkgs
/root/.conda/pkgs
envs directories : /root/miniconda3/envs
/root/.conda/envs
platform : linux-64
user-agent : conda/23.1.0 requests/2.28.1 CPython/3.10.8 Linux/4.15.0-202-generic ubuntu/18.04.6 glibc/2.27
UID:GID : 0:0
netrc file : None
offline mode : False
(base) root@Serv:~# conda list
_libgcc_mutex 0.1 main
_openmp_mutex 5.1 1_gnu
brotlipy 0.7.0 py310h7f8727e_1002
bzip2 1.0.8 h7b6447c_0
ca-certificates 2023.01.10 h06a4308_0
certifi 2022.12.7 py310h06a4308_0
cffi 1.15.1 py310h5eee18b_3
charset-normalizer 2.0.4 pyhd3eb1b0_0
conda 23.1.0 py310h06a4308_0
conda-content-trust 0.1.3 py310h06a4308_0
conda-package-handling 2.0.2 py310h06a4308_0
conda-package-streaming 0.7.0 py310h06a4308_0
cryptography 38.0.4 py310h9ce1e76_0
idna 3.4 py310h06a4308_0
ld_impl_linux-64 2.38 h1181459_1
libffi 3.4.2 h6a678d5_6
libgcc-ng 11.2.0 h1234567_1
libgomp 11.2.0 h1234567_1
libstdcxx-ng 11.2.0 h1234567_1
libuuid 1.41.5 h5eee18b_0
ncurses 6.4 h6a678d5_0
openssl 1.1.1s h7f8727e_0
pip 22.3.1 py310h06a4308_0
pluggy 1.0.0 py310h06a4308_1
pycosat 0.6.4 py310h5eee18b_0
pycparser 2.21 pyhd3eb1b0_0
pyopenssl 22.0.0 pyhd3eb1b0_0
pysocks 1.7.1 py310h06a4308_0
python 3.10.8 h7a1cb2a_1
readline 8.2 h5eee18b_0
requests 2.28.1 py310h06a4308_0
ruamel.yaml 0.17.21 py310h5eee18b_0
ruamel.yaml.clib 0.2.6 py310h5eee18b_1
setuptools 65.5.0 py310h06a4308_0
six 1.16.0 pyhd3eb1b0_1
sqlite 3.40.1 h5082296_0
tk 8.6.12 h1ccaba5_0
toolz 0.12.0 py310h06a4308_0
tqdm 4.64.1 py310h06a4308_0
tzdata 2022g h04d1e81_0
urllib3 1.26.14 py310h06a4308_0
wheel 0.37.1 pyhd3eb1b0_0
xz 5.2.10 h5eee18b_1
zlib 1.2.13 h5eee18b_0
zstandard 0.18.0 py310h5eee18b_0
I hope it helps. Cheers.
@carolinnerdc, Ok I have been talking with some of the other developers, and it sounds like we had a patch release that should have fixed this. However, Conda does not necessarily create a "clean" enough environment on its own that at simple new install will work. What seems to be working for people is remove their current environment conda remove -n YOUR_ENVIRONMENT_NAME, then run conda clean --all, then perform a fresh environment install using the instructions at the installation page. Let me know if this works for you.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.