Skip to Content.
Sympa Menu

en - Re: [en@sympa] [External] Re: Beginner's Help

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: VTR <address@concealed>
  • To: address@concealed
  • Subject: Re: [en@sympa] [External] Re: Beginner's Help
  • Date: Mon, 29 May 2023 11:43:47 -0400

Hi Phil:

I am now using “Location” and have verified locations to my /etc/httpd/conf/httpd.conf file as follows:

$ sudo find / -name "wwsympa.fcgi"
/usr/libexec/sympa/wwsympa.fcgi
$ sudo find / -name "static_content"
/usr/share/sympa/static_content

But I am still not getting the sympa website:


I looked in error_log and found:
[Mon May 29 14:02:09.907997 2023] [alias:warn] [pid 5168] AH00671: The Alias directive in /etc/httpd/conf.d/sympa.conf at line 34 will probably never match because it overlaps an earlier Alias.
[Mon May 29 14:02:09.910582 2023] [lbmethod_heartbeat:notice] [pid 5168] AH02282: No slotmem from mod_heartmonitor
[Mon May 29 14:02:09.910624 2023] [http2:warn] [pid 5168] AH10034: The mpm module (prefork.c) is not supported by mod_http2. The mpm determines how things are processed in your server. HTTP/2 has more demands in this regard and the currently selected mpm will just not do. This is an advisory warning. Your server will continue to work, but the HTTP/2 protocol will be inactive.
[Mon May 29 14:02:09.914102 2023] [mpm_prefork:notice] [pid 5168] AH00163: Apache/2.4.57 () configured -- resuming normal operations
[Mon May 29 14:02:09.914120 2023] [core:notice] [pid 5168] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon May 29 14:03:01.781218 2023] [authz_core:error] [pid 5169] [client x.x.x.x:44031] AH01630: client denied by server configuration: /usr/libexec/sympa/wwsympa.fcgi

But the error on the first line struck me weird, so I navigated to the /etc/httpd/conf.d/sympa.conf file and found almost identical code to the stanza you supplied:

# cat /etc/httpd/conf.d/sympa.conf
### Apache httpd 2.4 configuration for Sympa
##
## Note: As of 6.2.35-0.1.b.1, mod_proxy_fcgi was adopted instead of mod_fcgid.
## * You have to edit /etc/sysconfig/sympa as described in it.
## * Then, you have to run separate fastCGI services wwsympa and/or sympasoap:
##   systemctl start wwsympa
##   systemctl start sympasoap

## Definition of Sympa FastCGI server.
<IfModule mod_proxy_fcgi.c>
    # If you changed wwsympa_url in sympa.conf, change this path too.
    <Location /sympa>
        SetHandler "proxy:unix:/var/run/sympa/wwsympa.socket|fcgi://"
        # Don't forget to edit lines below!
        Require local
       #  Require all granted
    </Location>

#    # You may uncomment following lines to enable SympaSOAP feature.
#    <Location /sympasoap>
#        SetHandler "proxy:unix:/var/run/sympa/sympasoap.socket|fcgi://"
#        # Don't forget to edit lines below!
#        Require local
#        #Require all granted
#    </Location>
</IfModule>

## Other static contents
<Location /static-sympa>
    Require all granted
</Location>
Alias /static-sympa/css /var/lib/sympa/css
Alias /static-sympa/pictures /var/lib/sympa/pictures
Alias /static-sympa /usr/share/sympa/static_content

## If your host is dedicated to Sympa:
#RewriteEngine on
#RewriteRule ^/?$ /sympa [R=301]

I modified this file to match your code, and now I am getting this error when accessing the sympa webpage:

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

I was getting “Forbidden” before, so “Server Unavailable” is a new message.

------

On May 27, 2023, at 7:51 PM, Phil Stracchino <address@concealed> wrote:

On 5/27/23 18:10, VTR wrote:
Hi Phil,
Thanks for replying, but I don’t understand.
Are you saying that I should have used the word “Location” instead of “Directory” in my /etc/httpd/conf/httpd.conf file?


Yes.  I gave it to you correctly configured (for the given set of paths).  You changed the "Location" directive to "Directory", *which means a different thing*, and it is completely unsurprising that it no longer works.


Change "Directory" back to "Location", make certain that the paths in the ScriptAlias and the Alias are correct (point to the actual location of the files), and if nothing *else* is wrong, it SHOULD work.

If it still does not work, then something else is wrong, but we should be able to tell *what* from the error messages.



--
 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