Skip to Content.
Sympa Menu

en - Re: [sympa-users] How to debug web interface failure?

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: "William F. Dudley Jr." <address@concealed>
  • To: "Stefan Hornburg (Racke)" <address@concealed>, address@concealed
  • Subject: Re: [sympa-users] How to debug web interface failure?
  • Date: Thu, 29 Jul 2021 15:22:00 -0300

Racke et al,

Using a path (like sympa.dudley.nu/wws) doesn't change the outcome, as I
already tried and as you discovered for yourself. You still get bupkus.

The machine is running FreeBSD 11.4-RELEASE-p9 i386
Web server is Apache/2.4.48 (FreeBSD)

Here's the Apache virtual host stuff, entirely unchanged since this
was working 14 months ago:

<VirtualHost *:80>
ServerName sympa.dudley.nu
ServerAdmin address@concealed
Alias /.well-known/ /usr/local/www/sympa/docs/.well-known/
ErrorLog /var/log/sympa.dudley.nu-error_log
CustomLog /var/log/sympa.dudley.nu-access_log common
LogLevel warn
DocumentRoot /usr/local/www/sympa
RewriteEngine on
RewriteRule ^$ /cgi-bin/wwsympa-wrapper.fcgi [L]
RewriteRule ^/static-sympa/(.*)$ /docs/static/$1 [L]
RewriteRule ^/(.*)$ /cgi-bin/wwsympa-wrapper.fcgi/$1 [L]
Alias /static-sympa /usr/local/share/sympa/static
<Location /cgi-bin>
require all granted
Options +FollowSymLinks
</Location>
</VirtualHost>

These are the WWSympa related parameters from sympa.conf, also unchanged in
14 months (all other www-related settings are commented out):

wwsympa_url http://sympa.dudley.nu
static_content_url /static-sympa
static_content_path /usr/local/share/sympa/static
log_facility LOCAL1
default_home home
cookie_domain localhost
cookie_expire 0
cookie_refresh 60
use_html_editor 0
use_fast_cgi 0

This exists and has stuff in it:
ls /usr/local/share/sympa/static
css/ fonts/ icons/ js/ pictures/
and is owned by and readable and writable by sympa:
ls -ld /usr/local/share/sympa/static
drwxr-xr-x 7 sympa sympa 512 May 27 2020 /usr/local/share/sympa/static/

Here's the cgi-bin directory:
/var/www/sympa/cgi-bin> ls -l
total 2
-rw-r--r-- 2 sympa sympa 35 May 13 2020 robot.conf
lrwxr-xr-x 1 root wheel 31 May 18 2020 sympa.conf@ ->
/usr/local/etc/sympa/sympa.conf
lrwxr-xr-x 1 root wheel 45 May 18 2020 wwsympa-wrapper.fcgi@ ->
/usr/local/libexec/sympa/wwsympa-wrapper.fcgi
lrwxr-xr-x 1 root wheel 37 May 18 2020 wwsympa.fcgi@ ->
/usr/local/libexec/sympa/wwsympa.fcgi

Here are those files pointed to by the symbolic links above:
/usr/local/libexec/sympa> ls -l wwsympa*
-rwsr-sr-x 1 sympa sympa 4448 May 4 07:37 wwsympa-wrapper.fcgi*
-r-xr-xr-x 1 root wheel 598109 May 4 07:37 wwsympa.fcgi*

cat robot.conf
wwsympa_url http://sympa.dudley.nu

I don't understand this question:
> Also what do you use for the WWSympa service itself?

Finally: I'm using http because I haven't yet gotten a Let's Encrypt
Certificate, and I won't bother if this thing doesn't start acting a lot more
robust in the future. :-)

Thanks,
Bill Dudley

---------- Original Message -----------
From: "Stefan Hornburg (Racke)" <address@concealed>
To: "William F. Dudley Jr." <address@concealed>, address@concealed
Sent: Thu, 29 Jul 2021 17:00:55 +0200
Subject: Re: [sympa-users] How to debug web interface failure?

