Skip to Content.
Sympa Menu

en - Re: [sympa-users] Newbie configuration problem

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Phil Stracchino <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-users] Newbie configuration problem
  • Date: Fri, 19 Feb 2021 21:05:30 -0500

On 2/19/21 8:12 PM, Bill Oliver wrote:
> Thanks for the reply.  I thought about that, but it seems to be up.
>  Here's the status:
>
> systemctl status wwsympa
> ● wwsympa.service - WWSympa - Web interface for Sympa mailing list manager
>      Loaded: loaded (/lib/systemd/system/wwsympa.service; disabled;
> vendor preset: enabled)
>      Active: active (running) since Sat 2021-02-20 01:01:35 CET; 1h 8min ago
>     Process: 2010 ExecStart=/usr/bin/spawn-fcgi -F $FCGI_CHILDREN -s
> /var/run/wwsympa/wwsympa.socket -P /var/run/wwsympa/wwsympa.pid -u
> $FCGI_USER -g >
>    Main PID: 2019 (wwsympa.fcgi)
>       Tasks: 5 (limit: 7032)
>      Memory: 489.8M
>      CGroup: /system.slice/wwsympa.service
>              ├─2019 /usr/bin/perl /usr/lib/cgi-bin/sympa/wwsympa.fcgi
>              ├─2026 /usr/bin/perl /usr/lib/cgi-bin/sympa/wwsympa.fcgi
>              ├─2027 /usr/bin/perl /usr/lib/cgi-bin/sympa/wwsympa.fcgi
>              ├─2028 /usr/bin/perl /usr/lib/cgi-bin/sympa/wwsympa.fcgi
>              └─2029 /usr/bin/perl /usr/lib/cgi-bin/sympa/wwsympa.fcgi
>
> Feb 20 01:01:35 liberty.org spawn-fcgi[2010]: spawn-fcgi: child spawned
> successfully: PID: 2026
> Feb 20 01:01:35 liberty.org spawn-fcgi[2010]: spawn-fcgi: child spawned
> successfully: PID: 2027
> Feb 20 01:01:35 liberty.org spawn-fcgi[2010]: spawn-fcgi: child spawned
> successfully: PID: 2028
> Feb 20 01:01:35 liberty.org spawn-fcgi[2010]: spawn-fcgi: child spawned
> successfully: PID: 2029
> Feb 20 01:01:35 liberty.org systemd[1]: Started WWSympa - Web interface
> for Sympa mailing list manager.
> Feb 20 01:01:39 liberty.org wwsympa[2029]: info main:: WWSympa started,
> process 2029
> Feb 20 01:01:39 liberty.org wwsympa[2019]: info main:: WWSympa started,
> process 2019
> Feb 20 01:01:40 liberty.org wwsympa[2028]: info main:: WWSympa started,
> process 2028
> Feb 20 01:01:40 liberty.org wwsympa[2027]: info main:: WWSympa started,
> process 2027
> Feb 20 01:01:40 liberty.org wwsympa[2026]: info main:: WWSympa started,
> process 2026



OK, that certainly looks like wwsympa is alive. So Apache isn't talking
to it.

Is there anything written to your Apache error log when you try to hit it?
Is the socket path correct, and does the socket actually exist in
/run/sympa/ and with valid permissions?


minbar:root:~:6 # ls -l /var/run/sympa/
total 24
-rw-r--r-- 1 sympa sympa 5 Feb 16 23:58 archived.pid
-rw-r--r-- 1 sympa sympa 5 Feb 16 23:58 bounced.pid
-rw-r--r-- 1 sympa sympa 5 Feb 16 23:58 bulk.pid
-rw-r--r-- 1 sympa sympa 5 Feb 16 23:58 sympa_msg.pid
-rw-r--r-- 1 sympa sympa 5 Feb 16 23:58 task_manager.pid
-rw-r--r-- 1 root root 29 Feb 19 21:01 wwsympa.pid
srw------- 1 apache apache 0 Feb 19 21:01 wwsympa.socket=


I configured mine slightly differently from yours:

<IfDefine SYMPA>
ScriptAlias /sympa /usr/libexec/sympa/wwsympa.fcgi
Alias /static-sympa /var/spool/sympa/static_content

<Location /sympa>
SetHandler "proxy:unix:/var/run/sympa/wwsympa.socket|fcgi://"
Options +ExecCGI
Require all granted
</Location>

<Location /static-sympa>
Require all granted
</Location>
</IfDefine>


You might try adding the ScriptAlias directive if everything else looks
correct.


--
Phil Stracchino
Babylon Communications
address@concealed
address@concealed
Landline: +1.603.293.8485
Mobile: +1.603.998.6958



Archive powered by MHonArc 2.6.19+.

Top of Page