[🐛 Bug]: Grid saves empty selenium-server.log files for all sessions

[tpapaioa]

Description

On a dynamic Grid 4.41.0, the node fails to save selenium-server.log every session, leaving behind a 0-byte file. The Node container shows the following error each time:

15:00:40.890 INFO [Container.getLogs] - Getting logs 9317e1442a18ad0f79dd68bad27fb357eb24571beefdbe47372efab180ed0d0a
15:00:40.892 INFO [DockerClient.getContainerLogs] - Getting container logs: 9317e1442a18ad0f79dd68bad27fb357eb24571beefdbe47372efab180ed0d0a
15:00:40.913 WARN [DockerSession.saveLogs] - Error saving logs
java.lang.UnsupportedOperationException: Don't serialize binary stream - it might be large
       at org.openqa.selenium.remote.http.InputStreamContentSupplier.contentAsString(InputStreamContentSupplier.java:60)
       at org.openqa.selenium.remote.http.HttpMessage.contentAsString(HttpMessage.java:225)
       at org.openqa.selenium.remote.http.HttpResponse.contentAsString(HttpResponse.java:22)
       at org.openqa.selenium.remote.http.Contents.string(Contents.java:136)
       at org.openqa.selenium.docker.client.GetContainerLogs.apply(GetContainerLogs.java:55)
       at org.openqa.selenium.docker.client.DockerClient.getContainerLogs(DockerClient.java:163)
       at org.openqa.selenium.docker.Container.getLogs(Container.java:73)
       at org.openqa.selenium.grid.node.docker.DockerSession.saveLogs(DockerSession.java:77)
       at org.openqa.selenium.grid.node.docker.DockerSession.stop(DockerSession.java:68)
       at org.openqa.selenium.grid.node.DefaultActiveSession.execute(DefaultActiveSession.java:63)
       at org.openqa.selenium.grid.node.local.SessionSlot.execute(SessionSlot.java:180)
       at org.openqa.selenium.grid.node.local.LocalNode.executeWebDriverCommand(LocalNode.java:828)
       at org.openqa.selenium.grid.node.ForwardWebDriverCommand.execute(ForwardWebDriverCommand.java:48)
       at org.openqa.selenium.remote.http.Route$PredicatedRoute.handle(Route.java:398)
       at org.openqa.selenium.remote.http.Route.execute(Route.java:69)
       at org.openqa.selenium.remote.tracing.SpanWrappedHttpHandler.execute(SpanWrappedHttpHandler.java:87)
       at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63)
       at org.openqa.selenium.remote.http.Route$CombinedRoute.handle(Route.java:361)
       at org.openqa.selenium.remote.http.Route.execute(Route.java:69)
       at org.openqa.selenium.grid.node.Node.execute(Node.java:316)
       at org.openqa.selenium.remote.http.Route$CombinedRoute.handle(Route.java:361)
       at org.openqa.selenium.remote.http.Route.execute(Route.java:69)
       at org.openqa.selenium.remote.AddWebDriverSpecHeaders.lambda$apply$0(AddWebDriverSpecHeaders.java:35)
       at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0(ErrorFilter.java:44)
       at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63)
       at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0(ErrorFilter.java:44)
       at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63)
       at org.openqa.selenium.netty.server.SeleniumHandler.lambda$channelRead0$0(SeleniumHandler.java:49)
       at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
       at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
       at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
       at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
       at java.base/java.lang.Thread.run(Thread.java:1583)
15:00:40.914 INFO [Container.stop] - Stopping container 9317e1442a18ad0f79dd68bad27fb357eb24571beefdbe47372efab180ed0d0a

Reproducible Code

We're using quadlets instead of docker-compose, but it's a basic dynamic Grid on Linux:


# cat /etc/containers/systemd/selenium-grid.network 
[Network]
NetworkName=selenium-grid
IPv6=true


# cat /etc/containers/systemd/selenium-hub.container 
[Container]
ContainerName=selenium-hub
Image=docker.io/selenium/hub:4.41.0-20260222
Network=selenium-grid.network
PublishPort=4442:4442
PublishPort=4443:4443
PublishPort=4444:4444
PublishPort=[::]:4442:4442
PublishPort=[::]:4443:4443
PublishPort=[::]:4444:4444

[Unit]
StartLimitIntervalSec=30
StartLimitBurst=2

[Service]
Restart=always

[Install]
WantedBy=default.target

# cat /etc/containers/systemd/selenium-node.container 
[Container]
ContainerName=selenium-node
Environment=DOCKER_SOCK=/var/run/podman/podman.sock
Environment=SE_EVENT_BUS_HOST=selenium-hub
Environment=SE_VIDEO_RECORD_STANDALONE=true

Image=docker.io/selenium/node-docker:4.41.0-20260222
Network=selenium-grid.network
Volume=/root/config.toml:/opt/selenium/docker.toml
Volume=/var/run/podman/podman.sock:/var/run/docker.sock
Volume=/var/www/html/videos:/opt/selenium/assets
PodmanArgs=--privileged

[Unit]
StartLimitIntervalSec=30
StartLimitBurst=2
After=selenium-hub.service

[Service]
Restart=always

[Install]
WantedBy=default.target


# cat /root/config.toml 
[docker]
configs = [
  "selenium/standalone-firefox:4.41.0-20260222", '{"browserName": "firefox", "platformName": "linux"}',
  "selenium/standalone-chrome:4.41.0-20260222", '{"browserName": "chrome", "platformName": "linux"}',
  "selenium/standalone-edge:4.41.0-20260222", '{"browserName": "MicrosoftEdge", "platformName": "linux"}'
]
host-config-keys = ["Dns", "DnsOptions", "DnsSearch", "ExtraHosts", "Binds"]
url = "http://127.0.0.1:2375"
video-image = "selenium/video:ffmpeg-8.0-20260222"

[selenium-ci]

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

Selenium Triage Team: remember to follow the Triage Guide

[cgoldberg]

@tpapaioa I'm not sure if it's related, but this sounds similar to #17139 ... which was recently fixed and will be in the next release.