> On 29/07/2021 16:47, William F. Dudley Jr. wrote:
> > Racke and all who replied,
> >
> > Thanks for the reply, however I'm no closer to a resolution.
> >
> > I turned log_level to 1.
> >
> > Now the sympa.log file shows this:
> >
> > Jul 29 10:33:40 dudley wwsympa[98520]: info main:: WWSympa started,
> > process 98520
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: ORIG_PATH_INFO=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: ORIG_SCRIPT_NAME=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: PATH_INFO=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: QUERY_STRING=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: REMOTE_ADDR=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: REMOTE_HOST=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: REQUEST_METHOD=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: SCRIPT_NAME=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: SERVER_NAME=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: SERVER_PORT=
> > Jul 29 10:33:40 dudley wwsympa[98520]: debug main:: SYMPA_DOMAIN=
> >
> > Which is not terribly enlightening. This is repeated three times:
> > once each for the duplicate fetch of "/", and once for the fetch
> > of /favicon.ico. All return 421 error code.
> >
> > This is the URL in the browser URL window:
> > http://sympa.dudley.nu/
> >
> > This is the value of wwsympa_url in sympa.conf:
> > wwsympa_url http://sympa.dudley.nu
> >
> > I changed the latter to have a trailing '/', restarted sympa. No change.
> > They look identical to me.
> >
> > Now what?
> >
> > Bill Dudley
>
> Hello Bill,
>
> you are usually use a path part in the URL for WWSympa, e.g.
>
> http://sympa.dudley.nu/sympa or http://sympa.dudley.nu/wws.
>
> But your Sympa instance doesn't receive any information via the HTTP
> environment, so something is wrong with your setup.
>
> Please share your choice of the webserver and the WWSympa related
> configuration.
>
> Also what do you use for the WWSympa service itself?
>
> BTW: Nowadays there is no excuse to use http:// :-)
>
> Regards
> Racke
>
> >
> >
> > ---------- Original Message -----------
> > From: "Stefan Hornburg (Racke)" <address@concealed>
> > To: address@concealed
> > Sent: Thu, 29 Jul 2021 07:04:42 +0200
> > Subject: Re: [sympa-users] How to debug web interface failure?
> >
> >> On 29/07/2021 05:24, William F. Dudley Jr. wrote:
> >>> Sympa users,
> >>>
> >>> I installed sympa a year ago with the intention of migrating from
> >>> mailman 2. I never finished the project, but now I'm forced to abandon
> >>> mailman 2, so I must finish this.
> >>>
> >>> Machine is running FreeBSD 11.4-RELEASE-p9 i386.
> >>> Apache24-2.4.48 (FreeBSD package revision of Apache 2.4)
> >>> mysql57-server-5.7.34 (which sympa seems happy with)
> >>> sympa-6.2.62 (latest FreeBSD package)
> >>>
> >>> I had everything working -- web interface and the ability to send emails
> >>> that passed gmail's DMARC tests.
> >>>
> >>> Now, however, I find the web interace returns an entirely empty page.
> >>> Nothing at all. I can still send emails to my "test" list, so Sympa
> >>> is still "working" as a mailing list.
> >>>
> >>> The web access_log file shows this:
> >>> 98.109.205.15 - - [28/Jul/2021:22:45:18 -0400] "GET / HTTP/1.1" 421 1
> >>> 98.109.205.15 - - [28/Jul/2021:22:45:28 -0400] "GET / HTTP/1.1" 421 1
> >>>
> >>> There are TWO lines for every attempted access.
> >>>
> >>> All attempts to access the web interface return a blank page and show
> >>> a 421 code in the log file.
> >>>
> >>> (Yes, that's my own IP).
> >>>
> >>> The error_log file has no new entries at all.
> >>>
> >>> How do I debug why the web interface is broken? It worked, I ignored it
> >>> for a year, and now it's broken. There have been no changes to the
> >>> machine
> >>> other than regular security updates from freebsd.org.
> >>
> >> This can happen when the URL in the browser is different from the URL
> >> in the wwsympa_url configuration parameter.
> >>
> >> If you use log_level = 1, you will see the headers that WWSympa is
> >> using in the log file.
> >>
> >> Also it is recommended to use FreeBSD 13, to avoid performance
> >> problems due to FreeBSD bugs in older releases.
> >>
> >> Regards
> >> Racke
> >>
> >>>
> >>> Thanks,
> >>> Bill Dudley
> >>> New Jersey, USA
> >>>
> >>>
> >>
> >> --
> >> Ecommerce and Linux consulting + Perl and web application programming.
> >> Debian and Sympa administration.
> > ------- End of Original Message -------
> >
> >
>
> --
> Ecommerce and Linux consulting + Perl and web application programming.
> Debian and Sympa administration.
------- End of Original Message -------




Archive powered by MHonArc 2.6.19+.

Top of Page