App crashes with php-fpm: error while loading shared libraries: libjpeg.so.62

[ghost]

I follow the 60 second Getting Started instructions but my app won't start because it can't find libjpeg and libsso. Apparently this can be resolved by "adding libjpeg62 to build step's stack/packages.txt". Any idea how to resolve this issue? I've never used build packs before. Below is the logs from my app. Thanks.

2014-12-29T17:22:11.714804+00:00 heroku[web.1]: Starting process with command start.sh
2014-12-29T17:22:12.478776+00:00 app[web.1]: Starting nginx
2014-12-29T17:22:12.809652+00:00 app[web.1]: php-fpm: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory
2014-12-29T17:22:12.809662+00:00 app[web.1]: nginx: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
2014-12-29T17:22:13.810033+00:00 heroku[web.1]: State changed from starting to crashed
2014-12-29T17:22:13.810707+00:00 heroku[web.1]: State changed from crashed to starting
2014-12-29T17:22:13.806823+00:00 heroku[web.1]: Process exited with status 127
2014-12-29T17:22:19.780297+00:00 heroku[web.1]: Starting process with command start.sh
2014-12-29T17:22:21.242438+00:00 app[web.1]: Starting nginx
2014-12-29T17:22:24.302265+00:00 app[web.1]: nginx: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
2014-12-29T17:22:24.297585+00:00 app[web.1]: php-fpm: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory
2014-12-29T17:22:25.195227+00:00 heroku[web.1]: Process exited with status 127
2014-12-29T17:22:26.572262+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fastpress.herokuapp.com request_id=3da83923-2bd7-4310-9e18-372e6f1c9e9a fwd="86.144.70.97" dyno= connect= service= status=503 bytes=
2014-12-29T17:22:25.241121+00:00 heroku[web.1]: State changed from starting to crashed

[ConstantineYurevich]

Same issue

[ToadJamb]

Just FYI, this buildpack is unnecessary. I started following this issue because I ran across it, too. Further investigation revealed that Wordpress works out of the box on heroku now.

[thomasvangrondelle]

any updates to this? hitting the same problem

[ghost]

ToadJamb, how do you unbox Wordpress then? Is it simply a case of pushing an unzipped WP distro to heroku and following the 5 minute install process?

[ghost]

I can confirm that there is no need for this build pack. If you execute the following instructions, it should work for you too. It worked for me.

https://ksylvest.com/posts/2014-05-02/deploying-wordpress-to-heroku

[peterhartree]

@thomasvangrondelle @rayascott My reply to #91 should help you with this issue, if you still care.

[ghost]

Thanks Peter. I've had no problems as yet with the solution that worked for me, but I'll keep your advice in mind, should I need it. Thanks.