PDF Generation broken

[p-a-s-c-a-l]

Both on DEV and PROD:

Error generating document: Failed to generate PDF: Loading pages (1/6) [> ] 0% [======> ] 10% QSslSocket: cannot resolve CRYPTO_num_locks QSslSocket: cannot resolve CRYPTO_set_id_callback QSslSocket: cannot resolve CRYPTO_set_locking_callback QSslSocket: cannot resolve sk_free QSslSocket: c

See also clarity-h2020/csis-technical-validation#76 (comment)

Probably an error in the HTML2PDF library. Which one are we using?

[patrickkaleta]

Both on DEV and PROD:

Error generating document: Failed to generate PDF: Loading pages (1/6) [> ] 0% [======> ] 10% QSslSocket: cannot resolve CRYPTO_num_locks QSslSocket: cannot resolve CRYPTO_set_id_callback QSslSocket: cannot resolve CRYPTO_set_locking_callback QSslSocket: cannot resolve sk_free QSslSocket: c

See also clarity-h2020/csis-technical-validation#76 (comment)

Probably an error in the HTML2PDF library. Which one are we using?

We're using wkhtmltopdf (set in the Entity print settings) in the version 0.12.4 (I believe).

The error message seems familiar. I think we had that problem with QSslSocket in the past. AFAIK @DenoBeno fixed it be installing/updating something inside the docker-container? And maybe that got lost after the update of the Docker container?

[patrickkaleta]

Error generating document: Failed to generate PDF: Loading pages (1/6) [> ] 0% [======> ] 10% QSslSocket: cannot resolve CRYPTO_num_locks QSslSocket: cannot resolve CRYPTO_set_id_callback QSslSocket: cannot resolve CRYPTO_set_locking_callback QSslSocket: cannot resolve sk_free QSslSocket: c

Probably related to this issue. Seems like Debian and wkhtmltopdf 0.12.4 have a problematic relationship. The proposed solution by updating wkhtmltopdf to version 0.12.5 is not the solution, since that version itself has its problems (see 1, 2), so I believe we went with something like proposed in this comment.

But a month ago version 0.12.6 was finally released, which seems to solve some of the issues introduced in 0.12.5.

[p-a-s-c-a-l]

h4cc/wkhtmltopdf-amd64 seems to be abandoned. wkhtmltopdf. can be downloaded from here, so I'll update the docker image.

[p-a-s-c-a-l]

Error generating document: Failed to generate PDF: sh: 1: /app/vendor/h4cc/wkhtmltopdf-amd64/bin/wkhtmltopdf-amd64: not found

Now the question is how to tell phpwkhtmltopdf where to find the wkhtmltopdf binary?

[patrickkaleta]

Error generating document: Failed to generate PDF: sh: 1: /app/vendor/h4cc/wkhtmltopdf-amd64/bin/wkhtmltopdf-amd64: not found

Now the question is how to tell phpwkhtmltopdf where to find the wkhtmltopdf binary?

That should be possible in the Entity print settings. There you can specify the binary location.

[p-a-s-c-a-l]

PDF Generation is working again on DEV. I'm going to update PROD with the new docker image.

[patrickkaleta]

I'm going to update PROD with the new docker image.

I think there is a webinar taking place right now or just about to.

[p-a-s-c-a-l]

PROD is updated now. I had to lock drupal/group at 1.0.0-rc5. See #166