Hi,
It looks like grunt-ci stopped starting up on a few different prs, while it passes locally.
https://ci.theforeman.org/blue/organizations/jenkins/katello-pr-test/detail/katello-pr-test/5006/pipeline/79
https://ci.theforeman.org/blue/organizations/jenkins/katello-pr-test/detail/katello-pr-test/5008/pipeline/
https://ci.theforeman.org/blue/organizations/jenkins/katello-pr-test/detail/katello-pr-test/5005/pipeline/
It might be dependency related from this:
opened 03:04PM - 19 Aug 17 UTC
closed 03:58AM - 31 Aug 17 UTC
host
**Server Info:**
CUP: Intel(R) Xeon(R) Platinum 8163 CPU @ 2.50GHz
MemTotal: … 1016396 kB
OS:CentOS Linux release 7.3.1611 (Core)
Node:v8.4.0
when I try to run my app in this server, there have an error throw:
> (node:29208) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: **Failed to connect to chrome!**
I want run Chromium which download by puppeteer manual,there have some log output:
> robin@eve ~/project/memostickyserver/node_modules/puppeteer/.local-chromium/linux-494755/chrome-linux (master*) $ chrome
> robin@eve ~/project/memostickyserver/node_modules/puppeteer/.local-chromium/linux-494755/chrome-linux (master*) $ ./chrome
> [28268:28268:0819/223159.486750:FATAL:zygote_host_impl_linux.cc(123)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
> #0 0x7fd4bc6d6657 base::debug::StackTrace::StackTrace()
> #1 0x7fd4bc6ea311 logging::LogMessage::~LogMessage()
> #2 0x7fd4bb8db1f1 content::ZygoteHostImpl::Init()
> #3 0x7fd4bb575da0 content::BrowserMainLoop::EarlyInitialization()
> #4 0x7fd4bb57c4c3 content::BrowserMainRunnerImpl::Initialize()
> #5 0x7fd4bb575532 content::BrowserMain()
> #6 0x7fd4bc3e17fd content::ContentMainRunnerImpl::Run()
> #7 0x7fd4bc3e9314 service_manager::Main()
> #8 0x7fd4bc3e0462 content::ContentMain()
> #9 0x7fd4bb020b74 ChromeMain
> #10 0x7fd4b3da2b35 __libc_start_main
> #11 0x7fd4bb0209d0 <unknown>
>
> Received signal 6
> #0 0x7fd4bc6d6657 base::debug::StackTrace::StackTrace()
> #1 0x7fd4bc6d61cf base::debug::(anonymous namespace)::StackDumpSignalHandler()
> #2 0x7fd4ba04d370 <unknown>
> #3 0x7fd4b3db61d7 __GI_raise
> #4 0x7fd4b3db78c8 __GI_abort
> #5 0x7fd4bc6d5202 base::debug::BreakDebugger()
> #6 0x7fd4bc6ea7cc logging::LogMessage::~LogMessage()
> #7 0x7fd4bb8db1f1 content::ZygoteHostImpl::Init()
> #8 0x7fd4bb575da0 content::BrowserMainLoop::EarlyInitialization()
> #9 0x7fd4bb57c4c3 content::BrowserMainRunnerImpl::Initialize()
> #10 0x7fd4bb575532 content::BrowserMain()
> #11 0x7fd4bc3e17fd content::ContentMainRunnerImpl::Run()
> #12 0x7fd4bc3e9314 service_manager::Main()
> #13 0x7fd4bc3e0462 content::ContentMain()
> #14 0x7fd4bb020b74 ChromeMain
> #15 0x7fd4b3da2b35 __libc_start_main
> #16 0x7fd4bb0209d0 <unknown>
> r8: 00007fff21b42080 r9: 0000000000000395 r10: 0000000000000008 r11: 0000000000000206
> r12: 00007fff21b424e0 r13: 000000000000016d r14: 00007fff21b424d8 r15: 00007fff21b424d0
> di: 0000000000006e6c si: 0000000000006e6c bp: 00007fff21b42080 bx: 00007fff21b42080
> dx: 0000000000000006 ax: 0000000000000000 cx: ffffffffffffffff sp: 00007fff21b41ed8
> ip: 00007fd4b3db61d7 efl: 0000000000000206 cgf: 0000000000000033 erf: 0000000000000000
> trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
> [end of stack trace]
> Calling _exit(1). Core file will not be generated.
> robin@eve ~/project/memostickyserver/node_modules/puppeteer/.local-chromium/linux-494755/chrome-linux (master*) $ ./chrome --no-sandbox
> [0819/223234.158902:ERROR:nacl_helper_linux.cc(310)] NaCl helper process running without a sandbox!
> Most likely you need to configure your SUID sandbox correctly
pls help,how to fix this ?
# Troubleshooting
:::caution
Chromium currently does not provide arm64 binaries for Linux. There are only
binaries for
[Mac ARM with experimental support from Puppeteer](https://pptr.dev/contributing#macos-arm-and-custom-executables).
:::
## `Cannot find module 'puppeteer-core/internal/...'`
This can occur is your Node.js version is lower than 14 or you are using a
custom resolver (such as
[`jest-resolve`](https://www.npmjs.com/package/jest-resolve)). For the former,
we do not support deprecated versions of Node.js. For the latter, usually
upgrading the resolver (or its parent module such as `jest`) will work (e.g.
https://github.com/puppeteer/puppeteer/issues/9121)
## `Could not find expected browser locally`
This file has been truncated. show original
ekohl
September 21, 2020, 4:02pm
2
We’re seeing the same in our other tests that use chromium. It appears to have started with the upgrade to Chromium 85 on our nodes. @tbrisker and @ezr-ondrej did start to look into it, but so far haven’t found it. I did find this BZ from epel
https://bugzilla.redhat.com/show_bug.cgi?id=1881142
Perhaps it’s the same, though a quick local check didn’t reproduce it.
There’s also https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-dec199d5a2 waiting in epel7-testing and perhaps that helps.
1 Like