Unable to determine Composer vendor-dir setting
tillkruss opened this issue · comments
We're seeing strange crashes during boot. I can't make sense of the other two issues with the same error message.
2021-05-27T17:38:34.408021+00:00 heroku[web.1]: Starting process with command `vendor/bin/heroku-php-nginx -C nginx.conf web/`
2021-05-27T17:38:37.763082+00:00 app[web.1]: [heroku-exec] Starting
2021-05-27T17:38:38.208986+00:00 app[web.1]: Unable to determine Composer vendor-dir setting; is 'composer' executable on path or 'composer.phar' in current working directory?
2021-05-27T17:38:38.278000+00:00 heroku[web.1]: Process exited with status 1
2021-05-27T17:38:38.346112+00:00 heroku[web.1]: State changed from starting to crashed
Also during builds.
-----> Build succeeded!
-----> PHP app detected
-----> Bootstrapping...
-----> Installing platform packages...
- zstd (1.4.9)
- php (7.4.19)
- ext-bcmath (bundled with php)
- ext-exif (bundled with php)
- ext-gd (bundled with php)
- ext-mbstring (bundled with php)
- ext-pcntl (bundled with php)
- lz4 (1.9.3)
- liblzf (3.6)
- ext-msgpack (2.1.2)
- ext-igbinary (3.2.2)
- ext-relay (0.1.0)
- ext-redis (5.3.4)
- ext-imagick (3.4.4)
- apache (2.4.46)
- nginx (1.18.0)
- composer (2.0.13)
-----> Installing dependencies...
Composer version 2.0.13 2021-04-27 13:11:08
/tmp/codon/tmp/buildpacks/49830eb7d567d754bbb44099860d3e4d9f3cdaaf/bin/compile: line 603: 4322 Segmentation fault composer config --no-plugins -g --unset github-oauth.github.com &> /dev/null
Something is crashing. I'd say 99% chance it's one of your custom extensions ;)
The same segfault might also occur at startup, causing composer config vendor-dir
to fail.
If you still have an affected dyno that crashes this way, you can heroku run bash
in and run composer config vendor-dir
to see what the issue is - most likely a segfault as well causing PHP to crash.
Thanks David!