# MySQL targets not working after boundary 0.10.3 upgrade

**URL:** <https://discuss.hashicorp.com/t/mysql-targets-not-working-after-boundary-0-10-3-upgrade/43888>\
**Category:** Boundary\
**Created:** [September 2, 2022, 8:19am UTC](https://discuss.hashicorp.com/t/mysql-targets-not-working-after-boundary-0-10-3-upgrade/43888 "2022-09-02T08:19:16Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThomasKinow](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/thomaskinow/32/16852_2.png) [@ThomasKinow](https://discuss.hashicorp.com/u/ThomasKinow)\
**Post date:** [September 2, 2022, 8:19am UTC](https://discuss.hashicorp.com/t/mysql-targets-not-working-after-boundary-0-10-3-upgrade/43888/1 "2022-09-02T08:19:16Z")

</div>

Hello,

Yesterday I tried to upgrade our boundary instances (1 controller and 1 worker) from 0.9.1 to 0.10.3 and it dit not go well. Using 0.10.3 and connecting to MySQL targets was not working anymore.  
Errors:

- MySQL client: `ERROR 2013 (HY000): Lost connection to server at 'handshake: reading initial communication packet', system error: 11`
- boundary client: `error reading handshake result: failed to read protobuf message: failed to get reader: received close frame: status = StatusInternalError and reason = "refusing to activate session"`

Thanks,

---

<div class="post-metadata">

**Author:** ![omkensey](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/omkensey/32/40882_2.png) [@omkensey](https://discuss.hashicorp.com/u/omkensey)\
**Post date:** [September 5, 2022, 12:37am UTC](https://discuss.hashicorp.com/t/mysql-targets-not-working-after-boundary-0-10-3-upgrade/43888/2 "2022-09-05T00:37:24Z")

</div>

Did you run a `boundary database migrate` with the new version before running it as a controller?

---

<div class="post-metadata">

**Author:** ![ThomasKinow](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/thomaskinow/32/16852_2.png) [@ThomasKinow](https://discuss.hashicorp.com/u/ThomasKinow)\
**Post date:** [September 5, 2022, 7:18am UTC](https://discuss.hashicorp.com/t/mysql-targets-not-working-after-boundary-0-10-3-upgrade/43888/3 "2022-09-05T07:18:58Z")

</div>

Yes I did. As far as I remember the migration was successful.

Also http targets are working as usual (for example to target k8s eks api server through lens k8s ide).

---

<div class="post-metadata">

**Author:** ![jeff](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jeff/32/12882_2.png) [@jeff](https://discuss.hashicorp.com/u/jeff)\
**Post date:** [September 6, 2022, 3:06pm UTC](https://discuss.hashicorp.com/t/mysql-targets-not-working-after-boundary-0-10-3-upgrade/43888/4 "2022-09-06T15:06:37Z")

</div>

Quite possibly [refusing to activate session errors after upgrading to 0.10.1 · Issue #2362 · hashicorp/boundary · GitHub](https://github.com/hashicorp/boundary/issues/2362) which will be fixed in 0.10.4, out soon.

---

<div class="post-metadata">

**Author:** ![ThomasKinow](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/thomaskinow/32/16852_2.png) [@ThomasKinow](https://discuss.hashicorp.com/u/ThomasKinow)\
**Post date:** [September 14, 2022, 9:13am UTC](https://discuss.hashicorp.com/t/mysql-targets-not-working-after-boundary-0-10-3-upgrade/43888/5 "2022-09-14T09:13:41Z")

</div>

The problem disappeared while upgrading from 0.9.1 to **0.10.4**

Thanks!

---

<div class="post-metadata">

**Author:** ![jeff](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jeff/32/12882_2.png) [@jeff](https://discuss.hashicorp.com/u/jeff)\
**Post date:** [September 14, 2022, 2:00pm UTC](https://discuss.hashicorp.com/t/mysql-targets-not-working-after-boundary-0-10-3-upgrade/43888/6 "2022-09-14T14:00:09Z")

</div>

Awesome! Glad to hear it!