diff options
| -rw-r--r-- | admin/www/faq.html | 167 | ||||
| -rw-r--r-- | admin/www/index.html | 10 |
2 files changed, 174 insertions, 3 deletions
diff --git a/admin/www/faq.html b/admin/www/faq.html new file mode 100644 index 000000000..691271909 --- /dev/null +++ b/admin/www/faq.html @@ -0,0 +1,167 @@ +<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> +<html> + <head> + <title>Mailman FAQ</title> + </head> + + <body bgcolor="f6f6f6"> + <table cols=1 border=0 celspacing=4 cellpadding=5> + <tr> + <td width=100% bgcolor="#99cff"> + <center><font size=+2><strong>The Mailman Frequently Asked + Questions</strong></font></center> + </td> + </tr> + <tr> + <td width=100% bgcolor="fff0d0"> + <font size=+1><strong> + 1. If from the web you get "document contains no data", or + if mail isn't getting delivered, or + if you see "Premature end of script headers", or + if you see "Mailman CGI error!!!" + </strong></font> + </td></tr> + <tr><td> + The most likely cause of this is that the GID that is compiled + into the C wrappers does not match the GID that your Web server + invokes CGI scripts with. Note that a similar error could occur + if your mail system invokes filter programs under a GID that + does not match the one compiled into the C mail wrapper. + + <p>To fix this you will need to re-configure Mailman using the + <tt>--with-cgi-gid</tt> and <tt>--with-mail-gid</tt> options. + See <tt>INSTALL</tt> for details. + + These errors are logged to syslog and they do not show up in the + Mailman log files. Problems with the CGI wrapper do get + reported in the Web browser though, and include the expected + GID, so that should help a lot. + + You may want to have syslog running and configured to log the + mail.error log class somewhere; on Solaris systems, the line + + <blockquote><pre> + mail.debug /var/log/syslog + </pre></blockquote> + + causes the messages to go to them in <tt>/var/log/syslog</tt>, for + example. (The distributed syslog.conf forwards the message to + the loghost, when present. See the syslog man page for more + details.) + + If your system is set like this, and you get a failure trying to + visit the mailman/listinfo web page, and it's due to a UID or + GID mismatch, then you should get an entry at the end of + <tt>/var/log/syslog</tt> identifying the expected and received values. + </td></tr> + + <tr><td width=100% bgcolor="fff0d0"> + <font size=+1><strong> + 2. If the web pages hang... + </strong></font> + </td></tr> + <tr><td>CERN Web servers might leave Python processes running, and in + some cases might hang the CGI completely. In that case, switch + to Apache. + </td></tr> + + <tr><td width=100% bgcolor="fff0d0"> + <font size=+1><strong> + 3. Check ~mailman/logs/error periodically... + </strong></font> + </td></tr> + <tr><td> + Many of the scripts have their stderr logged to + <tt>~mailman/logs/error</tt>, and some of the modules write caught errors + there, as well, so you should check there at least occasionally + to look for bugs in the code and problems in your setup. + + <p>One thing that is <em>not</em> caught by stderr hook is syntax errors, + but any of these should have been caught in the installation + phase, which byte-compiles all .py files in the distribution. + There may be syntax errors lurking if you hacked the code, or in + the scripts that are not modules. + + <p>You can always use the Python module <tt>compile</tt> or + <tt>compileall</tt> + to force byte compilation of a file, or just fire up the Python + interpreter and try importing the module! + </td></tr> + + <tr><td width=100% bgcolor="fff0d0"> + <font size=+1><strong> + 4. Other debugging aids + </strong></font> + </td></tr> + <tr><td> + If you get exceptions in the log and/or Web pages, and these are + complaining that files could not be opened, you might like to + see which files Mailman is trying to open! + + <p>In Python 1.5.2, this will be a standard part of the exception + message. In Python 1.5.1 the best you can do is to comment out + the code in <tt>$prefix/scripts/driver</tt> where it is redefining the + built-in <tt>open()</tt> function. This simulates what Python 1.5.2 will + do when it raises an <tt>IOError</tt> exception, however this only works + for <tt>open()</tt>. While this is the most common case, Python 1.5.2 + will handle many other cases where files are unsuccessfully + referenced. + </td></tr> + + <tr><td width=100% bgcolor="fff0d0"> + <font size=+1><strong> + 5. Why doesn't the archive link work? + </strong></font> + </td></tr> + <tr><td> + Have any messages been posted to the list? This is a known + buglet; the archive link doesn't work until at least one message + has been posted. + </td></tr> + + <tr><td width=100% bgcolor="fff0d0"> + <font size=+1><strong> + 6. Okay, the archive link works, but I can't access the public + archives. + </strong></font> + </td></tr> + <tr><td> + If you are using Apache, you must make sure that <tt>FollowSymLinks</tt> + is enabled for the path to the public archives. Note that the + actual archives always reside in the private tree, and only when + archives are public, is the symlink followed. See this archive + message for more details: + + <p><a href="http://www.python.org/pipermail/mailman-users/1998-November/000173.html"> + http://www.python.org/pipermail/mailman-users/1998-November/000173.html + </a></td></tr> + + <tr><td width=100% bgcolor="fff0d0"> + <font size=+1><strong> + 7. Still having problems? Running on Linux? + </strong></font> + </td></tr> + <tr><td> + See the file <tt>README.LINUX</tt> in the distribution. + </td></tr> + + <tr><td width=100% bgcolor="fff0d0"> + <font size=+1><strong> + 8. I want to get rid of some messages in my archive. How do I do + this? + </strong></font> + </td></tr> + <tr><td> + David Rocher posts the following recipe: + + <pre><blockquote> + . remove $prefix/archives/private/<listname> + . edit $prefix/archives/private/<listname>.mbox/<listname>.mbox [optional] + . run $prefix/bin/arch <listname> + $prefix/archives/private/<listname>.mbox/<listname>.mbox + </blockquote></pre> + </td></tr> + + </table> + </body> +</html> diff --git a/admin/www/index.html b/admin/www/index.html index b15fd2a88..07e88fa0c 100644 --- a/admin/www/index.html +++ b/admin/www/index.html @@ -63,11 +63,15 @@ released <!-DATE--->Jan 14 1999<!-DATE--->) </td></tr> <tr> <td> -We'll be working on a FAQ in the near future. Until then, just post -questions to the +The <a href="faq.html">Frequently Asked Questions (FAQ)</a> is +available to answer most questions. For issues not covered in the +FAQ, please post your questions to the <a href="http://www.python.org/mailman/listinfo/mailman-users"> Mailman-Users</a> -mailing list. +mailing list. You might also want to check out the +<a href="http://www.python.org/pipermail/mailman-users/"> +Mailman Users mailing list archive</a> to see if your problem has +already been addressed. </td> </tr> <tr> |