[🐛 Bug]: Confusing log statement about the log level

[MJB222398]

What happened?

For my Hub and Nodes I set the environment variable for logging as follows:

SE_OPTS=--log-level CONFIG

But if I look in the logs for the nodes/hub then I see:

2025-04-08 17:00:46,956 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Appending Selenium options: --log-level CONFIG
Appending Selenium option: --port 4444
Selenium option: --log-level already set in env variable SE_OPTS. Ignore new option: --log-level INFO

Where is this INFO log level coming from? Pretty sure its not me setting it. If it's not me who has set it why is it mentioning it?

Command used to start Selenium Grid with Docker (or Kubernetes)

N/A

Relevant log output

N/A

Operating System

Ubuntu 20.04

Docker Selenium version (image tag)

4.31.0-20250404

Selenium Grid chart version (chart version)

No response

[github-actions]

@MJB222398, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

List env var https://github.com/SeleniumHQ/docker-selenium/blob/trunk/ENV_VARIABLES.md
SE_LOG_LEVEL represent for CLI option --log-level and it set INFO as default
To avoid duplicated config that might be input by user via SE_OPTS and existing env vars. So, config in SE_OPTS will be prioritised, and default env var will be skipped.

[MJB222398]

OK, I see, so I can avoid this message by just using SE_LOG_LEVEL=CONFIG instead. I think it was the fact that is said 'new option' that confused me, its not really a 'new' option, just the default?

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.