So I’m getting the error that other have had. But when I check my hosting they inform me that:
Path to PHP
/usr/local/bin/php
If I add this info the the config.ini
background.php.path = “/usr/local/bin/php-cli”
or
background.php.path = “/usr/local/bin/php”
I have multiple hosting services. So I tried this on both services, different path depending on the hosting service, and I’m getting the error on both sites.
RuntimeException: The configured PHP path (/usr/local/bin/php) does not point to a PHP-CLI binary.
If I run php -v from the path I see that php is indeed there 7.2.31 (cli)
I’ve tried everything and can’t get it to work. Tried setting every conceivable path, adding symlinks, setting CLI in bash, etc…
Zip. I can’t get it to work.
Thanks
In general, all you should have to do is find the path to the PHP CLI binary, and set that path as the value of background.php.path in application/config/config.ini.
@jscott What’s the full, exact output of running the command /usr/local/bin/php -v on these servers? @DavidGhedini, same question with whatever the relevant path on your server.
The error you posted gets thrown when we try to execute that -v command and the output doesn’t look like PHP X.Y.Z
Yours does look normal, how we’d expect. I’m thinking the issue here may be instead something like the relevant functions PHP uses to run commands (here, exec) simply being disabled. It’s not hugely uncommon for web hosts to disable exec and other similar functions.