langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-26 18:36:52 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The database did not start after upgrading from v1.10.1 to the main branch #20873

New Issue
Closed
opened 2026-02-21 20:09:37 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 20:09:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @Tabll on GitHub (Dec 8, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.10.1-fix.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Based on the solution suggested in https://github.com/langgenius/dify/issues/29278, it seems I should use the latest docker-compose.yaml file on the main branch.

However, after I switched to the main branch from v1.10.1 for deployment, I found that the database did not start.

Below is a list of started containers:

[+] up 12/12
 ✔ Network docker_ssrf_proxy_network Created                                                                                                                            0.0s 
 ✔ Network docker_default            Created                                                                                                                            0.0s 
 ✔ Container docker-redis-1          Created                                                                                                                            0.1s 
 ✔ Container docker-sandbox-1        Created                                                                                                                            0.1s 
 ✔ Container docker-weaviate-1       Created                                                                                                                            0.1s 
 ✔ Container docker-web-1            Created                                                                                                                            0.1s 
 ✔ Container docker-ssrf_proxy-1     Created                                                                                                                            0.1s 
 ✔ Container docker-plugin_daemon-1  Created                                                                                                                            0.1s 
 ✔ Container docker-worker_beat-1    Created                                                                                                                            0.1s 
 ✔ Container docker-worker-1         Created                                                                                                                            0.1s 
 ✔ Container docker-api-1            Created                                                                                                                            0.1s 
 ✔ Container docker-nginx-1          Created                                                                                                                            0.0s

The log in docker-nginx-1

2025/12/09 02:30:44 [emerg] 10#10: host not found in upstream "plugin_daemon" in /etc/nginx/conf.d/default.conf:33

The log in docker-plugin_daemon-1

2025/12/09 02:41:36 init.go:99: [PANIC]failed to init dify plugin db: failed to connect to `host=db user=postgres database=postgres`: hostname resolving error (lookup db on 127.0.0.11:53: server misbehaving)

panic: [PANIC]failed to init dify plugin db: failed to connect to `host=db user=postgres database=postgres`: hostname resolving error (lookup db on 127.0.0.11:53: server misbehaving)

goroutine 1 [running]:

github.com/langgenius/dify-plugin-daemon/internal/utils/log.writeLog({0x268e7b3, 0x5}, {0x26d5ab4?, 0x21c0a38?}, 0x1, {0xc000343ba0, 0x1, 0x1})

	/app/internal/utils/log/log.go:40 +0x305

github.com/langgenius/dify-plugin-daemon/internal/utils/log.Panic(...)

	/app/internal/utils/log/log.go:66

github.com/langgenius/dify-plugin-daemon/internal/db.Init(0x2710?)

	/app/internal/db/init.go:99 +0x416

github.com/langgenius/dify-plugin-daemon/internal/server.(*App).Run(0xc000302ee8, 0xc0005e8008)

	/app/internal/server/server.go:94 +0xd2

main.main()

	/app/cmd/server/main.go:28 +0x125

✔️ Expected Behavior

According to the security issue prompts in https://github.com/langgenius/dify/issues/29277 and https://github.com/langgenius/dify/issues/29278

❌ Actual Behavior

I did not modify any configuration files.
It was just a branch switch for the upgrade.
But no database container started.

Originally created by @Tabll on GitHub (Dec 8, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.10.1-fix.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Based on the solution suggested in https://github.com/langgenius/dify/issues/29278, it seems I should use the latest docker-compose.yaml file on the main branch. However, after I switched to the main branch from v1.10.1 for deployment, I found that the database did not start. Below is a list of started containers: ```sh [+] up 12/12 ✔ Network docker_ssrf_proxy_network Created 0.0s ✔ Network docker_default Created 0.0s ✔ Container docker-redis-1 Created 0.1s ✔ Container docker-sandbox-1 Created 0.1s ✔ Container docker-weaviate-1 Created 0.1s ✔ Container docker-web-1 Created 0.1s ✔ Container docker-ssrf_proxy-1 Created 0.1s ✔ Container docker-plugin_daemon-1 Created 0.1s ✔ Container docker-worker_beat-1 Created 0.1s ✔ Container docker-worker-1 Created 0.1s ✔ Container docker-api-1 Created 0.1s ✔ Container docker-nginx-1 Created 0.0s ``` The log in `docker-nginx-1` ``` 2025/12/09 02:30:44 [emerg] 10#10: host not found in upstream "plugin_daemon" in /etc/nginx/conf.d/default.conf:33 ``` The log in `docker-plugin_daemon-1` ```log 2025/12/09 02:41:36 init.go:99: [PANIC]failed to init dify plugin db: failed to connect to `host=db user=postgres database=postgres`: hostname resolving error (lookup db on 127.0.0.11:53: server misbehaving) panic: [PANIC]failed to init dify plugin db: failed to connect to `host=db user=postgres database=postgres`: hostname resolving error (lookup db on 127.0.0.11:53: server misbehaving) goroutine 1 [running]: github.com/langgenius/dify-plugin-daemon/internal/utils/log.writeLog({0x268e7b3, 0x5}, {0x26d5ab4?, 0x21c0a38?}, 0x1, {0xc000343ba0, 0x1, 0x1}) /app/internal/utils/log/log.go:40 +0x305 github.com/langgenius/dify-plugin-daemon/internal/utils/log.Panic(...) /app/internal/utils/log/log.go:66 github.com/langgenius/dify-plugin-daemon/internal/db.Init(0x2710?) /app/internal/db/init.go:99 +0x416 github.com/langgenius/dify-plugin-daemon/internal/server.(*App).Run(0xc000302ee8, 0xc0005e8008) /app/internal/server/server.go:94 +0xd2 main.main() /app/cmd/server/main.go:28 +0x125 ``` ### ✔️ Expected Behavior According to the security issue prompts in https://github.com/langgenius/dify/issues/29277 and https://github.com/langgenius/dify/issues/29278 ### ❌ Actual Behavior I did not modify any configuration files. It was just a branch switch for the upgrade. But no database container started.
yindo added the 🐞 bug label 2026-02-21 20:09:37 -05:00
yindo closed this issue 2026-02-21 20:09:37 -05:00
yindo commented 2026-02-21 20:09:37 -05:00
Author
Owner
Copy Link
Copy Source

@JokerQyou commented on GitHub (Dec 8, 2025):

I think postgresql database service name was changed from db to db_postgres in order to support multiple databases (MySQL, etc.). After pulling latest code from main branch please refer to .env.example and edit your .env file, and change to DB_HOST=db_postgres and COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-postgresql}. (Yes, database type is also configured via compose profile now)

@JokerQyou commented on GitHub (Dec 8, 2025): I think postgresql database service name was changed from `db` to `db_postgres` in order to support multiple databases (MySQL, etc.). After pulling latest code from `main` branch please refer to `.env.example` and edit your `.env` file, and change to `DB_HOST=db_postgres` and `COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-postgresql}`. (Yes, database type is also configured via compose profile now)
yindo commented 2026-02-21 20:09:37 -05:00
Author
Owner
Copy Link
Copy Source

@Tabll commented on GitHub (Dec 8, 2025):

Editing the .env file also had no effect.
The command to start the entire service has been modified to:

docker compose --profile postgresql up -d
@Tabll commented on GitHub (Dec 8, 2025): Editing the `.env` file also had no effect. The command to start the entire service has been modified to: ```sh docker compose --profile postgresql up -d ```
yindo commented 2026-02-21 20:09:37 -05:00
Author
Owner
Copy Link
Copy Source

@JokerQyou commented on GitHub (Dec 8, 2025):

Editing the .env file also had no effect.

It actually has effect. If you read it carefully you would notice this: COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-postgresql} which sets COMPOSE_PROFILES to weaviate,postgresql by default. You can also override by setting DB_TYPE to postgresql. After that docker compose command would automatically set correseponding profiles when invoked.

@JokerQyou commented on GitHub (Dec 8, 2025): > Editing the `.env` file also had no effect. It actually has effect. If you read it carefully you would notice this: `COMPOSE_PROFILES=${VECTOR_STORE:-weaviate},${DB_TYPE:-postgresql}` which sets `COMPOSE_PROFILES` to `weaviate,postgresql` by default. You can also override by setting `DB_TYPE` to `postgresql`. After that `docker compose` command would automatically set correseponding profiles when invoked.
yindo commented 2026-02-21 20:09:37 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 9, 2025):

Editing the .env file also had no effect. The command to start the entire service has been modified to:

docker compose --profile postgresql up -d

https://github.com/langgenius/dify/releases/tag/1.10.1

Image
@crazywoola commented on GitHub (Dec 9, 2025): > Editing the `.env` file also had no effect. The command to start the entire service has been modified to: > > docker compose --profile postgresql up -d https://github.com/langgenius/dify/releases/tag/1.10.1 <img width="2402" height="696" alt="Image" src="https://github.com/user-attachments/assets/f16d79d0-8bcd-402c-8a2f-d51aba0931a1" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#20873
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?