# Update to 2.1

**URL:** <https://forums.interworx.com/t/update-to-2-1/10011>\
**Category:** General Inquries\
**Created:** [September 14, 2005, 11:55am UTC](https://forums.interworx.com/t/update-to-2-1/10011 "2005-09-14T11:55:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jerricho](https://forums.interworx.com/letter_avatar_proxy/v4/letter/j/898d66/32.png) [@jerricho](https://forums.interworx.com/u/jerricho)\
**Post date:** [September 14, 2005, 11:55am UTC](https://forums.interworx.com/t/update-to-2-1/10011/1 "2005-09-14T11:55:12Z")

</div>

error: %post(interworx-nodeworx-2.1.0-45.iworx.noarch) scriptlet failed, exit status 255

Is this something bad?

---

<div class="post-metadata">

**Author:** ![IWorx-Chris](https://forums.interworx.com/letter_avatar_proxy/v4/letter/i/ba8739/32.png) [@IWorx-Chris](https://forums.interworx.com/u/IWorx-Chris)\
**Post date:** [September 14, 2005, 12:13pm UTC](https://forums.interworx.com/t/update-to-2-1/10011/2 "2005-09-14T12:13:58Z")

</div>

The short answer is the update failed most likely and I believe you just opened a ticket so we’ll check it out in just a sec.

It looks like YUM on many folk’s boxes is interpreting the prerequisites “differently” than it did before so if you see any upgrade oddness please open a ticket and we’ll check it out.

What’s odd is on our 10s of internal test and production boxes we didn’t see a lick of the yum issue :S.

Anyway, we’ll be checking this out in just a sec.

Chris

---

<div class="post-metadata">

**Author:** ![Paul](https://forums.interworx.com/user_avatar/forums.interworx.com/paul/32/6_2.png) [@Paul](https://forums.interworx.com/u/Paul)\
**Post date:** [September 14, 2005, 2:12pm UTC](https://forums.interworx.com/t/update-to-2-1/10011/3 "2005-09-14T14:12:50Z")

</div>

We’ve figured out the cause of this update issue some folks have been having with the update.

A new set of InterWorx rpms have been put up to resolve the issue (the 2.1.0-46 set).

If you have this issue and only have the 2.1.0-45 set installed, running  
yum update

will solve the problem.

Paul