[Mailman-Users] Trying to setup mailman2.1 and following the docs on RHEL8.2

2020-09-09 Thread Stephen J. Turnbull 
Steven Jones writes:
 > I get this failure message,
 > 
 > ===
 > [root@vuwunicomailmp1 system]# pwd
 > /usr/lib/systemd/system
 > [root@vuwunicomailmp1 system]# for X in mailman-*.timer ; do systemctl 
 > enable $X && systemctl start $X ; done
 > Invalid unit name "mailman-*.timer" was escaped as "mailman-\x2a.timer" 
 > (maybe you should use systemd-escape?)
 > Failed to enable unit: Unit file mailman-\x2a.timer does not exist.
 > [root@vuwunicomailmp1 system]#
 > ===
 > 
 > help please.

That's a Red Hat problem.  Apparently systemd expected to find a set
of files matching the glob "mailman-*.timer" somewhere, and they
weren't there. Fixing this will require knowledge of Red Hat package
software layout that I don't have.

That is not a Mailman-supplied set of files, it's some sort of
automation supplied by Red Hat.  I'm not even sure what it does; it
might be the standard Mailman cron jobs, but the extension ".timer"
makes me unsure.  ".timer" may be a systemd-ism for cron jobs, but I'm
not a Red Hat user so that's purely a guess.

Maybe somebody else here can provide real help, but I would advise
going to Red Hat support for this for quicker response.  Not sure what
Abhilash uses, but Mark is mostly Debian/Ubuntu I think, and he's on
vacation in a Internet-free zone for the next week.

Steve

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Apache/mailman2 on RHEL8.2

2020-09-09 Thread Stephen J. Turnbull 
Steven Jones writes:

 > Trying to do a setup,

Did you get the issue with missing mailman-*.timer files sorted, or
are you problem-solving in parallel?

 > I get the default page OK but when I follow the link,
 > 
 > "List administrators, you can visit the list admin overview page to
 > find the management interface for your list."
 > 
 > I get,
 > 
 > Not Found
 > 
 > The requested URL /mailman/admin was not found on this server.

I'm guessing that you're using Red Hat packages (or perhaps RPMs from
a 3rd party repository) to install.

Both problems seem to stem from a lack of, or failed, configuration of
Mailman and systems (systemd, Apache) that it interacts with.

