Katalon Engine fails to start Chrome in Linux

Product Forums Katalon Studio
,
1

When executing Katalon test suite we get an error related to Chrome not starting correctly. Are there instructions on how to configure this properly on Linux?

Starting ChromeDriver 84.0.4147.30 (48b3e868b4cc0aa7e8149519690b6f6949e110a8-refs/branch-heads/4147@{#310}) on port 6419
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
2020-08-04 09:27:17.787 ERROR c.k.katalon.core.main.TestCaseExecutor   - ? Test Cases/mobiletestapp/largeScreen Login FAILED.
Reason:
org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally.
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'srvrdtek', ip: 'x.x.x.x', os.name: 'Linux', os.arch: 'amd64', os.version: '4.14.35-1902.8.4.el7uek.x86_64', java.version: '1.8.0_252'
Driver info: driver.version: ChromeDriver
remote stacktrace: #0 0x55d4f83e2ea9 <unknown>

        at org.openqa.selenium.remote.W3CHandshakeResponse.lambda$errorHandler$0(W3CHandshakeResponse.java:62)
        at org.openqa.selenium.remote.HandshakeResponse.lambda$getResponseFunction$0(HandshakeResponse.java:30)
2

@david.mossakowski
You can try to add these desired capabilities in Desired Capabilities settings of Chrome (headless):

"args":["--no-sandbox","--disable-dev-shm-usage"]
"useAutomationExtension":"false"

Screen Shot 2020-08-04 at 3.11.18 PM
Screen Shot 2020-08-04 at 3.11.18 PM1832×1112 253 KB

Related dicussion: selenium - WebDriverException: unknown error: DevToolsActivePort file doesn't exist while trying to initiate Chrome Browser - Stack Overflow

3

I have the exact same issue but only when it is executed through a jenkins job; it works perfectly ok through KSE.
In Jenkins file we run test scripts on different browsers image
This is how Chrome is defined in jenkins file
image

Could you please assist how this can be fixed? Is this issue with all docker images of katalon?