[Mailman-Users] Cannot access Mailman
Mark Sapiro
mark at msapiro.net
Tue Oct 21 00:58:45 CEST 2008
jewel.brueggeman-makda at washburn.edu wrote:
>Red Hat 5.1
>Apache 2
>Mailman 2.1.11
>
>
>I am a newbie with Linux and am trying to get apache to see my Mailman
>install. I have Apache's default home page up and running fine but am
>not seeing Mailman. I have tried the full path also:
>http://localhost/mailman/listinfo/ and it doesn;t display anything.
>It's blank. I have also created the mailman list and checked perms and
>everything looks fine. I have also read the archives regarding this
>issue and noticed the person was redirected to contact Apache, which I
>very well may have to, but wanted to check with this listserv first to
>make sure I am not missing anything. Here is what I have in my
>httpd.conf file.
>
><Directory "/">
> Options FollowSymLinks
> AllowOverride None
></Directory>
>
><Directory "/var/www/html">
> Options Indexes Includes FollowSymLinks
> AllowOverride None
> Allow from all
> Order allow,deny
></Directory>
>
><Directory "/var/www/icons">
> Options Indexes MultiViews
> AllowOverride None
> Allow from all
> Order allow,deny
></Directory>
>
><Directory "/var/www/cgi-bin">
> Options ExecCGI
> AllowOverride None
> Allow from all
> Order allow,deny
></Directory>
>
>ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/
>Alias /pipermail/ /usr/local/mailman/archives/public/
>
><Directory /usr/local/mailman/archives/>
> Options +FollowSymlinks
You're going to need
Order allow,deny
Allow from all
here, but that only affects public archive access.
></Directory>
>
><Directory /usr/local/mailman/cgi-bin>
> AllowOverride None
> Options +ExecCGI
> Order allow,deny
> Allow from all
></Directory>
>
>Here is a snippet of my httpd.log:
>[Mon Oct 20 10:47:16 2008] [notice] Apache/2.2.3 (Red Hat) configured --
>resuming normal operations
>[Mon Oct 20 10:47:20 2008] [error] [client 127.0.0.1] (13)Permission
>denied: exec of '/usr/local/mailman/cgi-bin/admindb' failed
Have you run "bin/check_perms"?
>[Mon Oct 20 10:47:20 2008] [error] [client 127.0.0.1] Premature end of
>script headers: admindb
>[Mon Oct 20 10:47:25 2008] [error] [client 127.0.0.1] attempt to invoke
>directory as script: /usr/local/mailman/cgi-bin/
>[Mon Oct 20 10:47:27 2008] [error] [client 127.0.0.1] attempt to invoke
>directory as script: /usr/local/mailman/cgi-bin/
If you want to be able to go to http://hostname/mailman/ and have it go
to the listinfo overview, you need
RedirectMatch ^/mailman[/]*$ /mailman/listinfo
in httpd.conf.
>[Mon Oct 20 10:47:31 2008] [error] [client 127.0.0.1] (13)Permission
>denied: exec of '/usr/local/mailman/cgi-bin/listinfo' failed
check_perms?
>[Mon Oct 20 10:47:31 2008] [error] [client 127.0.0.1] Premature end of
>script headers: listinfo
>[Mon Oct 20 10:57:32 2008] [notice] caught SIGTERM, shutting down
>[Mon Oct 20 10:59:01 2008] [notice] core dump file size limit raised to
>4294967295 bytes
>[Mon Oct 20 10:59:01 2008] [notice] SELinux policy enabled; httpd
>running as context system_u:system_r:httpd_t:s0
>[Mon Oct 20 10:59:01 2008] [notice] suEXEC mechanism enabled (wrapper:
>/usr/sbin/suexec)
Aha! You have both SELinux and SuEXEC Both of these affect permissions
in different ways: SuEXEC confilcts with Mailman's security model of
SETGID wrappers. Getting Mailman's web interface to run with SuEXEC is
somewhat involved. You will probably find additional error messages in
/var/log/httpd/suexec_log. It would be best to disable SuEXEC by
chmod u-s /usr/sbin/suexec
and restart Apache. See <http://httpd.apache.org/docs/2.0/suexec.html>.
If you do this and still have "permissions" issues, see
<http://www.mail-archive.com/mailman-users@python.org/msg33574.html>.
--
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users
mailing list