Le Wed, Jul 28, 2021 at 01:11:10PM +0200, Patrick Cernko a écrit : > Hi, > > On 20/06/2021 13:28, Philipp Kolmann wrote: > > I have faced the same issue and with several sources across the > > internet I was able to fix it for me. > > > > 1.) Adding a wwsympa.service > > 2.) Changing the apache config. > > > > Maybe this helps someone facing the issues while updating to bullseye. > > > > Thanks for this fix. However, it might be worth mentioning that you have to > enable apache module proxy_fcgi (and it's dependency proxy) for the handler > to work: > > a2enmod proxy_fcgi # will enable proxy as dependency > > In my setup apache2 otherwise answered all requests to /wws with a 404 with > no hint, what's missing. Enabling module proxy at least gave: > > AH01144: No protocol handler was valid for the URL /wws (scheme 'unix'). If > you are using a DSO version of mod_proxy, make sure the proxy submodules are > included in the configuration using LoadModule. > > Ah, and you have to install package spawn-fcgi obviously. >
A few notes after experiencing the same issue, upgrading a stable server : - instructions for adding the wwsympa.service are documented in upstream docs (https://sympa-community.github.io/manual/install/configure-http-server-spawnfcgi.html), should you beunfamiliar with systemd - the apache config file patch mentioned in https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=980561;filename=apache-sympa.diff;msg=10 gives a hint at to how to change the /etc/apache2/conf-available/sympa.conf file. In my case, I preserved the /wws path, in "<Location /wws>" to align with the previous "ScriptAlias /wws" Hope this helps, Best regards, -- Olivier BERGER https://www-public.imtbs-tsp.eu/~berger_o/ - OpenPGP 2048R/0xF9EAE3A65819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France)
