# Installation of 2022.11 fails

**URL:** https://forum.qiime2.org/t/installation-of-2022-11-fails/25167
**Category:** Technical Support
**Created:** [January 9, 2023, 6:02pm UTC](https://forum.qiime2.org/t/installation-of-2022-11-fails/25167 "2023-01-09T18:02:55Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![ataqdog](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/a/77aa72/32.png) [@ataqdog](https://forum.qiime2.org/u/ataqdog)
#### Post date: [January 9, 2023, 6:02pm UTC](https://forum.qiime2.org/t/installation-of-2022-11-fails/25167/1 "2023-01-09T18:02:55Z")

</div>

Recently (yesterday) updated from 2022.2 to 2022.11 however on my Linux (Debian Buster) box qiime fails with a hardware error:  
[7] 360653 illegal hardware instruction

Googling/tracing etc. suggested that this COULD be due to the Unifrac conda packages were compiled with a particular hardware dependency (GPU perhaps?). So I deleted both unifrac and unifrac-binaries from the install and this fixes the error messaging - but of course unifrac is an important component needed for many of my analyses. I wonder if a) others have experienced this (running a pretty old hardware though on a multiprocessor server from Dell) and if b) there is a simple fix like setting and environment variable like "export UNIFRAC\_USE\_GPU=N" (which did NOT work when unifrac is installed). Thanks.  
Ken

---

<div class="post-metadata">

### Author: ![ataqdog](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/a/77aa72/32.png) [@ataqdog](https://forum.qiime2.org/u/ataqdog)
#### Post date: [January 9, 2023, 8:34pm UTC](https://forum.qiime2.org/t/installation-of-2022-11-fails/25167/2 "2023-01-09T20:34:00Z")

</div>

Update:  
I uninstalled unifrac (and unifrac-binaries) and then reinstalled from conda repo and I see there is now an "updated" version of the binaries file to bioconda/linux-64::unifrac-binaries-1.2-h73f19ed\_1 from unifrac-binaries bioconda/linux-64::unifrac-binaries-1.1.1-h15a0faf\_4 and this has completely fixed the program. So thanks to the developers!

---

<div class="post-metadata">

### Author: ![ebolyen](https://forum.qiime2.org/user_avatar/forum.qiime2.org/ebolyen/32/11_2.png) [@ebolyen](https://forum.qiime2.org/u/ebolyen)
#### Post date: [January 12, 2023, 6:39pm UTC](https://forum.qiime2.org/t/installation-of-2022-11-fails/25167/3 "2023-01-12T18:39:08Z")

</div>

Hi @ataqdog, welcome to the forum!  
Sorry you ran into an issue, but thanks so much for documenting your solution!

---

<div class="post-metadata">

### Author: ![ataqdog](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/a/77aa72/32.png) [@ataqdog](https://forum.qiime2.org/u/ataqdog)
#### Post date: [January 20, 2023, 4:43pm UTC](https://forum.qiime2.org/t/installation-of-2022-11-fails/25167/4 "2023-01-20T16:43:30Z")

</div>

Spoke too soon. The problem persists. I see Daniel McDonald encountered a similar problem with the 2022.2 build that was not resolved for that situation. Seems like a compilation quirk on my hardware (standard 2011ish Dell box).

qiime --help  
QIIME is caching your current deployment for improved performance. This may take a few moments and should only happen once per deployment.  
[1] 3815128 illegal hardware instruction qiime --help

I have uninstalled unifrac unifrac-binaries using conda and conda also uninstalls q2-diversity plugins. Reinstalling unifrac and unifrac-binaries does NOT cause the problem - only trying to add back the q2-diversity plugins causes this issue. If other architectures do not see this, I will just use 2022.2 until a newer 2023 release appears (and perhaps the gods will smile on my architecture again). This is probably a black hole not worth pursuing of little-ole me - the older version seems to work just fine. Or maybe I can spring for a new box to run it on! 10 years is a long time to be using the same old silicon.

---

<div class="post-metadata">

### Author: ![lizgehret](https://forum.qiime2.org/user_avatar/forum.qiime2.org/lizgehret/32/17128_2.png) [@lizgehret](https://forum.qiime2.org/u/lizgehret)
#### Post date: [January 20, 2023, 11:41pm UTC](https://forum.qiime2.org/t/installation-of-2022-11-fails/25167/5 "2023-01-20T23:41:54Z")

</div>

Hi @ataqdog,

Thanks for following up - sorry to hear you're still running into issues!

How are you installing QIIME 2 on your machine? Through conda? If so, can you try running `conda clean --all`, removing your current 2022.11 environment, and doing a fresh install? If that doesn't work, we can investigate further!

Cheers 🦎

---

<div class="post-metadata">

### Author: ![system](https://forum-qiime2-org.s3.dualstack.us-west-2.amazonaws.com/original/3X/2/1/21af5fe23cb6f4579467c66a9ed94e55274ca7bd.svg) [@system](https://forum.qiime2.org/u/system)
#### Post date: [February 21, 2023, 5:41am UTC](https://forum.qiime2.org/t/installation-of-2022-11-fails/25167/6 "2023-02-21T05:41:58Z")

</div>

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
