# Version 4.4 Upgrade issue mariadb unhealthy

**URL:** <https://forum.seatable.com/t/version-4-4-upgrade-issue-mariadb-unhealthy/3345>\
**Category:** Upgrade\
**Created:** [April 1, 2024, 5:37pm UTC](https://forum.seatable.com/t/version-4-4-upgrade-issue-mariadb-unhealthy/3345 "2024-04-01T17:37:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pascal](https://forum.seatable.com/letter_avatar_proxy/v4/letter/p/e9a140/32.png) [@pascal](https://forum.seatable.com/u/pascal)\
**Post date:** [April 1, 2024, 5:37pm UTC](https://forum.seatable.com/t/version-4-4-upgrade-issue-mariadb-unhealthy/3345/1 "2024-04-01T17:37:36Z")

</div>

Hello all,  
after following all steps carefully, the seatable server 4.4 (enterprise) is still not willing to start:

 ![seatable upgrade error](https://forum.seatable.io/uploads/default/original/2X/8/8eaa32adbed35ee0a1a1836ce1af2d5a9fbced37.png)  
Any help would be appreciated.

---

<div class="post-metadata">

**Author:** ![rdb](https://forum.seatable.com/user_avatar/forum.seatable.com/rdb/32/1869_2.png) [@rdb](https://forum.seatable.com/u/rdb)\
**Post date:** [April 1, 2024, 6:14pm UTC](https://forum.seatable.com/t/version-4-4-upgrade-issue-mariadb-unhealthy/3345/2 "2024-04-01T18:14:00Z")

</div>

You deploy an unofficial test version. Hence no support from the official side

---

<div class="post-metadata">

**Author:** ![pascal](https://forum.seatable.com/letter_avatar_proxy/v4/letter/p/e9a140/32.png) [@pascal](https://forum.seatable.com/u/pascal)\
**Post date:** [April 2, 2024, 6:36pm UTC](https://forum.seatable.com/t/version-4-4-upgrade-issue-mariadb-unhealthy/3345/3 "2024-04-02T18:36:27Z")

</div>

How can it be an unofficial test version, given that the latest seatable (enterprise) image on dockerhub is 4.3.10. When looking in the admin manual, it states:

> “With version 4.3 we introduced a new way to install, update and maintain a SeaTable server. Before 4.3 you used to have one big docker-compose.yml. Even if it not mandatory to switch this setup, but we recommend it. Please check out this [article for more details](https://admin.seatable.io/upgrade/migrate_seatable_release/).”

Which are exactly the steps I followed.

---

<div class="post-metadata">

**Author:** ![rdb](https://forum.seatable.com/user_avatar/forum.seatable.com/rdb/32/1869_2.png) [@rdb](https://forum.seatable.com/u/rdb)\
**Post date:** [April 2, 2024, 6:59pm UTC](https://forum.seatable.com/t/version-4-4-upgrade-issue-mariadb-unhealthy/3345/4 "2024-04-02T18:59:53Z")

</div>

> [@pascal](#):
>
> the seatable server 4.4 (enterprise)

vs.

> [@pascal](#):
>
> given that the latest seatable (enterprise) image on dockerhub is 4.3.10.

Your words. Nothing to add.

---

<div class="post-metadata">

**Author:** ![system](https://forum.seatable.com/uploads/default/original/1X/04603423fe81a46c321283663086c475429e8ccb.png) [@system](https://forum.seatable.com/u/system)\
**Post date:** [April 4, 2024, 7:00pm UTC](https://forum.seatable.com/t/version-4-4-upgrade-issue-mariadb-unhealthy/3345/5 "2024-04-04T19:00:48Z")

</div>

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