Столкновение с проблемой конфигурации с узлом на AWS и концентраторе.Ошибка при получении параметров из концентратора.Узел может закончиться с неправильными тайм-аутами - PullRequest
0 голосов
/ 06 декабря 2018

Пожалуйста, помогите, я пытался изменить время ожидания, но ничего не помогло.пожалуйста, предложите правильную конфигурацию концентратора и узла.

------ Концентратор успешно запущен ----

C:\>java -jar selenium-server-standalone-3.141.59.jar -role hub -hubConfig grid_
hub.json
Picked up JAVA_TOOL_OPTIONS: -agentlib:jvmhook
Picked up _JAVA_OPTIONS: -Xrunjvmhook -Xbootclasspath/a:"C:\Program Files (x86)\
HP\Unified Functional Testing\bin\java_shared\classes";"C:\Program Files (x86)\H
P\Unified Functional Testing\bin\java_shared\classes\jasmine.jar"
12:18:05.811 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, re
vision: e82be7d358
12:18:05.936 INFO [GridLauncherV3.lambda$buildLaunchers$5] - Launching Selenium
Grid hub on port null
2018-12-06 12:18:06.330:INFO::main: Logging initialized @802ms to org.seleniumhq
.jetty9.util.log.StdErrLog
12:18:06.647 INFO [Hub.start] - Selenium Grid hub is up and running
12:18:06.648 INFO [Hub.start] - Nodes should register to http://10.72.25.43:4444
/grid/register/
12:18:06.648 INFO [Hub.start] - Clients should connect to http://10.72.25.43:444
4/wd/hub

Ошибка при запуске узла - выбор browserTimeout и тайм-аутазначения из хаба перед отправкой заявки на регистрацию.Ошибка при получении параметров из концентратора.Узел может закончиться с неправильными тайм-аутами.


C:\>java -jar selenium-server-standalone-3.141.59.jar -role webdriver -hub http://10.72.25.43:4444/grid/register -port 7777 -debug
12:18:27.688 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
12:18:27.817 INFO [GridLauncherV3.lambda$buildLaunchers$7] - Launching a Selenium Grid node on port 7777
2018-12-06 12:18:28.013:INFO::main: Logging initialized @598ms to org.seleniumhq.jetty9.util.log.StdErrLog
12:18:28.275 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
12:18:28.364 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 7777
12:18:28.364 INFO [GridLauncherV3.lambda$buildLaunchers$7] - Selenium Grid node is up and ready to register to the hub
12:18:28.442 DEBUG [SelfRegisteringRemote.startRegistrationProcess] - Using the json request : {
  "class": "org.openqa.grid.common.RegistrationRequest",
  "configuration": {
    "capabilities": [
      {
        "browserName": "firefox",
        "marionette": true,
        "maxInstances": 5,
        "platform": "XP",
        "platformName": "XP",
        "seleniumProtocol": "WebDriver",
        "server:CONFIG_UUID": "ea0fa21a-f231-43d6-90b1-6717a08dd027"
      },
      {
        "browserName": "chrome",
        "maxInstances": 5,
        "platform": "XP",
        "platformName": "XP",
        "seleniumProtocol": "WebDriver",
        "server:CONFIG_UUID": "8ee7531c-ed6b-474b-9ed5-bca52afcaa39"
      },
      {
        "browserName": "internet explorer",
        "maxInstances": 1,
        "platform": "WINDOWS",
        "platformName": "WINDOWS",
        "seleniumProtocol": "WebDriver",
        "server:CONFIG_UUID": "672dcea2-14ce-4ad9-ae10-a97265b32a56"
      }
    ],
    "custom": {
    },
    "debug": true,
    "downPollingLimit": 2,
    "enablePlatformVerification": true,
    "host": "10.104.1.81",
    "hub": "http:\u002f\u002f10.72.25.43:4444\u002fgrid\u002fregister",
    "id": "http:\u002f\u002f10.104.1.81:7777",
    "maxSession": 5,
    "nodePolling": 5000,
    "nodeStatusCheckTimeout": 5000,
    "port": 7777,
    "proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
    "register": true,
    "registerCycle": 5000,
    "remoteHost": "http:\u002f\u002f10.104.1.81:7777",
    "role": "node",
    "servlets": [
    ],
    "unregisterIfStillDownAfter": 60000,
    "withoutServlets": [
    ]
  },
  "description": null,
  "name": null
}
12:18:28.449 INFO [SelfRegisteringRemote$1.run] - Starting auto registration thread. Will try to register every 5000 ms.
12:18:28.450 DEBUG [SelfRegisteringRemote.registerToHub] - Fetching browserTimeout and timeout values from the hub before sending registration request
12:18:49.786 WARN [SelfRegisteringRemote.registerToHub] - ****Error getting the parameters from the hub. The node may end up with wrong timeouts.Failed to connect to /10.72.25.43:4444**
12:18:49.786 INFO [SelfRegisteringRemote.registerToHub] - Registering the node to the hub: http://10.72.25.43:4444/grid/register
12:19:10.801 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: Error sending the registration request: Failed to connect to /10.72.25.43:4444**
12:19:36.811 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: The hub is down or not responding: Failed to connect to /10.72.25.43:4444
12:20:02.817 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: The hub is down or not responding: Failed to connect to /10.72.25.43:4444
12:20:28.824 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: The hub is down or not responding: Failed to connect to /10.72.25.43:4444
12:20:54.830 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: The hub is down or not responding: Failed to connect to /10.72.25.43:4444
12:21:20.848 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: The hub is down or not responding: Failed to connect to /10.72.25.43:4444
...