[🐛 Bug]: The node of appium cannot register with the hub node of selenium #15447
Description
What happened?
Distressed, don't know how to solve it
The node of appium cannot register with the hub node of selenium
How can we reproduce the issue?
hub IP: 192.168.16.153
appium node IP : 192.168.16.154
appium 2.17.0
I have turned off the firewall
sudo ufw default allow incoming
sudo ufw default allow outgoing
root@coco:/home/cocosudo ufw status
Status: inactive
Relevant log output
The startup command of the hub node is: java -jar selenium-server-4.27.0.jar node --hub http://192.168.16.153:4444
log:
root@coco:/home/coco# java -jar selenium-server-4.27.0.jar hub --host 192.168.16.153 --port 4444
09:57:06.545 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
09:57:06.550 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
09:57:06.618 INFO [BoundZmqEventBus.<init>] - XPUB binding to [binding to tcp://*:4442, advertising as tcp://127.0.1.1:4442], XSUB binding to [binding to tcp://*:4443, advertising as tcp://127.0.1.1:4443]
09:57:06.666 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://127.0.1.1:4442 and tcp://127.0.1.1:4443
09:57:06.688 INFO [UnboundZmqEventBus.<init>] - Sockets created
09:57:07.690 INFO [UnboundZmqEventBus.<init>] - Event bus ready
09:57:08.106 INFO [Hub.execute] - Started Selenium Hub 4.27.0 (revision d6e718d): http://192.168.16.153:4444
09:57:08.973 INFO [Node.<init>] - Binding additional locator mechanisms: relative
09:57:18.971 INFO [Node.<init>] - Binding additional locator mechanisms: relative
09:59:13.360 INFO [Node.<init>] - Binding additional locator mechanisms: relative
09:59:23.385 INFO [Node.<init>] - Binding additional locator mechanisms: relative
09:59:33.411 INFO [Node.<init>] - Binding additional locator mechanisms: relative
The startup command of the appium node is: java -jar selenium-server-4.27.0.jar node --hub http://192.168.16.153:4444 --config node2.toml
log:
root@coco:/home/coco# java -jar selenium-server-4.27.0.jar node --hub http://192.168.16.153:4444 --config node2.toml
09:59:11.704 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
09:59:11.709 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
09:59:11.790 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://192.168.16.153:4442 and tcp://192.168.16.153:4443
09:59:11.827 INFO [UnboundZmqEventBus.<init>] - Sockets created
09:59:12.830 INFO [UnboundZmqEventBus.<init>] - Event bus ready
09:59:12.913 INFO [NodeServer.createHandlers] - Reporting self as: http://172.17.0.1:5555
09:59:12.934 INFO [NodeOptions.getSessionFactories] - Detected 4 available processors
09:59:12.953 INFO [RelayOptions.getSessionFactories] - Adding relay configs for http://192.168.16.154:4733
09:59:12.961 INFO [RelayOptions.lambda$getSessionFactories$1] - Mapping Capabilities {appium:automationName: uiautomator2, appium:udid: 7e4fbdd1, platformName: ANDROID}, 1 times
09:59:12.982 INFO [Node.<init>] - Binding additional locator mechanisms: relative
09:59:13.108 INFO [NodeServer$2.start] - Starting registration process for Node http://172.17.0.1:5555
09:59:13.111 INFO [NodeServer.execute] - Started Selenium node 4.27.0 (revision d6e718d): http://172.17.0.1:5555
09:59:13.363 INFO [NodeServer$2.lambda$start$1] - Sending registration event...
09:59:23.391 INFO [NodeServer$2.lambda$start$1] - Sending registration event...
09:59:33.417 INFO [NodeServer$2.lambda$start$1] - Sending registration event...
09:59:43.442 INFO [NodeServer$2.lambda$start$1] - Sending registration event...
09:59:53.468 INFO [NodeServer$2.lambda$start$1] - Sending registration event...
node2.toml:
[server]
port = 5555
[node]
detect-drivers = false
[relay]
url = "http://192.168.16.154:4733"
status-endpoint = "/status"
configs = [
"1", "{\"platformName\": \"android\",\"appium:automationName\": \"uiautomator2\",\"appium:udid\": \"7e4fbdd1\"}"
]Operating System
ubuntu server 20
Selenium version
4.27.0
What are the browser(s) and version(s) where you see this issue?
NA
What are the browser driver(s) and version(s) where you see this issue?
NA
Are you using Selenium Grid?
4.27.0