[GH-ISSUE #40] issue: INFO logging despite TERMINALS_LOG_LEVEL set to WARNING #16

New issue

Closed

opened 2026-10-18 21:13:25 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-18 21:13:25 +00:00

Owner

Originally created by @Classic298 on GitHub (Jul 15, 2026).
Original GitHub issue: https://github.com/open-webui/terminals/issues/40

terminals-ai-computer  | INFO:     172.30.0.2:46260 - "GET /ports HTTP/1.1" 200 OK
terminals-ai-computer  | INFO:     172.30.0.2:59486 - "GET /ports HTTP/1.1" 200 OK
terminals-ai-computer  | INFO:     172.30.0.2:33796 - "GET /ports HTTP/1.1" 200 OK
terminals-ai-computer  | INFO:     172.30.0.2:50020 - "GET /ports HTTP/1.1" 200 OK
terminals-ai-computer  | INFO:     172.30.0.2:43798 - "GET /ports HTTP/1.1" 200 OK
terminals-ai-computer  | INFO:     172.30.0.2:57520 - "GET /ports HTTP/1.1" 200 OK

TERMINALS_LOG_LEVEL is set to WARNING and even then INFO is being logged across the individual user's open-terminal container

Originally created by @Classic298 on GitHub (Jul 15, 2026). Original GitHub issue: https://github.com/open-webui/terminals/issues/40 ``` terminals-ai-computer | INFO: 172.30.0.2:46260 - "GET /ports HTTP/1.1" 200 OK terminals-ai-computer | INFO: 172.30.0.2:59486 - "GET /ports HTTP/1.1" 200 OK terminals-ai-computer | INFO: 172.30.0.2:33796 - "GET /ports HTTP/1.1" 200 OK terminals-ai-computer | INFO: 172.30.0.2:50020 - "GET /ports HTTP/1.1" 200 OK terminals-ai-computer | INFO: 172.30.0.2:43798 - "GET /ports HTTP/1.1" 200 OK terminals-ai-computer | INFO: 172.30.0.2:57520 - "GET /ports HTTP/1.1" 200 OK ``` TERMINALS_LOG_LEVEL is set to WARNING and even then INFO is being logged across the individual user's open-terminal container

bsakaguchi closed this issue

2026-10-18 21:13:25 +00:00

bsakaguchi commented

2026-10-18 21:13:26 +00:00

Author

Owner

@owui-terminator[bot] commented on GitHub (Jul 15, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

🟣 #21 feat: make log level configurable
This is the only directly related issue found: it requested making the log level configurable, which is the same area implicated by #40 where TERMINALS_LOG_LEVEL is expected to suppress INFO logs but does not. Even though #21 is broad, it covers the logging configuration behavior at issue here.
by Classic298

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

@owui-terminator[bot] commented on GitHub (Jul 15, 2026):  🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#21](https://github.com/open-webui/terminals/issues/21) **feat: make log level configurable** *This is the only directly related issue found: it requested making the log level configurable, which is the same area implicated by #40 where TERMINALS_LOG_LEVEL is expected to suppress INFO logs but does not. Even though #21 is broad, it covers the logging configuration behavior at issue here.* *by Classic298* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.

bsakaguchi referenced this issue

2026-10-18 21:13:46 +00:00

[PR #16] [MERGED] fix: auto-recover errored terminal CRs in operator backend #49