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

Celery worker and beat fail when LOG_LEVEL is unset #7904

New Issue
Closed
opened 2026-02-21 18:22:58 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:22:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @osaimi on GitHub (Jan 27, 2025).

Self Checks

  • 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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

When LOG_LEVEL is not set, Celery worker and beat processes fail to start with the following error:

Usage: celery worker [OPTIONS]
Try 'celery worker --help' for help.

Error: Invalid value for '-l' / '--loglevel': '-Q' is not one of 'DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL', 'FATAL'.

Most environment variables in entrypoint.sh have default values, but LOG_LEVEL does not. I propose adding a default value for LOG_LEVEL to ensure consistency and to prevent container failures when the variable is not explicitly set.

2. Additional context or comments

I previously submitted a PR https://github.com/langgenius/dify/pull/13066 to address this issue, but it was closed because no issue was opened first. I am happy to open a new PR to address this problem once this issue is acknowledged.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @osaimi on GitHub (Jan 27, 2025). ### Self Checks - [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. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. When LOG_LEVEL is not set, Celery worker and beat processes fail to start with the following error: ``` Usage: celery worker [OPTIONS] Try 'celery worker --help' for help. Error: Invalid value for '-l' / '--loglevel': '-Q' is not one of 'DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL', 'FATAL'. ``` Most environment variables in entrypoint.sh have default values, but LOG_LEVEL does not. I propose adding a default value for LOG_LEVEL to ensure consistency and to prevent container failures when the variable is not explicitly set. ### 2. Additional context or comments I previously submitted a PR https://github.com/langgenius/dify/pull/13066 to address this issue, but it was closed because no issue was opened first. I am happy to open a new PR to address this problem once this issue is acknowledged. ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 🐞 bug label 2026-02-21 18:22:58 -05:00
yindo closed this issue 2026-02-21 18:22:58 -05:00
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#7904
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?