The mailing list for listmasters using Sympa

["Christian H. Kuhn" <address@concealed>]

Hi cmb,

Am 10.09.2025 um 16:43 schrieb "C. Bernard" (via en Mailing List):
> the "=" at the end of your last line is some "ls" linuxism?
Yes. It just means "socket".

> And where is the "/run/sympa/sympasoap.socket" entry? (I would remove 
> the soap config part / localtion for the moment, until the basic GUI works)
Removed.

> Have you tried the retype the "|" in your config? (Maybe pasting did 
> something bad in any of the copied config).
That is a problem i had in /etc/sympa/transport.sympa, but not here. But 
i gave it a try. Without avail. And the space does not matter in linux.

> Do you have the proper module in httpd.conf...?:
>
> LoadModule proxy_fcgi_module libexec/apache24/mod_proxy_fcgi.so

It is enabled by a2enmod. If i load it explicitly, a warning is logged 
that the module already is loaded.

> I have only one alias for the entire tree (and no optional soap API 
> configured) :

It seems that in my distro there are two paths. css and pictures are in 
/var/lib/sympa, static_content is in /usr/share/sympa. So i stay with 
the docs.

> I use spawn
Me too. Ubuntu is a systemd distro.

> [root@beastly /usr/local/etc/apache24]# grep -E 'spawn|sympa' /etc/rc.conf
> sympa_enable="YES"

thats
# systemctl enable sympa.service
# systemctl start sympa.service
here.

> spawn_fcgi_enable="YES"
> #spawn_fcgi_enable="NO"
> spawn_fcgi_app="/usr/local/bin/perl"
> spawn_fcgi_app_args="/usr/local/libexec/sympa/wwsympa.fcgi"
> spawn_fcgi_bindsocket="/var/run/sympa/wwsympa.socket"
> spawn_fcgi_bindsocket_mode="0600 -U www"
> spawn_fcgi_username="sympa"
> spawn_fcgi_groupname="sympa"

I fear that is where i’m going wrong. I installed spawn by apt without 
further configuring, as the docs didn’t mention any. Seems i was wrong.

I created /etc/spawn-fcgi/.root
USERID=www̵-data
GROUPID=www-data
FCGIPROGRAM="/usr/bin/perl /usr/lib/cgi-bin/sympa/wwsympa.fcgi"
FCGISOCKET=/run/spawnfcgi/spawnfcgi.socket
FCGIMODE=0600
FCGIPID=/run/spawnfcgi/spawnfcgi.pid

copied /usr/share/doc/spawn-fcgi/examples/spawn-fcgi_launcher to 
/usr/libexec/, removed the need for a CONF_FILE parameter, edited the 
CONF_FILE to /etc/spawn-fcgi/.conf instead of ${1}.conf, changed the 
required parameters and called
env - ${SPAWNFCGI} -s ${FCGISOCKET} -M ${FCGIMODE} -u ${USERID} -g 
${GROUPID}-P ${FCGIPID} -f ${FCGIPROGRAM}

I do not really know what i do there, i just read the man and your mail 
and hoped for the best. But in the end, spawn-fcgi was running.

Now i have the sockets for spawn-fcgi und wwsympa:
root@bywater ~ # ll /run/spawnfcgi/
total 4
drwxr-x---  2 www-data sympa      80 Sep 11 17:34 ./
drwxr-xr-x 46 root     root     1380 Sep 11 17:30 ../
-rw-r--r--  1 root     root        7 Sep 11 17:34 spawnfcgi.pid
srw-------  1 www-data www-data    0 Sep 11 17:34 spawnfcgi.socket=
root@bywater ~ # ll /run/sympa/
total 20
drwxr-xr-x  2 sympa    sympa     160 Sep 11 17:37 ./
drwxr-xr-x 46 root     root     1380 Sep 11 17:30 ../
-rw-r--r--  1 sympa    sympa       8 Sep 11 16:47 archived.pid
-rw-r--r--  1 sympa    sympa       8 Sep 11 16:47 bounced.pid
-rw-r--r--  1 sympa    sympa       8 Sep 11 16:47 bulk.pid
-rw-r--r--  1 sympa    sympa       8 Sep 11 16:47 sympa_msg.pid
-rw-r--r--  1 sympa    sympa       8 Sep 11 16:47 task_manager.pid
srw-rw----  1 www-data www-data    0 Sep  9 22:11 wwsympa.socket=

But still https://www.sglasker.de/sympa throws a 404. Can it be that 
apache looks for fcgi://localhost instead of 
unix:/run/spawnfcgi/pawnfcgi.socket what leads to the error?

TIA
QNo