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

After upgrade to v1.3.0, my entire datebase is missing #13296

New Issue
Closed
opened 2026-02-21 19:11:30 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:11:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @EscaticZheng on GitHub (Apr 24, 2025).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.3.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I delete the volumes file in dify/docker in version 1.0.1, then "sudo tar -xvf volumes-1745473810.tgz" to generate backup volumes, after upgrade to 1.3.0, everything is gone? I have to create new system account? Though in dify/api log, it shows data migration is success. And I can find my data in /app/api/storage.

Image

Image

✔️ Expected Behavior

It should have migrated all my accounts, plugins, and knowledge bases, but it didn't.

❌ Actual Behavior

Image

Image

Originally created by @EscaticZheng on GitHub (Apr 24, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.3.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I delete the volumes file in dify/docker in version 1.0.1, then "sudo tar -xvf volumes-1745473810.tgz" to generate backup volumes, after upgrade to 1.3.0, everything is gone? I have to create new system account? Though in dify/api log, it shows data migration is success. And I can find my data in /app/api/storage. ![Image](https://github.com/user-attachments/assets/d418412b-9ec7-4e14-8bbe-84bb22ab0661) ![Image](https://github.com/user-attachments/assets/a309da39-31cf-4681-a39d-6c0329b5667b) ### ✔️ Expected Behavior It should have migrated all my accounts, plugins, and knowledge bases, but it didn't. ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/363b8fd9-d73a-41aa-b184-15f5bdd20ad3) ![Image](https://github.com/user-attachments/assets/3f9322a5-a610-4554-bc5f-a4d8e3daa6bb)
yindo added the 🐞 bug label 2026-02-21 19:11:30 -05:00
yindo closed this issue 2026-02-21 19:11:30 -05:00
yindo commented 2026-02-21 19:11:31 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 24, 2025):

Hello @EscaticZheng! I'm Dosu, your friendly bot here to help you with bugs, questions, and becoming a contributor. I'll be assisting you while you wait for a human maintainer. How can I help you today?

I found a similar unsolved discussion titled "备份迁移的数据后，新服务器没有数据" which translates to "After backing up and migrating data, the new server has no data" [1]. This might be related to your issue of missing data after the upgrade.

For your specific issue, it seems like the data migration process indicated success, but the data is not visible in the application. Here are some steps you can take to troubleshoot:

  1. Verify Data Location: Ensure that the data is correctly extracted to the expected directories, such as ./volumes/db/data for PostgreSQL, ./volumes/redis/data for Redis, and ./volumes/app/storage for API and Worker services.

  2. Check Docker Volumes: Make sure that the Docker volumes are correctly mounted and that the data is accessible within the containers. You can inspect the volumes using Docker commands to verify their contents.

  3. Database Connection: Confirm that the application is correctly connecting to the database. Check the database connection settings in your configuration files to ensure they are pointing to the correct database instance.

  4. Logs and Errors: Review the logs for any errors or warnings that might indicate issues with data access or migration. The logs can provide insights into what might be going wrong.

  5. Data Integrity: If possible, manually inspect the database to see if the data is present but not being displayed in the application. This can help determine if the issue is with data visibility rather than data loss.

If these steps do not resolve the issue, you might need to consider restoring from a backup and attempting the migration again, ensuring all steps are followed precisely.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 24, 2025): <!-- Greeting --> Hello @EscaticZheng! I'm [Dosu](https://dosu.dev), your friendly bot here to help you with bugs, questions, and becoming a contributor. I'll be assisting you while you wait for a human maintainer. How can I help you today? <!-- Answer --> I found a similar unsolved discussion titled "[备份迁移的数据后，新服务器没有数据](https://github.com/langgenius/dify/discussions/15928)" which translates to "After backing up and migrating data, the new server has no data" <sup>[[1]](https://github.com/langgenius/dify/discussions/15928)</sup>. This might be related to your issue of missing data after the upgrade. For your specific issue, it seems like the data migration process indicated success, but the data is not visible in the application. Here are some steps you can take to troubleshoot: 1. **Verify Data Location**: Ensure that the data is correctly extracted to the expected directories, such as `./volumes/db/data` for PostgreSQL, `./volumes/redis/data` for Redis, and `./volumes/app/storage` for API and Worker services. 2. **Check Docker Volumes**: Make sure that the Docker volumes are correctly mounted and that the data is accessible within the containers. You can inspect the volumes using Docker commands to verify their contents. 3. **Database Connection**: Confirm that the application is correctly connecting to the database. Check the database connection settings in your configuration files to ensure they are pointing to the correct database instance. 4. **Logs and Errors**: Review the logs for any errors or warnings that might indicate issues with data access or migration. The logs can provide insights into what might be going wrong. 5. **Data Integrity**: If possible, manually inspect the database to see if the data is present but not being displayed in the application. This can help determine if the issue is with data visibility rather than data loss. If these steps do not resolve the issue, you might need to consider restoring from a backup and attempting the migration again, ensuring all steps are followed precisely. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=other)</sup>
yindo commented 2026-02-21 19:11:31 -05:00
Author
Owner
Copy Link
Copy Source

@EscaticZheng commented on GitHub (Apr 24, 2025):

Hello @EscaticZheng! I'm Dosu, your friendly bot here to help you with bugs, questions, and becoming a contributor. I'll be assisting you while you wait for a human maintainer. How can I help you today?

I found a similar unsolved discussion titled "备份迁移的数据后，新服务器没有数据" which translates to "After backing up and migrating data, the new server has no data" [1]. This might be related to your issue of missing data after the upgrade.

For your specific issue, it seems like the data migration process indicated success, but the data is not visible in the application. Here are some steps you can take to troubleshoot:

  1. Verify Data Location: Ensure that the data is correctly extracted to the expected directories, such as ./volumes/db/data for PostgreSQL, ./volumes/redis/data for Redis, and ./volumes/app/storage for API and Worker services.
  2. Check Docker Volumes: Make sure that the Docker volumes are correctly mounted and that the data is accessible within the containers. You can inspect the volumes using Docker commands to verify their contents.
  3. Database Connection: Confirm that the application is correctly connecting to the database. Check the database connection settings in your configuration files to ensure they are pointing to the correct database instance.
  4. Logs and Errors: Review the logs for any errors or warnings that might indicate issues with data access or migration. The logs can provide insights into what might be going wrong.
  5. Data Integrity: If possible, manually inspect the database to see if the data is present but not being displayed in the application. This can help determine if the issue is with data visibility rather than data loss.

If these steps do not resolve the issue, you might need to consider restoring from a backup and attempting the migration again, ensuring all steps are followed precisely.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

I think the issue is that the backup of the volumes is not working. Every time I delete the volumes, regardless of the version, it starts creating accounts from scratch.

@EscaticZheng commented on GitHub (Apr 24, 2025): > Hello [@EscaticZheng](https://github.com/EscaticZheng)! I'm [Dosu](https://dosu.dev), your friendly bot here to help you with bugs, questions, and becoming a contributor. I'll be assisting you while you wait for a human maintainer. How can I help you today? > > I found a similar unsolved discussion titled "[备份迁移的数据后，新服务器没有数据](https://github.com/langgenius/dify/discussions/15928)" which translates to "After backing up and migrating data, the new server has no data" [[1]](https://github.com/langgenius/dify/discussions/15928). This might be related to your issue of missing data after the upgrade. > > For your specific issue, it seems like the data migration process indicated success, but the data is not visible in the application. Here are some steps you can take to troubleshoot: > > 1. **Verify Data Location**: Ensure that the data is correctly extracted to the expected directories, such as `./volumes/db/data` for PostgreSQL, `./volumes/redis/data` for Redis, and `./volumes/app/storage` for API and Worker services. > 2. **Check Docker Volumes**: Make sure that the Docker volumes are correctly mounted and that the data is accessible within the containers. You can inspect the volumes using Docker commands to verify their contents. > 3. **Database Connection**: Confirm that the application is correctly connecting to the database. Check the database connection settings in your configuration files to ensure they are pointing to the correct database instance. > 4. **Logs and Errors**: Review the logs for any errors or warnings that might indicate issues with data access or migration. The logs can provide insights into what might be going wrong. > 5. **Data Integrity**: If possible, manually inspect the database to see if the data is present but not being displayed in the application. This can help determine if the issue is with data visibility rather than data loss. > > If these steps do not resolve the issue, you might need to consider restoring from a backup and attempting the migration again, ensuring all steps are followed precisely. > > _To continue talking to [Dosu](https://dosu.dev), mention [@dosu](https://github.com/dosu)._ > > Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/28e105f4-8dd7-4e52-bd7e-00ccfc4ccdd0?feedback_type=other) I think the issue is that the backup of the volumes is not working. Every time I delete the volumes, regardless of the version, it starts creating accounts from scratch.
yindo commented 2026-02-21 19:11:31 -05:00
Author
Owner
Copy Link
Copy Source

@EscaticZheng commented on GitHub (Apr 24, 2025):

I understand now. The reason is that I didn't use sudo permissions when tar, which resulted in the files under db/data not being copied over, so they all disappeared.

@EscaticZheng commented on GitHub (Apr 24, 2025): I understand now. The reason is that I didn't use sudo permissions when tar, which resulted in the files under db/data not being copied over, so they all disappeared.
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#13296
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?