[Mailman-Users] new install: mailman archive not working

[Jeremy Olmen]

I am having a hard time going to
http://lilpup.mymachine.com/mailman/archives, whenever I do it generates:


We're sorry, we hit a Bug in Mailman version 2.0.6

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
bugfind this information in the Mailman error logs.


I have freshly installed mailman 2.0.6 on a FreeBSD 4.4-RC and a 4.3-STABLE
machine, making sure I followed the INSTALL file to the letter, and I can't
seem to get to that page. I always get a traceback logged in my error log
file, which reads:

Sep 03 18:13:28 2001 admin(2099):
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
admin(2099): [----- Mailman Version: 2.0.6 -----]
admin(2099): [----- Traceback ------]
admin(2099): Traceback (most recent call last):
admin(2099):   File "/home/mailman/scripts/driver", line 91, in run_main
admin(2099):     module = getattr(pkg, scriptname)
admin(2099): AttributeError: archives
admin(2099): [----- Python Information -----]
admin(2099): sys.version    = 2.0 (#2, Aug 31 2001, 19:01:55)
[GCC 2.95.3 20010315 (release) [FreeBSD]]
admin(2099): sys.executable = /usr/local/bin/python
admin(2099): sys.prefix     = /usr/local
admin(2099): sys.exec_prefix= /usr/local
admin(2099): sys.path       = /usr/local
admin(2099): sys.platform   = freebsd4
admin(2099): [----- Environment Variables -----]
admin(2099):    DOCUMENT_ROOT: /usr/local/www/data
admin(2099):    SERVER_ADDR: 10.1.1.162
admin(2099):    HTTP_ACCEPT_ENCODING: gzip, deflate
admin(2099):    SERVER_PORT: 80
admin(2099):    REMOTE_ADDR: 10.1.1.161
admin(2099):    UNIQUE_ID: O5QAiAoBAaIAAAEdCB8
admin(2099):    HTTP_ACCEPT_LANGUAGE: en-us
admin(2099):    GATEWAY_INTERFACE: CGI/1.1
admin(2099):    SERVER_NAME: lilpup.fargel.com
admin(2099):    HTTP_CONNECTION: Keep-Alive
admin(2099):    HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 5.01; Windows
NT 5.0)
admin(2099):    HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg,
image/pjpeg, application/vnd.ms-powerpoint, application/v
nd.ms-excel, application/msword, */*
admin(2099):    REQUEST_URI: /mailman/archives
admin(2099):    QUERY_STRING:
admin(2099):    SCRIPT_FILENAME: /usr/home/mailman/cgi-bin/archives
admin(2099):    HTTP_HOST: lilpup.fargel.com
admin(2099):    REQUEST_METHOD: GET
admin(2099):    SERVER_SIGNATURE: <ADDRESS>Apache/1.3.19 Server at
lilpup.fargel.com Port 80</ADDRESS>

admin(2099):    SCRIPT_NAME: /mailman/archives
admin(2099):    SERVER_ADMIN: lilpuppie at mindspring.com
admin(2099):    SERVER_SOFTWARE: Apache/1.3.19 (Unix)
admin(2099):    PYTHONPATH: /home/mailman
admin(2099):    HTTP_COOKIE: test:admin
admin(2099):    SERVER_PROTOCOL: HTTP/1.1
admin(2099):    REMOTE_PORT: 1271


I have posted some articles to a test list, and it seems that everything is
being created correctly in /home/mailman/archives/public/. Everything else
about this server that I've tested so far works wonderfully.

I have searched the web for this problem, and I have found that there are a
number of active mailman servers with this same error. Is this an Apache
mis-configuration? I have seen this same problem from people using versions
of mailman going all the way back to 2.0beta1, so I am inclined to think it
is a server-config problem, not a bug within mailman but i really do not
know. Any and all help with this problem is greatly appreciated.


Thank you,

Jeremy Olmen
lilpuppie at mindspring.com