Bug 27207

Summary:	PHP no more working after last update, error 503, service unavailable
Product:	Mageia	Reporter:	papoteur <yvesbrungard>
Component:	RPM Packages	Assignee:	Marc Krämer <mageia>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal
Version:	7
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	apache-mod_php-7.3.21-2.mga7	CVE:
Status comment:

Description papoteur 2020-08-27 08:58:35 CEST

Description of problem:
After the last update including PHP, phpmyadmin and other applications are no more accessible.
http://localhost/phpmyadmin gives:
Service inaccessible!

En raison de travaux de maintenance ou de problèmes de capacité le serveur n'est pas en mesure de répondre à votre requête pour l'instant. Veuillez réessayer plus tard.

Si vous pensez qu'il s'agit d'une erreur du serveur, veuillez contacter le webmestre.
Error 503
localhost
Apache/2.4.46 (Mageia) PHP/7.3.21

In the same time I use also php-fpm. Applications configured with it continue to work.

Comment 1 papoteur 2020-08-27 09:16:12 CEST

After removing file /etc/httpd/conf/modules.d/10_php-fpm.conf and restarting httpd, all applications work again.
If I understand bug 26922, 10_php-fpm.conf causes mod_php doesn't work anymore. Why this file is needed if after I suppress it, all works?

Comment 2 Marc Krämer 2020-08-27 10:50:55 CEST

I assume this config is in conflict to your current config.
As stated in the other bug, php-fpm and apache_mod-php should not run in parallel

Comment 3 David Walser 2020-08-27 23:40:51 CEST

Apparently this issue happened on the Mageia infrastructure too, so something probably isn't right in the package.

Comment 4 Marc Krämer 2020-08-28 02:13:34 CEST

as beeing said in the other report, php-fpm and apache-mod_php should not be installed in parallel.

Comment 5 Marc Krämer 2020-08-28 02:16:54 CEST

we can totally remove any config for apache from php. I think it is no good idea to ship them.

Comment 6 Marc Krämer 2020-12-16 16:45:00 CET

I think this one is fixed.

Resolution: (none) => FIXED
Status: NEW => RESOLVED