gotenberg: Latest 7.5.0 docker image intermittently crashes
Every so often, the latest 7.5 docker image will crash on startup. Here’s the docker logs:
pdfgen_1 |
pdfgen_1 | _____ __ __
pdfgen_1 | / ___/__ / /____ ___ / / ___ _______ _
pdfgen_1 | / (_ / _ \/ __/ -_) _ \/ _ \/ -_) __/ _ '/
pdfgen_1 | \___/\___/\__/\__/_//_/_.__/\__/_/ \_, /
pdfgen_1 | /___/
pdfgen_1 |
pdfgen_1 | A Docker-powered stateless API for PDF files.
pdfgen_1 | Version: 7.5.0
pdfgen_1 | -------------------------------------------------------
pdfgen_1 | [SYSTEM] modules: api chromium gc libreoffice logging pdfcpu pdfengines pdftk prometheus qpdf uno uno-pdfengine webhook
pdfgen_1 | [SYSTEM] gc: application started
pdfgen_1 | [SYSTEM] api: server listening on port 3000
pdfgen_1 | [SYSTEM] prometheus: collecting metrics
pdfgen_1 | [SYSTEM] pdfengines: pdfcpu pdftk qpdf uno-pdfengine
pdfgen_1 | [FATAL] starting uno: start long-running LibreOffice listener: waiting for the LibreOffice listener socket to be available: context deadline exceeded
Is this a timeout issue? I don’t believe the previous docker image (7.4.3) had this issue.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19
I’m not able to reproduce the problem with that image. As it was an intermittent issue, I’m not 100% positive it’s fixed, but I tried restarting many times and didn’t experience the problem. All our tests passed.
Thanks much for working on this!
–John
hi @gulien already test on Cloud Run, and it works! Great Job!
I changed the timeout to 60 seconds and still experienced the issue. Yes, I suspect something is dying.
This is in Gitlab CI which is using docker compose. In our production docker compose configuration we do have restart always which should help.
I agree, it would be helpful to have more debugging output when the fatal timeout gets hit.
Thank you for your help trying to figure this out! Much appreciated. By the way, we love this service.