search

heroku / heroku-buildpack-emberjs

**This buildpack is deprecated!** Please use the official Node.js buildpack combined with the static or nginx buildpack instead.
71 stars 28 forks source link

"bin/nginx: error while loading shared libraries: libcrypto.so.1.0.0" on Heroku-20 #65

Closed edmorley closed 4 years ago

edmorley commented 4 years ago

Whilst this buildpack is no longer maintained, I'm filing this in case it helps others with debugging.

We've had a support ticket reporting that using this buildpack on Heroku-20 results in the following error at application start (after a seemingly successful build):

heroku[web.1]: Starting process with command `bin/boot`
app[web.1]: Starting log redirection...
app[web.1]: Starting nginx...
app[web.1]: bin/nginx: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
app[web.1]: Process exited unexpectedly: nginx
app[web.1]: Going down, terminating child processes...

This error is coming from the nginx binary installed by the static buildpack (which is one of the several buildpacks the emberjs buildpack downloads and runs as sub-buildpacks).

The static buildpack added support for Heroku-20 in heroku/heroku-buildpack-static/pull/182 and a new release was published to the buildpack registry in heroku/heroku-buildpack-static/pull/183.

However the emberjs buildpack doesn't use its sub-buildpacks from the buildpack registry, and instead fetches them from a the legacy codon-buildpacks S3 bucket here: https://github.com/heroku/heroku-buildpack-emberjs/blob/38845a55d1c96d3d0b32d00149d7f4b8cee2c9f0/buildpack/mrblib/buildpack/buildpack_runner.rb#L7

...which means it's still using an old version of the static buildpack that doesn't support Heroku-20.

Long term any users of the emberjs buildpack should switch to using a combination of the nodejs+static buildpacks directly, and not this wrapper buildpack.

Short term I'll see if I can get the codon-buildpacks copy of the static buildpack synced up with the latest buildpack registry release.

edmorley commented 4 years ago

This has now been resolved, by making sure the static buildpack published to the buildpack registry is also synced back to the legacy codon-buildpacks S3 bucket too, in: https://github.com/heroku/heroku-buildpack-static/issues/187

Longer-term users of the emberjs buildpack should migrate to using the nodejs/static/... buildpacks directly.