My first guess is that Mailman proper and files that interface Mailman
with other packages are split into separate packages, and you need to
install those "interface/configuration" packages as well.  (Although
they should be specified as dependencies for the Mailman package
itself, and automatically installed or at least get a loud warning
that dependencies aren't satisfied.)

The second possibility is that packages were incompletely installed so
that the configuration step did not occur.  If so, it's possible that
your package manager can diagnose this, and try to complete the
installation process.

Again, I would say that checking with the package provider you are
more likely to get help than from Mailman sources, although there are
probably Red Hat users here.

If you don't get help through those channels, it would help if you can
tell us exactly how you installed Mailman, and send us your Mailman,
Apache, and MTA (if nothing else is configured, I bet you're going to
have MTA problems too) configurations.

It's not hard to install Mailman from source.  There's one binary that
needs to be compiled from C source; everything else is Python.
Probably somebody can help with manual configuration of systemd so
that cron jobs get run and Mailman's runners get started automatically
at boot, etc, and many of us can help with manual configuration of
Apache and several other webservers.

The problem for us helping with distro packages is that the distros
tend to have somewhat idiosyncratic file system layouts (they
interpret the Filesystem Hierarchy Standard differently) and manage
automatic configuration of MTAs, webservers, and daemon management
differently.  If you don't use that distro, you're lost trying to help
somebody else.  However, with installation from source, there's a
traditional layout under /usr/local that we all know well.  The main
issue with installation from source is that if you upgrade, you need
to do the installation manually again and may need to tweak
configurations.  But with Mailman 2 basically at EOL, you shouldn't
need to upgrade or tweak (no new features).

We'll do what we can, but that's the situation.

Steve
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Apache/mailman2 on RHEL8.2

2020-09-09 Thread Steven Jones 
Hi,

Problem solving in parallel, and I have another one.

Yes I think it is mostly down to RHat doing things "their way" but their method 
is not documented terribly well, which is usual for them. So I am trying to 
follow Mailman docs which it seems dont totally apply and I seem to be making a 
mess of it. Once there I will have docs for it.

The trouble with using source is then you have to maintain it out of the 
regular OS patching regime which would mean more time and anti-social hours.  
If I use the RH binary it seems to run OK once going, like 15years+.

Yes I know Mailman2 is EOL but with the Virus impact on our budget there is no 
money  and no skills for moving to anything newer/better and 2~3 years should 
see it no longer used/needed.



regards

Steven


From: Stephen J. Turnbull 
Sent: Thursday, 10 September 2020 2:25 AM
To: Steven Jones 
Cc: mailman-users@python.org 
Subject: [Mailman-Users] Apache/mailman2 on RHEL8.2

Steven Jones writes:

 > Trying to do a setup,

Did you get the issue with missing mailman-*.timer files sorted, or
are you problem-solving in parallel?

 > I get the default page OK but when I follow the link,
 >
 > "List administrators, you can visit the list admin overview page to
 > find the management interface for your list."
 >
 > I get,
 >
 > Not Found
 >
 > The requested URL /mailman/admin was not found on this server.

I'm guessing that you're using Red Hat packages (or perhaps RPMs from
a 3rd party repository) to install.

Both problems seem to stem from a lack of, or failed, configuration of
Mailman and systems (systemd, Apache) that it interacts with.

My first guess is that Mailman proper and files that interface Mailman
with other packages are split into separate packages, and you need to
install those "interface/configuration" packages as well.  (Although
they should be specified as dependencies for the Mailman package
itself, and automatically installed or at least get a loud warning
that dependencies aren't satisfied.)

The second possibility is that packages were incompletely installed so
that the configuration step did not occur.  If so, it's possible that
your package manager can diagnose this, and try to complete the
installation process.

Again, I would say that checking with the package provider you are
more likely to get help than from Mailman sources, although there are
probably Red Hat users here.

If you don't get help through those channels, it would help if you can
tell us exactly how you installed Mailman, and send us your Mailman,
Apache, and MTA (if nothing else is configured, I bet you're going to
have MTA problems too) configurations.

It's not hard to install Mailman from source.  There's one binary that
needs to be compiled from C source; everything else is Python.
Probably somebody can help with manual configuration of systemd so
that cron jobs get run and Mailman's runners get started automatically
at boot, etc, and many of us can help with manual configuration of
Apache and several other webservers.

The problem for us helping with distro packages is that the distros
tend to have somewhat idiosyncratic file system layouts (they
interpret the Filesystem Hierarchy Standard differently) and manage
automatic configuration of MTAs, webservers, and daemon management
differently.  If you don't use that distro, you're lost trying to help
somebody else.  However, with installation from source, there's a
traditional layout under /usr/local that we all know well.  The main
issue with installation from source is that if you upgrade, you need
to do the installation manually again and may need to tweak
configurations.  But with Mailman 2 basically at EOL, you shouldn't
need to upgrade or tweak (no new features).

We'll do what we can, but that's the situation.

Steve

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Mailman CGI Error-Group mismatch error

2020-09-09 Thread Fernando 

Did you find the solution?

I am receiving a similar error  on mailman-2.1.29-lp152.6.13.x86_64   on 
Opensuse Leap 15.1



 Mailman CGI error!!!

The Mailman CGI wrapper encountered a fatal error. This entry is being 
stored in your syslog:


Failure to exec script. WANTED gid 483, GOT gid 8.


The correct gid I think it should be 8 (wwwrun), 483  is vnc so it has 
no sense  wanting it.



tutatis:/usr/lib/mailman/cgi-bin # ls -l
total 144
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 admin
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 admindb
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 confirm
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 create
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 editarch
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 edithtml
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 listinfo
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 options
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 private
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 rmlist
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 roster
-rwxr-sr-x 1 root mailman 10848 Jun  9 06:22 subscribe
tutatis:/usr/lib/mailman/cgi-bin #




best regards


Hi, I received the following error this morning. So I rerun configure 
again with the following command: ./configure --with-cgi-id=apache 
--prefix=/var/mailman. I'm still getting the same error. Is there any 
place that I can look for so that I can debug this problem better? 
Perhaps, looking at the config history file or something. Any other 
places that I can check the cause of this error?


"Mailman CGI error!!!

The Mailman CGI wrapper encountered a fatal error. This entry is being 
stored in your syslog: Group mismatch error. Mailman expected the CGI 
wrapper script to be executed as group "nobody", but the system's web 
server executed the CGI script as group "apache". Try tweaking the web 
server to run the script as group "nobody", or re-run configure, 
providing the command line option `--with-cgi-gid=apache'."


Thanks


--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Mailman CGI Error-Group mismatch error

2020-09-09 Thread Mark Sapiro 
On 9/8/20 1:49 AM, Fernando wrote:
> Did you find the solution?
> 
> I am receiving a similar error  on mailman-2.1.29-lp152.6.13.x86_64   on
> Opensuse Leap 15.1
> 
> 
>  Mailman CGI error!!!
> 
> The Mailman CGI wrapper encountered a fatal error. This entry is being
> stored in your syslog:
> 
> Failure to exec script. WANTED gid 483, GOT gid 8.
> 
> 
> The correct gid I think it should be 8 (wwwrun), 483  is vnc so it has
> no sense  wanting it.


Your wrappers are compiled to want that gid. You need to recompile them
by running configure with the option --with-cgi-id=wwwrun and then `make
install`.  See the FAQ article at .


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Apache/mailman2 on RHEL8.2

2020-09-09 Thread Jim Tittsler 

On 2020-09-09 7:35 a.m., Steven Jones wrote:

I get the default page OK but when I follow the link,

"List administrators, you can visit the list admin overview page to find the 
management interface for your list."

I get,

Not Found


Are there virtual domains involved on that server?  Is the *host* (and 
protocol) part of that link correct?  (If you or the Redhat installation 
script changed URL names part way through the installation process, you 
may need to use fix_url.py to correct links within the web interface. 
 )

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/