Posting Rules:
I have updated to 3.27.0 and followed the process to update PHP on my VMware Ubuntu installation.
The process seemed to go without issue and when I checked php -v I get 8.4.14 but the Eramba system health claims I’m running 8.2.27 still and is “not ok”
Anyone encountered this? Eramba seemingly functions totally fine, I just can’t update now due to the health check.
Have you run the following to select your desired version? I had something similar and this worked for me.
sudo update-alternatives --config php
Seems like you updated the CLI and not the apache extension. Both need to be updated - cron uses the CLI.
Not sure what that means unfortunately. is this an INI change. Heading to the googles!
The results from sudo update-alternatives --config php look fine, but have you run the following to disable the apache mod and enable the new one?
a2dismod php8.2
a2enmod php8.4
systemctl restart apache2
It could be that the php_module is symlinked and is pointing to a generic or old version rather than the specific one that’s required.
Run the below to confirm which version is actually loaded:
ls -l /etc/apache2/mods-enabled/php*.load
You should see something like this: /etc/apache2/mods-available/php8.4.load. If it points to another php version, then apache is still linked to an older version.
If the symlink doesn’t point to php8.4 try running the below as an example to disable any other versions that are showing:
sudo a2dismod php8.1 php8.2 php8.3
sudo a2enmod php8.4
sudo systemctl restart apache2
As for the error message, you can run the below to clean it up:
sudo rm /etc/apache2/mods-enabled/php8.1.load /etc/apache2/mods-enabled/php8.1.conf 2>/dev/null
sudo systemctl restart apache2
Other than trying the above, I’m not sure!
Appreciate the help!
I ran all those and restarted the service and still showing fail. I’ll have to poke around some more
