Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[🐛 Bug]: selenium-server v4.28.0 writes log on stdout instead of dedicated log file #15176

Closed
zefkide opened this issue Jan 28, 2025 · 3 comments
Assignees

Comments

@zefkide
Copy link

zefkide commented Jan 28, 2025

What happened?

Hello

I'm running selenium grid in hub and nodes architecture. Configuration is in toml files. Logging section is (pretty standard) :

[logging]
log-encoding = "UTF-8"
log-file = "/var/log/selenium/sel4hub.log"
log-level = "INFO"
plain-logs = true
structured-logs = false

When I start the hub or a node with the jar v4.27 the output goes to log file /var/log/selenium/sel4hub.log but when I use version v28 the output goes to stdout and nothing is wrote in the log file.

HUB : java -jar selenium-server-4.28.0.jar hub --config config.toml
NODE : java -jar selenium-server-4.28.0.jar node --config config.toml
java -version
openjdk version "17.0.13" 2024-10-15 LTS

Best regards,
Marius

How can we reproduce the issue?

java -jar selenium-server-4.28.0.jar standalone --log /var/log/selenium/test.log

Relevant log output

log goes to stdout

Operating System

RH9

Selenium version

4.28.0

What are the browser(s) and version(s) where you see this issue?

chrome 132.0.6834.110

What are the browser driver(s) and version(s) where you see this issue?

132.0.6834.110

Are you using Selenium Grid?

4.28.0

Copy link

@zefkide, 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!

@pujagani
Copy link
Contributor

Thank you for sharing the details. I was able to reproduce it. It was caused by the changes made as part of 16b0074. I am identifying the right solution to fix it.

@Delta456
Copy link
Contributor

Delta456 commented Feb 3, 2025

This issue can be closed as #15197 has been merged which has the fix for this.

@diemol diemol closed this as completed Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants