FAQ
Hi,

I'm trying to install Mailman 2.1.12. It compiled fine, with the
following flags:
./configure --prefix=/var/lib/mailman --with-username=list \
--with-groupname=list \
--with-mail-gid=daemon --with-cgi-gid=w-lists \
--without-permcheck --with-mailhost=localhost \
--with-urlhost=localhost


Then I copied the cgi-bin scripts to the /var/www/w-lists directory.
This step is necessary to get the scripts inside the suexec environment.

When I go to <URL>/mailman/listinfo, I get the following page text:
-----------------
Bug in Mailman version 2.1.12

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited,
but the webmaster can find this information in the Mailman error logs.
---------------
The mailman/error.log file is completely empty. How can I find out
what's going wrong here?

Kind regards,

Remco Poelstra

Search Discussions

  • Mark Sapiro at Jul 21, 2009 at 10:38 pm

    Remco Poelstra wrote:
    I'm trying to install Mailman 2.1.12. It compiled fine, with the
    following flags:
    ./configure --prefix=/var/lib/mailman --with-username=list \
    --with-groupname=list \
    --with-mail-gid=daemon --with-cgi-gid=w-lists \

    This won't work. Your Mailman group is 'list'. With suEXEC, your
    wrappers cannot be SETGID, thus Apache must invoke them as group
    'list' and this must also be the group that the wrappers expect to be
    invoked as. I.e. --with-cgi-gid=list

    --without-permcheck --with-mailhost=localhost \
    --with-urlhost=localhost

    If you want to actually create and use lists, --with-mailhost and
    --with-urlhost need to be fully qualified domain names, not
    'localhost. You can fix this after the fact by setting
    DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST in mm_cfg.py followed by

    VIRTUAL_HOSTS.clear()
    add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

    Then I copied the cgi-bin scripts to the /var/www/w-lists directory.
    This step is necessary to get the scripts inside the suexec environment.

    When I go to <URL>/mailman/listinfo, I get the following page text:
    -----------------
    Bug in Mailman version 2.1.12

    We're sorry, we hit a bug!

    Please inform the webmaster for this site of this problem. Printing of
    traceback and other system information has been explicitly inhibited,
    but the webmaster can find this information in the Mailman error logs.
    ---------------
    The mailman/error.log file is completely empty. How can I find out
    what's going wrong here?

    If you're looking at /var/lib/mailman/logs/error (based on your
    configure command) and it is empty or non-existent, fix permissions so
    your web server can create/write it.

    Alternatively, you can modify /var/lib/mailman/scripts/driver and change

    STEALTH_MODE = 1

    to

    STEALTH_MODE = 0

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Remco Poelstra at Jul 22, 2009 at 7:05 am
    Mark Sapiro schreef:
    This won't work. Your Mailman group is 'list'. With suEXEC, your
    wrappers cannot be SETGID, thus Apache must invoke them as group
    'list' and this must also be the group that the wrappers expect to be
    invoked as. I.e. --with-cgi-gid=list

    If you want to actually create and use lists, --with-mailhost and
    --with-urlhost need to be fully qualified domain names, not
    'localhost. You can fix this after the fact by setting
    DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST in mm_cfg.py followed by

    VIRTUAL_HOSTS.clear()
    add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

    If you're looking at /var/lib/mailman/logs/error (based on your
    configure command) and it is empty or non-existent, fix permissions so
    your web server can create/write it.

    Alternatively, you can modify /var/lib/mailman/scripts/driver and change

    STEALTH_MODE = 1

    to

    STEALTH_MODE = 0
    Hi,

    Thanks for the tips. Since I had to recompile to get the cgi-gid
    correct, I also directly fixed the hostname flags, just to save myself
    some trouble later on. Now I also instantly got some working logs files,
    so it was all very close related.
    General note: Maybe it would be nice if Mailman would not say `We hit a
    bug`, since that?s not really correct, but say more something like
    ?permission error?.

    Regards,

    Remco Poelstra
  • Mark Sapiro at Jul 22, 2009 at 3:29 pm

    Remco Poelstra wrote:
    General note: Maybe it would be nice if Mailman would not say `We hit a
    bug`, since that?s not really correct, but say more something like
    ?permission error?.

    This page is produced for any uncaught exception encountered by any of
    the web CGI scripts. The intent is to produce something without going
    into a lot of analysis of the exception which could trigger another
    exception, so it needs to be a generic message. "We hit a bug" is
    probably often not strictly correct, but other things like "permission
    error" or "configuration error" would be even less correct in general.

    Possibly "We hit an error" or "We hit an exception" might be
    technically more accurate, but I'd be concerned that these tend to
    imply a user error which is not the case.

    --
    Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedJul 20, '09 at 11:35a
activeJul 22, '09 at 3:29p
posts4
users2
websitelist.org

2 users in discussion

Mark Sapiro: 2 posts Remco Poelstra: 2 posts

People

Translate

site design / logo © 2022 Grokbase