HTML to PDF bug persists - Pupeteer Error
Hello together, yesterday i brought up and issue with the HTML to PDF node, that the pdf couldnt be loaded.
We were able to "fix" that issue tempoarily by creating a new node and let that node return the buffer. We use the buffer for us to safe the pdf in our cloud storage.
Today we unfortunatly encounterd the same issue again. We tried different methods and followed best practices like using the create public url node as a download node.
When we checked the return from the buffer we found this error
Failed to launch the browser process!
[0808/125844.331607:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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 0x555766aad612 base::debug::CollectStackTrace()
#1 0x555766a0c193 base::debug::StackTrace::StackTrace()
#2 0x555766a1fdea logging::LogMessage::~LogMessage()
#3 0x55576498803b content::ZygoteHostImpl::Init()
#4 0x55576659856c content::ContentMainRunnerImpl::Initialize()
#5 0x555766596491 content::RunContentProcess()
#6 0x5557665965e4 content::ContentMain()
#7 0x5557665f03ba headless::(anonymous namespace)::RunContentMain()
#8 0x5557665f00c5 headless::HeadlessShellMain()
#9 0x555762e0b1e3 ChromeMain
#10 0x7f1298c6f09b __libc_start_main
#11 0x555762e0b02a _start
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
From the looks of it , it looks like there must be some kind of pupeteer issues. Would appreciate a quick feedback if the issue is know / being solved in the moment. Because this problem is currently breaking our application, it would be nice to know we are in the process here rn.
Thanks for the support.
We were able to "fix" that issue tempoarily by creating a new node and let that node return the buffer. We use the buffer for us to safe the pdf in our cloud storage.
Today we unfortunatly encounterd the same issue again. We tried different methods and followed best practices like using the create public url node as a download node.
When we checked the return from the buffer we found this error
Failed to launch the browser process!
[0808/125844.331607:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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 0x555766aad612 base::debug::CollectStackTrace()
#1 0x555766a0c193 base::debug::StackTrace::StackTrace()
#2 0x555766a1fdea logging::LogMessage::~LogMessage()
#3 0x55576498803b content::ZygoteHostImpl::Init()
#4 0x55576659856c content::ContentMainRunnerImpl::Initialize()
#5 0x555766596491 content::RunContentProcess()
#6 0x5557665965e4 content::ContentMain()
#7 0x5557665f03ba headless::(anonymous namespace)::RunContentMain()
#8 0x5557665f00c5 headless::HeadlessShellMain()
#9 0x555762e0b1e3 ChromeMain
#10 0x7f1298c6f09b __libc_start_main
#11 0x555762e0b02a _start
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
From the looks of it , it looks like there must be some kind of pupeteer issues. Would appreciate a quick feedback if the issue is know / being solved in the moment. Because this problem is currently breaking our application, it would be nice to know we are in the process here rn.
Thanks for the support.
GitHub
JavaScript API for Chrome and Firefox. Contribute to puppeteer/puppeteer development by creating an account on GitHub.
