Fwd: [Mailman-Users] Mailman CGI error!!!

[jpsota at gmail.com]

Hi, I'm still having trouble with installing Mailman. The original
error is as follows:

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

Failure to lookup via getgrgid() the group info for group id -1 that
this Mailman CGI wrapper is executing under.
This is probably due to an incorrectly configured system and is not a
Mailman problem

I listed some responses to questions people on the list asked. I think
there's a system configuration problem, but I'm not sure if it's with
my users or groups or apache config etc. I'd really appreciate the
help. I'm also willing to perform a brute force solution.

Thanks,
jim

---------- Forwarded message ----------
From: jpsota at gmail.com <jpsota at gmail.com>
Date: Mon, 7 Feb 2005 12:48:39 -0800
Subject: Re: [Mailman-Users] Mailman CGI error!!!
To: John Dennis <jdennis at redhat.com>


John,

I'm running Fedora Core 2, and here's the info that yum info gives:

Gathering header information file(s) from server(s)
Server: Fedora Core 2 - i386 - Base
Server: Fedora Core 2 - i386 - Released Updates
Finding updated packages
Downloading needed headers
Looking in Available Packages:

Looking in Installed Packages:
Name   : mailman
Arch   : i386
Version: 2.1.5
Release: 7
Size   : 27.95 MB
Group  : Applications/Internet
Repo   : Locally Installed
Summary: Mailing list manager with built in Web access.

id mailman gives the exact line as below, and check_perms gives "no
problems". is there something else I can try?

Thanks a lot.
jim


On Fri, 04 Feb 2005 16:48:50 -0500, John Dennis <jdennis at redhat.com> wrote:
> Here's a couple of other things to try:
>
> What does the command "id mailman" give you?
>
> It should look something like this:
>
> uid=41(mailman) gid=41(mailman) groups=41(mailman)
>
> try running the script in the mailman bin directory called check_perms,
> does it give errors? If so try running it with the -f option to fix the
> problems.
>
> BTW, if this is a redhat rpm you should not be having any of these
> problems, if it is a redhat rpm and you are having these problems then
> something is uniquely amiss on your system.
>
>