I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
Upgrading to .5.x from .4.8 works without issue while using postgres db
Actual Behavior:
All .5.x versions get stuck upgrading from .4.8, seems to have an issue with the channels table
Description
Bug Summary:
the container starts up and hangs when trying to run database migrations / updates
Reproduction Details
Steps to Reproduce:
Start with .4.8 on k8s installed via helm
use an postgres database (using cloudnative-pg operator version 1.24 and postgres DB version 16.4)
upgrade the helm chart from .4.8 to a .5.x version and watch it hang
Logs and Screenshots
Postgres database outputs no logs or errors
Docker Container Logs:
Going to .5.0, .5.1, .5.2, .5.3 all show the same output:
Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
Generating WEBUI_SECRET_KEY
Loading WEBUI_SECRET_KEY from .webui_secret_key
/app/backend/open_webui
/app/backend
/app
INFO:open_webui.env:GLOBAL_LOG_LEVEL: DEBUG
INFO:open_webui.env:AUDIO_LOG_LEVEL: DEBUG
INFO:open_webui.env:COMFYUI_LOG_LEVEL: DEBUG
INFO:open_webui.env:CONFIG_LOG_LEVEL: DEBUG
INFO:open_webui.env:DB_LOG_LEVEL: DEBUG
INFO:open_webui.env:IMAGES_LOG_LEVEL: DEBUG
INFO:open_webui.env:MAIN_LOG_LEVEL: DEBUG
INFO:open_webui.env:MODELS_LOG_LEVEL: DEBUG
INFO:open_webui.env:OLLAMA_LOG_LEVEL: DEBUG
INFO:open_webui.env:OPENAI_LOG_LEVEL: DEBUG
INFO:open_webui.env:RAG_LOG_LEVEL: DEBUG
INFO:open_webui.env:WEBHOOK_LOG_LEVEL: DEBUG
INFO:open_webui.env:SOCKET_LOG_LEVEL: DEBUG
INFO:open_webui.internal.wrappers:Connected to PostgreSQL database
INFO:open_webui.internal.db:Starting migrations
DEBUG:peewee:('CREATE TABLE IF NOT EXISTS "migratehistory" ("id" SERIAL NOT NULL PRIMARY KEY, "name" VARCHAR(255) NOT NULL, "migrated_at" TIMESTAMP NOT NULL)', [])
DEBUG:peewee:('SELECT "t1"."id", "t1"."name", "t1"."migrated_at" FROM "migratehistory" AS "t1" ORDER BY "t1"."id"', [])
INFO:open_webui.internal.db:There is nothing to migrate
DEBUG:passlib.utils.compat:loaded lazy attr 'SafeConfigParser': <class 'configparser.ConfigParser'>
DEBUG:passlib.utils.compat:loaded lazy attr 'NativeStringIO': <class '_io.StringIO'>
DEBUG:passlib.utils.compat:loaded lazy attr 'BytesIO': <class '_io.BytesIO'>
Running migrations
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
INFO [alembic.runtime.migration] Running upgrade 922e7a387820 -> 57c599a3cb57, Add channel table
Additional Information
Rolling back to 4.8 works fine to recover the instance
going from .4.8 to .5.3 on sqllite backend via docker on a single machine works fine. Problems started when testing k8s instance with postgres db
Originally created by @tkg61 on GitHub (Jan 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8276
# Bug Report
## Installation Method
helm
## Environment
- **Open WebUI Version:** .4.8 -> .5.x
- **Operating System:** k8s 1.29.4
**Confirmation:**
- [x] I have read and followed all the instructions provided in the README.md.
- [x] I am on the latest version of both Open WebUI and Ollama.
- [ ] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
Upgrading to .5.x from .4.8 works without issue while using postgres db
## Actual Behavior:
All .5.x versions get stuck upgrading from .4.8, seems to have an issue with the channels table
## Description
**Bug Summary:**
the container starts up and hangs when trying to run database migrations / updates
## Reproduction Details
**Steps to Reproduce:**
- Start with .4.8 on k8s installed via helm
- use an postgres database (using cloudnative-pg operator version 1.24 and postgres DB version 16.4)
- upgrade the helm chart from .4.8 to a .5.x version and watch it hang
## Logs and Screenshots
Postgres database outputs no logs or errors
**Docker Container Logs:**
### Going to .5.0, .5.1, .5.2, .5.3 all show the same output:
```
Loading WEBUI_SECRET_KEY from file, not provided as an environment variable.
Generating WEBUI_SECRET_KEY
Loading WEBUI_SECRET_KEY from .webui_secret_key
/app/backend/open_webui
/app/backend
/app
INFO:open_webui.env:GLOBAL_LOG_LEVEL: DEBUG
INFO:open_webui.env:AUDIO_LOG_LEVEL: DEBUG
INFO:open_webui.env:COMFYUI_LOG_LEVEL: DEBUG
INFO:open_webui.env:CONFIG_LOG_LEVEL: DEBUG
INFO:open_webui.env:DB_LOG_LEVEL: DEBUG
INFO:open_webui.env:IMAGES_LOG_LEVEL: DEBUG
INFO:open_webui.env:MAIN_LOG_LEVEL: DEBUG
INFO:open_webui.env:MODELS_LOG_LEVEL: DEBUG
INFO:open_webui.env:OLLAMA_LOG_LEVEL: DEBUG
INFO:open_webui.env:OPENAI_LOG_LEVEL: DEBUG
INFO:open_webui.env:RAG_LOG_LEVEL: DEBUG
INFO:open_webui.env:WEBHOOK_LOG_LEVEL: DEBUG
INFO:open_webui.env:SOCKET_LOG_LEVEL: DEBUG
INFO:open_webui.internal.wrappers:Connected to PostgreSQL database
INFO:open_webui.internal.db:Starting migrations
DEBUG:peewee:('CREATE TABLE IF NOT EXISTS "migratehistory" ("id" SERIAL NOT NULL PRIMARY KEY, "name" VARCHAR(255) NOT NULL, "migrated_at" TIMESTAMP NOT NULL)', [])
DEBUG:peewee:('SELECT "t1"."id", "t1"."name", "t1"."migrated_at" FROM "migratehistory" AS "t1" ORDER BY "t1"."id"', [])
INFO:open_webui.internal.db:There is nothing to migrate
DEBUG:passlib.utils.compat:loaded lazy attr 'SafeConfigParser': <class 'configparser.ConfigParser'>
DEBUG:passlib.utils.compat:loaded lazy attr 'NativeStringIO': <class '_io.StringIO'>
DEBUG:passlib.utils.compat:loaded lazy attr 'BytesIO': <class '_io.BytesIO'>
Running migrations
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
INFO [alembic.runtime.migration] Running upgrade 922e7a387820 -> 57c599a3cb57, Add channel table
```
## Additional Information
Rolling back to 4.8 works fine to recover the instance
going from .4.8 to .5.3 on sqllite backend via docker on a single machine works fine. Problems started when testing k8s instance with postgres db
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tkg61 on GitHub (Jan 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8276
Bug Report
Installation Method
helm
Environment
Open WebUI Version: .4.8 -> .5.x
Operating System: k8s 1.29.4
Confirmation:
Expected Behavior:
Upgrading to .5.x from .4.8 works without issue while using postgres db
Actual Behavior:
All .5.x versions get stuck upgrading from .4.8, seems to have an issue with the channels table
Description
Bug Summary:
the container starts up and hangs when trying to run database migrations / updates
Reproduction Details
Steps to Reproduce:
Logs and Screenshots
Postgres database outputs no logs or errors
Docker Container Logs:
Going to .5.0, .5.1, .5.2, .5.3 all show the same output:
Additional Information
Rolling back to 4.8 works fine to recover the instance
going from .4.8 to .5.3 on sqllite backend via docker on a single machine works fine. Problems started when testing k8s instance with postgres db