Changing SELinux to permissive worked!
I edited the /etc/selinux/config SELINUX=permissive Thank you! Jewel -----Original Message----- From: Mailman-Users [mailto:[email protected]] On Behalf Of Mark Sapiro Sent: Wednesday, June 29, 2016 6:24 PM To: [email protected] Subject: Re: [Mailman-Users] Not able to access Mailman web interface On 6/29/16 9:12 AM, Jewel Brueggeman-Makda wrote: > I am trying to setup a new instance of Mailman 2.1.22 on RedHat 7.2 using > Apache 2.4. The plan is to move mailman from an old server to the new one. > For the moment I am just trying to get it setup. > > Apache's home page is fine but as soon as I try to go to > webserver/mailman/listinfo I get the generic "Bug in Mailman" error page. > There is nothing in the mailman logs to help me. > > The httpd logs only point to a cgi error. One example of the lines in the > logs are: > [cgi:error] [pid 20032] [client 198.256.23.205.54:12345\ AH01215: > \tHTTP_ACCEPT_ENCODING: gzip, deflate AH01215 seems to be a generic cgi error code so that doesn't say much. Were there more lines to this log message? Usually any cgi stderr output is logged. > Below is what I have in my httpd.comf file: > <Directory "/var/www"> > AllowOverride None > Require all granted > </Directory> > > <Directory "/var/www/html"> > Options Indexes FollowSymLinks > AllowOverride None > Require all granted > </Directory> > > <Directory "/usr/local/mailman/cgi-bin/"> > AllowOverride None > Options None > Require all granted > </Directory> > > Alias /pipermail/ /usr/local/mailman/archives/public/ > ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ That all looks OK and anyway, you are seeing the "We hit a bug" screen and not just a 500 error, so the Mailman script is executing. > I have ran bin/check_perms -f and things look good. I will show my > permissions just in case I am missing something. > drwxrwsr-x. 4 root mailman 33 Jun 28 14:45 archives > drwxrwsr-x. 2 root mailman 4096 Jun 29 09:31 bin drwxrwsr-x. 2 root > mailman 4096 Jun 29 09:30 cgi-bin Are all the files cgi-bin/* at least -rwxrws--- and group mailman? check_perms should complain if not, but ... > drwxrwsr-x. 2 root mailman 4096 Jun 29 09:30 cron drwxrwsr-x. 2 root > mailman 108 Jun 29 09:30 data drwxrwsr-x. 2 root mailman 4096 Jun 29 > 09:30 icons > drwxrwsr-x. 3 root mailman 20 Jun 28 16:28 lists > drwxrwsr-x. 2 root mailman 81 Jun 29 10:49 locks > drwxrwsr-x. 2 root mailman 43 Jun 28 16:32 logs > drwxrwsr-x. 2 root mailman 20 Jun 29 09:30 mail > drwxrwsr-x. 11 root mailman 4096 Jun 29 09:30 Mailman drwxrwsr-x. 40 > root mailman 4096 Jun 28 14:45 messages > drwxrwsr-x. 2 root mailman 6 Jun 28 14:45 pythonlib > drwxrwsr-x. 11 root mailman 4096 Jun 28 16:32 qfiles drwxrwsr-x. 2 > root mailman 4096 Jun 29 09:30 scripts > drwxrwsr-x. 2 root mailman 6 Jun 28 14:45 spam > drwxrwsr-x. 41 root mailman 4096 Jun 28 14:45 templates drwxrwsr-x. 4 > root mailman 4096 Jun 29 09:31 tests This could be a SELinux issue. If it's enabled, try disabling it. -- Mark Sapiro <[email protected]<mailto:[email protected]>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected]<mailto:[email protected]> https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/jewel.makda%40washburn.edu ------------------------------------------------------ Mailman-Users mailing list [email protected] https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
