Le 26/09/2021 à 16:18, John Romano D'Orazio a écrit :
Hello all, I recently updated the packages on my server, among the updates was apache2 which was updated to version 2.4.29 (I use the PPA for Apache 2.x : Ondřej Surý <https://launchpad.net/~ondrej/+archive/ubuntu/apache2>).After the update, all services (nginx, apache2, php8.0-fpm, php7.4-fpm ...) were active. For good measure, I restarted all these services, and again they started correctly and were active without any errors.However, all of my websites were giving 500 internal server errors. Inspecting the system logs (|/var/log/syslog|,|/var/log/nginx/error.log|,|/var/log/apache2/error.log|) I didn't see any errors, however when inspecting the logs for my single websites, I was seeing this error on all of them:AH10292: Invalid proxy UDS filename (proxy:unix:///var/www/vhosts/system/mydomain.com/php-fpm.sock|fcgi://127.0.0.1:9000/var/www/vhosts/mydomain.com/httpdocs/wp-login.php)The relative |php-fpm.sock|files do exist in the related paths, and have correct permissions, and were working fine until before the package upgrade.I stopped services, uninstalled the apache2 package, removed the *ppa:ondrej/apache2* repository, and then reinstalled *apache2*, which is now at version 2.4.41, and all my websites are back up again.****I use Plesk to help manage my webserver and websites. The system is Ubuntu 20.04.3 LTS, architecture x86_64, Plesk is *Plesk Obsidian 18.0.38 Update#2 <https://github.com/oerdnj/deb.sury.org/issues/2>*, last updated on Sept 15, 2021 02:19 AM.Other pleskians had the same problem, as can be seen on this thread:https://talk.plesk.com/threads/all-domains-apache2-error-500.362208/ <https://talk.plesk.com/threads/all-domains-apache2-error-500.362208/>.I created an issue on Ondrej Sury's github repo: https://github.com/oerdnj/deb.sury.org/issues/1643 <https://github.com/oerdnj/deb.sury.org/issues/1643>Ondrej answered suggesting to open a ticket on the Apache upstream, stating that there haven't been any updates to the packaging.Is there perhaps an already known bug that might be causing this? Or should a bug report be opened?Kind regards, John D'Orazio ****
Hi, I guess that it is fixed by r1893519 (trunk) [1] This has been backported in r1893559 (2.4.x) [2] and will be part of 2.4.50. CJ [1]: https://svn.apache.org/viewvc?view=revision&revision=1893519 [2]: https://svn.apache.org/viewvc?view=revision&revision=1893559 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|