Open ninjabugs opened 9 years ago
Having been instructed to upgrade to cedar-14 by heroku - I've just discovered this the hard way
2015-08-27T04:50:15.834617+00:00 heroku[web.1]: Starting process with command start.sh
2015-08-27T04:50:18.257612+00:00 app[web.1]: Starting nginx
2015-08-27T04:50:18.369413+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
2015-08-27T04:50:18.364895+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
2015-08-27T04:50:19.239296+00:00 heroku[web.1]: State changed from starting to crashed
I guess we can just rebuild nginx/php-fpm to work with the updated libraries somehow?
nginx is linked against fixed versions of libraries
ldd nginx linux-vdso.so.1 => (0x00007ffe797f1000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4bef614000) libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f4bef3db000) libssl.so.0.9.8 => not found libcrypto.so.0.9.8 => not found libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4bef1d7000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f4beefbe000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4beebf9000) /lib64/ld-linux-x86-64.so.2 (0x00007f4bef832000)
~/vendor/php $ ldd /app/vendor/php/sbin/php-fpm linux-vdso.so.1 => (0x00007ffdb4dd5000) libjpeg.so.62 => not found libssl.so.0.9.8 => not found libcrypto.so.0.9.8 => not found libcurl.so.4 => /usr/lib/x86_64-linux-gnu/libcurl.so.4 (0x00007fb35179b000)
The following are available on heroku cedar-14 /lib/x86_64-linux-gnu/libssl.so.1.0.0 /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
I've resolved my issues by installing wordpress through https://github.com/xyu/heroku-wp
I've detailed the steps to convert here: http://kieranbingham.co.uk/upgrade-wordpress-on-heroku-to-cedar-14/
Any plan on upgrading this buildpack for Cedar-14?
No plans, this project hasn't had commits during this year. Please see https://github.com/mchung/heroku-buildpack-wordpress#see-also for alternatives, Heroku's PHP support is nowadays better.
@okko Thanks!
@kbingham can you share the details on how you migrated from this buildpack to the native php buildpack using heroku-wp?
@vmetayer Ha, well it looks like my blog has broken. Time for me to move it off heroku anyway! For your reference however, I've pasted the blog entry onto gist for you. https://gist.github.com/kbingham/3c2431f2a7e6d71c2d4a
I think you should write in the README in capital letters that this doesn't work with cedar-14, to save people's time
@kbingham your link is broke, dam... im at 2018 trying to make this work out... but no luck so far
@Diegow3b Ahh sorry - it's just the www. forwarding. http://www.kieranbingham.co.uk/upgrade-wordpress-on-heroku-to-cedar-14/ should work. Looks like I pasted the detail at https://gist.github.com/kbingham/3c2431f2a7e6d71c2d4a too
But ... surely cedar-14 is waaaay out of date too ? - I'd recommend looking at other solutions here if you upgrade to make sure you're on a more up to date base.
cedar-14 still default... but nvm, im using one from heroku https://dashboard.heroku.com/new?button-url=https%3A%2F%2Felements.heroku.com%2Fbuttons%2Fellefsen%2Fwordpress-heroku-php&template=https%3A%2F%2Fgithub.com%2Fellefsen%2Fwordpress-heroku-php
Also having this problem, so cedar-14 is a no go to deploy WordPress on Heroku?
https://gist.github.com/ryanfreemanio/2a6fc23bd87c404f5556c9865039845e
Cedar-10 will read end-of-life on November 4th, 2015. Upgrading the stack to cedar-14 breaks the site.