[🐛 Bug]: Possile that Selenium Manager Might not be working as expected

[francoisdejgr]

Description

Not sure if this is the right place to report or if this is a bug

Either the Selenium Manager is not putting the chrome / gecko driver in the correct place or it is missing a parameter.

Using Jmeter with jp@gc - Remote Driver Config 
Started Hub with : java -jar selenium-server-4.39.0.jar hub
Started Node with : java -jar selenium-server-4.39.0.jar node   --selenium-manager true
In Jmeter I access the hub : http://---:4444/wd/hub
Remote Browser : Firefox and Chrome

I expect the web page to open.

I get:
Node Window:

13:39:37.524 INFO [NodeServer.execute] - Started Selenium node 4.39.0 (revision 126f156aee): http://-----:5555
13:39:37.543 INFO [NodeServer$2.lambda$start$2] - Sending registration event...
13:39:38.201 INFO [NodeServer.lambda$createHandlers$2] - Node has been added

Hub Window

13:38:57.828 INFO [Hub.execute] - Started Selenium Hub 4.39.0 (revision 126f156aee): http://---:4444
13:39:37.597 INFO [Node.<init>] - Binding additional locator mechanisms: relative
13:39:38.190 INFO [LocalGridModel.setAvailability] - Switching Node 7c3b7a7c-6c23-46de-b055-a300d9ccc29b (uri: http://-----:5555) from DOWN to UP
13:39:38.191 INFO [LocalNodeRegistry.add] - Added node 7c3b7a7c-6c23-46de-b055-a300d9ccc29b at http://---:5555. Health check every 120s

After I start the JMeter Test I see in the HUB window

13:41:48.021 INFO [LocalDistributor.newSession] - Session request received by the Distributor:
 [Capabilities {acceptInsecureCerts: true, browserName: chrome, goog:chromeOptions: {args: [--remote-allow-origins=*], extensions: []}, proxy: {proxyType: system}}]
13:41:48.202 WARN [SeleniumSpanExporter$1.lambda$export$3] - {"traceId": "bce189d7e14a8f525cf3f5a36a9db031","eventTime": 1768304508021103000,"eventName": "Session request received by the Distributor","attributes": {"logger": "org.openqa.selenium.grid.distributor.local.LocalDistributor","request.payload": "[Capabilities {acceptInsecureCerts: true, browserName: chrome, goog:chromeOptions: {args: [--remote-allow-origins=*], extensions: []}, proxy: {proxyType: system}}]"}}

13:41:48.202 WARN [SeleniumSpanExporter$1.lambda$export$1] - Unable to create session: Could not start a new session. Could not start a new session. Error while creating session with the driver service. **Unable to obtain: chromedriver**, error Command failed with code: 2, executed: [--browser, chrome, --proxy, --language-binding, java, --output, json]
**error: a value is required for '--proxy <PROXY>' but none was supplied**

For more information, try '--help'.

Host info: host: '---', ip: '--'
Build info: version: '4.39.0', revision: '126f156aee'
System info: os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '21.0.6'
Driver info: driver.version: unknown
Build info: version: '4.39.0', revision: '126f156aee'
System info: os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '21.0.6'
Driver info: driver.version: unknown
13:41:48.206 WARN [SeleniumSpanExporter$1.lambda$export$1] - org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Could not start a new session. Error while creating session with the driver service. Unable to obtain: chromedriver, error Command failed with code: 2, executed: [--browser, chrome, --proxy, --language-binding, java, --output, json]
error: a value is required for '--proxy <PROXY>' but none was supplied

For more information, try '--help'.

Reproducible Code

java -jar selenium-server-4.39.0.jar node   --selenium-manager true

[selenium-ci]

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

Selenium Triage Team: remember to follow the Triage Guide

[titusfortner]

Selenium manager is passed the proxy information that was created for the http client. Looks like the bindings see that a proxy object was created, but don't see a value. I think the answer is we have bindings ignore proxy when it is of type system.

[francoisdejgr]

Greetings

Not Sure if this additional info will help

As I was working on a machine that was setup for dev, I reran the code on machines that used default settings for Firefox, Chrome and Java.

I get the same error.

This is the script that I use to start the HUB
.\selenium-manager --driver chromedriver    --debug  --output LOGGER --trace --browser-version stable
.\selenium-manager --driver geckodriver    --debug  --output LOGGER --trace  --browser-version stable
java -jar selenium-server-4.39.0.jar hub 

This is the script that I use to start the Node

.\selenium-manager --driver chromedriver    --debug  --output LOGGER --trace  --browser-version stable
.\selenium-manager --driver geckodriver    --debug  --output LOGGER --trace  --browser-version stable
java -jar selenium-server-4.39.0.jar node --selenium-manager true