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

After the API is called, the management backend cannot see the log #6897

New Issue
Closed
opened 2026-02-21 18:17:52 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:17:52 -05:00
Owner
Copy Link
Copy Source

Originally created by @JiesenSun on GitHub (Nov 22, 2024).

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

V0.11.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

As shown in the figure, there is no log after the API is successfully called

image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @JiesenSun on GitHub (Nov 22, 2024). ### 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 V0.11.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce As shown in the figure, there is no log after the API is successfully called ![image](https://github.com/user-attachments/assets/1bfee82f-a317-4503-a877-cab577bc430e) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:17:52 -05:00
yindo closed this issue 2026-02-21 18:17:52 -05:00
yindo commented 2026-02-21 18:17:52 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 22, 2024):

I found some similar discussions and issues that might be relevant to your problem:

  1. No record was found in the API call log - This discussion is unsolved and was last updated on November 15, 2024 [1].

  2. DIY API interface call, unable to parse context - Another unsolved discussion, last updated on October 30, 2024 [2].

Additionally, there was a closed issue related to logging in Docker Compose for version 0.6.9, which might provide some insights. The suggested solution involved initializing the logging configuration before any other log configurations are executed. You can find the details of this solution in the issue here [3].

For version 0.11.2, the logging level is set to INFO by default, as specified in the docker-compose.yaml file [4]. If you're not seeing logs, you might want to check if the log level is set correctly and ensure that the log file location is properly configured. The default log file location is not explicitly set, so it defaults to an empty value unless specified otherwise [5].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 22, 2024): <!-- Answer --> I found some similar discussions and issues that might be relevant to your problem: 1. [No record was found in the API call log](https://github.com/langgenius/dify/discussions/10751) - This discussion is unsolved and was last updated on November 15, 2024 <sup>[[1]](https://github.com/langgenius/dify/discussions/10751)</sup>. 2. [DIY API interface call, unable to parse context](https://github.com/langgenius/dify/discussions/10044) - Another unsolved discussion, last updated on October 30, 2024 <sup>[[2]](https://github.com/langgenius/dify/discussions/10044)</sup>. Additionally, there was a closed issue related to logging in Docker Compose for version 0.6.9, which might provide some insights. The suggested solution involved initializing the logging configuration before any other log configurations are executed. You can find the details of this solution in the issue [here](https://github.com/langgenius/dify/issues/4990) <sup>[[3]](https://github.com/langgenius/dify/issues/4990)</sup>. For version 0.11.2, the logging level is set to `INFO` by default, as specified in the `docker-compose.yaml` file <sup>[[4]](https://github.com/langgenius/dify/blob/main/docker-legacy/docker-compose.yaml)</sup>. If you're not seeing logs, you might want to check if the log level is set correctly and ensure that the log file location is properly configured. The default log file location is not explicitly set, so it defaults to an empty value unless specified otherwise <sup>[[5]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:17:53 -05:00
Author
Owner
Copy Link
Copy Source

@JiesenSun commented on GitHub (Nov 22, 2024):

Bug Report

@JiesenSun commented on GitHub (Nov 22, 2024): Bug Report
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 🤔 cant-reproduce
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#6897
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?