[Mailman-Users] unsubscribe please
Dan Neary
dneary at auctionwatch.com
Sun Nov 12 19:03:56 CET 2000
-----Original Message-----
From: mailman-users-request at python.org
[mailto:mailman-users-request at python.org]
Sent: Sunday, November 12, 2000 9:02 AM
To: mailman-users at python.org
Subject: Mailman-Users digest, Vol 1 #864 - 6 msgs
Send Mailman-Users mailing list submissions to
mailman-users at python.org
To subscribe or unsubscribe via the World Wide Web, visit
http://www.python.org/mailman/listinfo/mailman-users
or, via email, send a message with subject or body 'help' to
mailman-users-request at python.org
You can reach the person managing the list at
mailman-users-admin at python.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Mailman-Users digest..."
Today's Topics:
1. Help: AttributeError: web_page_url (John A. Martin)
2. Upgrade to 2.0rc2 destroyed some archives (Greg Connor)
3. Resolved: Upgrade to 2.0rc2 destroyed some archives (Greg Connor)
4. 2.0rc2 upgrade FAILS if lists have pending requests (Greg Connor)
5. Archive headers (John Camp)
6. Re: [Mailman-Developers] Announcing Mailman 2.0 release candidate 2
(Phil Barnett)
--__--__--
Message: 1
To: Mailman-Users at python.org
Date: Sat, 11 Nov 2000 14:56:06 -0500
From: "John A. Martin" <jam at jamux.com>
Subject: [Mailman-Users] Help: AttributeError: web_page_url
After upgrading apache from the Red Hat 6.2 apache-1.3.12-2.i386.rpm
to apache-1.3.14-2.6.2.i386.rpm it seems to be impossible to access
the Mailman web interface. Other stuff on the web site is OK. I do
not believe apache's /etc/httpd/conf/httpd.conf was changed with
respect to the entries pertaining to Mailman. No joy reverting back
to the apache-1.3.12-2 package. Several tracebacks are logged leading
back to 'AttributeError: web_page_url'. This Mailman has been in
production for about a year. The Mailman web interface is now down
and I don't have a clue.
-------------- cut here ---->8 ---< head
Bug in Mailman version 1.1
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy of
this page to the webmaster
for this site with a description of what happened. Thanks!
Traceback:
Traceback (innermost last):
File "/home/mailman/scripts/driver", line 112, in run_main
main()
File "/home/mailman/Mailman/Cgi/listinfo.py", line 40, in main
FormatListinfoOverview()
File "/home/mailman/Mailman/Cgi/listinfo.py", line 88, in
FormatListinfoOverview
l = MailList.MailList(n, lock = 0)
File "/home/mailman/Mailman/MailList.py", line 62, in __init__
self.Load()
File "/home/mailman/Mailman/MailList.py", line 824, in Load
self.CheckValues()
File "/home/mailman/Mailman/MailList.py", line 853, in CheckValues
if self.web_page_url and self.web_page_url[-1] != '/':
AttributeError: web_page_url
Environment variables:
Variable
Value
DOCUMENT_ROOT
/home
SERVER_ADDR
216.0.124.17
HTTP_ACCEPT_ENCODING
gzip
SERVER_PORT
80
GATEWAY_INTERFACE
CGI/1.1
HTTP_ACCEPT_LANGUAGE
en
REMOTE_ADDR
216.0.124.17
SERVER_NAME
lists.essential.org
HTTP_CONNECTION
Keep-Alive
HTTP_USER_AGENT
Mozilla/4.75 [en] (X11; U; Linux 2.2.14-12
i586; Nav)
HTTP_ACCEPT_CHARSET
iso-8859-1,*,utf-8
HTTP_ACCEPT
image/gif, image/x-xbitmap, image/jpeg,
image/pjpeg,
image/png, */*
REQUEST_URI
/mailman/listinfo
PATH
/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin
QUERY_STRING
SCRIPT_FILENAME
/home/mailman/cgi-bin/listinfo
HTTP_HOST
lists.essential.org
REQUEST_METHOD
GET
SERVER_SIGNATURE
Apache/1.3.14 Server at lists.essential.org
Port 80
SCRIPT_NAME
/mailman/listinfo
SERVER_ADMIN
root at localhost
SERVER_SOFTWARE
Apache/1.3.14 (Unix) (Red-Hat/Linux)
mod_perl/1.23
PYTHONPATH
/home/mailman
SERVER_PROTOCOL
HTTP/1.0
REMOTE_PORT
2936
---- 8<------- cut here ----------> tail
-------------- cut here ---->8 ---< head
Bug in Mailman version 1.1
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy
of this page to the webmaster for this site with a description of what
happened. Thanks!
Traceback:
Traceback (innermost last):
File "/home/mailman/scripts/driver", line 112, in run_main
main()
File "/home/mailman/Mailman/Cgi/listinfo.py", line 40, in main
FormatListinfoOverview()
File "/home/mailman/Mailman/Cgi/listinfo.py", line 88, in
FormatListinfoOverview
l = MailList.MailList(n, lock = 0)
File "/home/mailman/Mailman/MailList.py", line 62, in __init__
self.Load()
File "/home/mailman/Mailman/MailList.py", line 824, in Load
self.CheckValues()
File "/home/mailman/Mailman/MailList.py", line 853, in CheckValues
if self.web_page_url and self.web_page_url[-1] != '/':
AttributeError: web_page_url
Environment variables:
Variable
Value
DOCUMENT_ROOT
/home/listproc/httpd/html
SERVER_ADDR
216.0.124.17
HTTP_ACCEPT_ENCODING
gzip
SERVER_PORT
80
REMOTE_ADDR
216.0.124.17
SERVER_SOFTWARE
Apache/1.3.12 (Unix) (Red Hat/Linux)
mod_perl/1.23
GATEWAY_INTERFACE
CGI/1.1
HTTP_ACCEPT_LANGUAGE
en
REMOTE_PORT
1464
SERVER_NAME
lists.essential.org
HTTP_CONNECTION
Keep-Alive
HTTP_USER_AGENT
Mozilla/4.75 [en] (X11; U; Linux 2.2.14-12
i586; Nav)
HTTP_ACCEPT_CHARSET
iso-8859-1,*,utf-8
HTTP_ACCEPT
image/gif, image/x-xbitmap, image/jpeg,
image/pjpeg,
image/png, */*
REQUEST_URI
/mailman/listinfo
PATH
/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin
QUERY_STRING
SERVER_PROTOCOL
HTTP/1.0
HTTP_HOST
lists.essential.org
REQUEST_METHOD
GET
SERVER_SIGNATURE
Apache/1.3.12 Server at lists.essential.org
Port 80
SCRIPT_NAME
/mailman/listinfo
SERVER_ADMIN
root at localhost
SCRIPT_FILENAME
/home/mailman/cgi-bin/listinfo
PYTHONPATH
/home/mailman
HTTP_REFERER
http://lists.essential.org/
HTTP_PRAGMA
no-cache
---- 8<------- cut here ----------> tail
jam
--__--__--
Message: 2
Date: Sat, 11 Nov 2000 21:55:49 -0800
From: Greg Connor <gconnor at nekodojo.org>
To: mailman-users at python.org
Subject: [Mailman-Users] Upgrade to 2.0rc2 destroyed some archives
After upgrading, some of my archives are now "corrupt" according to
qrunner, and looks like additional messages are not being archived.
This is the message from the error log that suggests archiving is not
working.
Nov 11 17:18:34 2000 qrunner(5155): Traceback (innermost last):
Nov 11 17:18:34 2000 qrunner(5155): File
"/home/mailman/Mailman/Archiver/Archiver.py", line 221, i
n ArchiveMail
Nov 11 17:18:34 2000 qrunner(5155): h.processUnixMailbox(f,
HyperArch.Article)
Nov 11 17:18:34 2000 qrunner(5155): File
"/home/mailman/Mailman/Archiver/pipermail.py", line 521,
in processUnixMailbox
Nov 11 17:18:34 2000 qrunner(5155): a = articleClass(m,
self.sequence)
Nov 11 17:18:34 2000 qrunner(5155): File
"/home/mailman/Mailman/Archiver/HyperArch.py", line 224,
in __init__
Nov 11 17:18:34 2000 qrunner(5155): self.cenc = string.lower(cenc)
Nov 11 17:18:34 2000 qrunner(5155): TypeError: read-only character
buffer, None
Nov 11 17:18:34 2000 (5155) CORRUPT ARCHIVE FOR LIST: poly-listowners
I have tried to rebuild the archives, but I get a similar error (see
below).
Unfortunately, due to stupidity on my part, I deleted all the .mbox
files and directories, thinking "What are these doing here, I thought I
turned off 'mbox' archiving a long time ago". I didn't realize at the
time, but "update" probably re-created these (since they aren't in my
backup).
Anyway, I tried to regenerate the mbox files by doing
gunzip *.txt.gz
cat *.txt > ../listname.mbox/listname.mbox
and then moving the directory and re-running bin/arch. When I do that,
it thinks about it for a while, and then I get this error. bin/arch
creates a directory but there are no files inside.
Traceback (innermost last):
File "/home/mailman/bin/arch", line 129, in ?
main()
File "/home/mailman/bin/arch", line 118, in main
archiver.processUnixMailbox(fp, Article)
File "/home/mailman/Mailman/Archiver/pipermail.py", line 521, in
processUnixMailbox
a = articleClass(m, self.sequence)
File "/home/mailman/Mailman/Archiver/HyperArch.py", line 224, in
__init__
self.cenc = string.lower(cenc)
TypeError: read-only character buffer, None
I am still working on trying to get my archives back, but I wanted to
put the word out in case this is a new issue. I searched the entire
archive and I couldn't find any reference to self.cenc or
string.lower(cenc). I have also tried padding each .txt file with one
newline (even tried two) and the results are the same.
If you happen to know how I can make the archives usable again, or how
to rebuild the archives, help would be appreciated. My only thing left
to try is to restore mailman from backup and try the upgrade again, but
the rest of the upgrade was quite painful...
Thanks
gregc
--
Greg Connor <gconnor at nekodojo.org>
--__--__--
Message: 3
Date: Sun, 12 Nov 2000 00:21:28 -0800
From: Greg Connor <gconnor at nekodojo.org>
To: mailman-users at python.org
Subject: [Mailman-Users] Resolved: Upgrade to 2.0rc2 destroyed some archives
Greg Connor wrote:
>
> After upgrading, some of my archives are now "corrupt" according to
> qrunner, and looks like additional messages are not being archived.
> This is the message from the error log that suggests archiving is not
> working.
OK, it looks like my initial analysis was not quite correct... the
"CORRUPT" message seems to have been spurious and archives were actually
working. Details follow...
I restored my mailmail 1.1 directory from backup and performed the
upgrade to 2.0rc2 again. This time, I got the same message suggesting
the archive was corrupted:
> Nov 11 23:23:10 2000 qrunner(10590): OSError: [Errno 2] No such file or
directory:
'/home/mailman/archives/private/poly-listowners.mbox/poly-listowners.mbox'
> Nov 11 23:23:10 2000 (10590) CORRUPT ARCHIVE FOR LIST: poly-listowners
But, it looks like the message was archived properly anyway. According
to my mm_cfg.py setting "ARCHIVE_TO_MBOX = 0", the message was NOT
supposed to be added to the mbox file, but HyperArch.py still throws an
error that says "No such file or directory" for the mbox file.
This implies that the mbox file must exist, even if you don't plan to
add to it, but in my case, the only side effect is a spurious error
message (and the message is still archived to the hypermail archive
directory.) I created the mbox file and confirmed that ARCHIVE_TO_MBOX
= 0 is still obeyed - nothing is added to the mbox file
I decided to change back to ARCHIVE_TO_MBOX = 2, so I would get mbox
files growing again, and this works too. It now seems like the only
impact was the spurious message if we don't have mbox files and don't
intend to use them.
Regarding the previous error:
> Nov 11 17:18:34 2000 qrunner(5155): File
"/home/mailman/Mailman/Archiver/HyperArch.py", line 224, in __init__
> Nov 11 17:18:34 2000 qrunner(5155): self.cenc = string.lower(cenc)
> Nov 11 17:18:34 2000 qrunner(5155): TypeError: read-only character buffer,
None
I tried the operation again with a proper "mbox" file, and the behavior
was correct. I don't know what was wrong with the mbox file I made by
sticking the .txt files all together. I now don't need to regenerate
the mbox files... the above error was only encountered in my attempt to
fix the first error message. I would still like to know how to create
the mbox file again from the contents of the pipermail directory, but
since archives are working correctly there is not so much need for
this. I would only need to regenerate the mbox file if I want to delete
some messages from the archive or something (or to have a second copy in
case pipermail gets corrupted.)
If anyone is interested in the details of what I did, I'm posting a log
of the second upgrade operation:
http://www.nekodojo.org/~gconnor/Mailman_20rc2_update_log.txt
--
Greg Connor <gconnor at nekodojo.org>
--__--__--
Message: 4
Date: Sun, 12 Nov 2000 00:35:44 -0800
From: Greg Connor <gconnor at nekodojo.org>
To: mailman-users at python.org
Subject: [Mailman-Users] 2.0rc2 upgrade FAILS if lists have pending requests
Error:
"make update" and "make install" fail when there are pending requests.
I got this message while updating from Mailman 1.1 to 2.0rc2
% make install
...
Updating mailing list: poly-houston
- updating old private mbox file
looks like you have a really recent CVS installation...
you're either one brave soul, or you already ran me
- updating old public mbox file
Updating mailing list: poly-under30
Traceback (innermost last):
File "bin/update", line 350, in ?
errors = main()
File "bin/update", line 281, in main
errors = errors + dolist(listname)
File "bin/update", line 79, in dolist
mlist = MailList.MailList(listname, lock=0)
File "/home/mailman/Mailman/MailList.py", line 79, in __init__
self.Load()
File "/home/mailman/Mailman/MailList.py", line 906, in Load
self.CheckVersion(dict)
File "/home/mailman/Mailman/MailList.py", line 917, in CheckVersion
Update(self, stored_state)
File "/home/mailman/Mailman/versions.py", line 54, in Update
NewRequestsDatabase(l)
File "/home/mailman/Mailman/versions.py", line 247, in
NewRequestsDatabase
l.HoldMessage(msg, reason)
File "/home/mailman/Mailman/ListAdmin.py", line 145, in HoldMessage
self.__opendb()
File "/home/mailman/Mailman/ListAdmin.py", line 66, in __opendb
assert self.Locked() and self.__filename
AssertionError
At this point, make install has failed while running update, and I have
tried
running check_perms, and fixing some errors, but running update again
gives the
same error.
My workaround:
I turned apache back on and I used the mailman/admindb form to respond
to all the pending requests. (I tried this because the traceback says
"NewRequestsDatabase" so this made me think it could not convert
existing pending requests. Also, other lists went through "Updating"
ok, and they didn't have pending requests.)
After clearing the requests, make update got a bit further (to the next
lists with pending requests) I cleared that one too, and the update was
able to complete on the third try.
I'm discarding the requests, but I think one could approve at this point
too. Most everything is installed, but since sendmail isn't running,
the message would probably just queue up for qrunner...
If anyone is interested in the details of what I did, I'm posting a log
of the second upgrade operation:
http://www.nekodojo.org/~gconnor/Mailman_20rc2_update_log.txt
Suggested fix:
If possible, make it so that upgrading doesn't die if requests are
pending. However, if the requests can't be converted, Mailman's install
should deal with this gracefully and tell the user what needs to be
done. If this can't be resolved, I suggest a note in the release notes
telling peole that they have to clean out the administrative requests db
for ALL lists before doing the upgrade. This is awkward because often
the person approving the message is not the same person who is
installing Mailman 2.
--
Greg Connor <gconnor at nekodojo.org>
--__--__--
Message: 5
Date: Sun, 12 Nov 2000 14:57:48 +0000
To: mailman-users at python.org
From: John Camp <camp at bigfoot.com>
Subject: [Mailman-Users] Archive headers
Why should some archived messages be shown as having been sent by the
list-address? This has started since rc1.
John Camp
--__--__--
Message: 6
From: "Phil Barnett" <midnight at the-oasis.net>
To: mailman-developers-admin at python.org, mailman-users at python.org
Date: Sun, 12 Nov 2000 10:03:15 -0500
Reply-To: midnight at the-oasis.net
Subject: [Mailman-Users] Re: [Mailman-Developers] Announcing Mailman 2.0
release candidate 2
On 10 Nov 2000, at 23:24, Barry A. Warsaw wrote:
> Please let me know if you find any errors in the docs. Unless
> something's royally screwed, those are the only changes I'll make
> before 2.0 final. Plan for that one week from today: Friday November
> 17th.
I hope you'll also accepts bugs found in the program. ;-)
(I posted this last night, but didn't see it in the list, so I'm posting it
again)
I upgraded from 2.0b6 from 2.0rc2 Friday night. A person wrote me
and said the replyto: is no longer pointed to the list. I checked
several messages and they were, but some were not. Any
message I send to the list has a replyto of myself instead of to the
list.
Here is a mail message from before and one right after the change.
Notice that on the first one the replyto is set to the list and the
second one it's set to myself. I checked the list checkbox and it's
still set to replyto the list.
-------------Before--------------
Return-Path: <harbourtalk-
admin at lists.harbour-project.org>
Delivered-To: the-oasis-net-
midnight at the-oasis.net
Received: (qmail 11516 invoked from
network); 11 Nov 2000 05:41:04 -0000
Received: from ns.dios.net (HELO
taz2.fiberhosting.com)
(mailman at 127.0.0.1)
by ns.dios.net with SMTP; 11 Nov
2000 05:41:04 -0000
Return-Path: <midnight at the-oasis.net>
Delivered-To: mailman-
harbourtalk at lists.harbour-project.org
Received: (qmail 11475 invoked from
network); 11 Nov 2000 05:40:06 -0000
Received: from max1-
221.mtld.fl.iag.net (HELO odo)
(207.30.74.221)
by taz.fiberhosting.com with SMTP;
11 Nov 2000 05:40:06 -0000
From: "Phil Barnett" <midnight at the-
oasis.net>
To: harbourtalk at lists.harbour-
project.org
MIME-Version: 1.0
Content-type: text/plain; charset=US-
ASCII
Content-transfer-encoding: 7BIT
Message-ID:
<3A0C9560.428.22A641 at localhost>
Priority: normal
X-mailer: Pegasus Mail for Win32
(v3.12c)
Subject: [HarbourTalk] Mailman Upgrade.
Sender: harbourtalk-
admin at lists.harbour-project.org
Errors-To: harbourtalk-
admin at lists.harbour-project.org
X-BeenThere: harbourtalk at lists.harbour-
project.org
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: harbourtalk at lists.harbour-
project.org
List-Help: <mailto:harbourtalk-
request at lists.harbour-
project.org?subject=help>
List-Post:
<mailto:harbourtalk at lists.harbour-
project.org>
List-Subscribe:
<http://www.matrixlist.com/mailman/list
info/harbourtalk>, <mailto:harbourtalk-
request at lists.harbour-
project.org?subject=subscribe>
List-Id: General Talk about the
Harbour Project
<harbourtalk.lists.harbour-project.org>
List-Unsubscribe:
<http://www.matrixlist.com/mailman/list
info/harbourtalk>, <mailto:harbourtalk-
request at lists.harbour-
project.org?subject=unsubscribe>
List-Archive:
http://www.matrixlist.com/pipermail/har
bourtalk/
Date: Sat, 11 Nov 2000 00:40:00 -0500
I am going to perform a Mailman
upgrade to 2.0rc2.
I'm configuring it and make-ing it
tonight. There may be a slight
delay for some messages. I'll be
sending test messages during
this test to Harbour Talk when I get
it back up, and a notice here
when the upgrade is done. If you see
anything funny after that
notice, please report it to me
immediately. I'll do what I can even
up
to reverting to the prior version if
necessary. Hopefully, it will
upgrade nicely.
--
Phil Barnett
mailto:midnight at the-oasis.net
WWW
http://www.the-oasis.net/
FTP Site
ftp://ftp.the-oasis.net
_______________________________________
________
HarbourTalk mailing list
HarbourTalk at lists.harbour-project.org
http://www.matrixlist.com/mailman/listi
nfo/harbourtalk
-------------After----------------
Return-Path: <harbourtalk-admin at lists.harbour-project.org>
Delivered-To: the-oasis-net-midnight at the-oasis.net
Received: (qmail 13034 invoked from network); 11 Nov 2000
05:51:04 -0000
Received: from ns.dios.net (HELO taz2.fiberhosting.com)
(mailman at 127.0.0.1)
by ns.dios.net with SMTP; 11 Nov 2000 05:51:04 -0000
Return-Path: <midnight at the-oasis.net>
Delivered-To: mailman-harbourtalk at lists.harbour-project.org
Received: (qmail 13012 invoked from network); 11 Nov 2000
05:50:50 -0000
Received: from max1-221.mtld.fl.iag.net (HELO odo)
(207.30.74.221)
by taz.fiberhosting.com with SMTP; 11 Nov 2000 05:50:50 -0000
From: "Phil Barnett" <midnight at the-oasis.net>
To: harbourtalk at lists.harbour-project.org
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: [HarbourTalk] Mailman Upgrade.
Reply-to: midnight at the-oasis.net
Message-ID: <3A0C97E5.1835.2C7BDB at localhost>
Priority: normal
In-reply-to: <3A0C9560.428.22A641 at localhost>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Sender: harbourtalk-admin at lists.harbour-project.org
Errors-To: harbourtalk-admin at lists.harbour-project.org
X-BeenThere: harbourtalk at lists.harbour-project.org
X-Mailman-Version: 2.0rc2
Precedence: bulk
List-Help: <mailto:harbourtalk-request at lists.harbour-
project.org?subject=help>
List-Post: <mailto:harbourtalk at lists.harbour-project.org>
List-Subscribe:
<http://www.matrixlist.com/mailman/listinfo/harbourtalk>,
<mailto:harbourtalk-request at lists.harbour-
project.org?subject=subscribe>
List-Id: General Talk about the Harbour Project
<harbourtalk.lists.harbour-project.org>
List-Unsubscribe:
<http://www.matrixlist.com/mailman/listinfo/harbourtalk>,
<mailto:harbourtalk-request at lists.harbour-
project.org?subject=unsubscribe>
List-Archive: <http://www.matrixlist.com/pipermail/harbourtalk/>
Date: Sat, 11 Nov 2000 00:50:45 -0500
Ok, this is a test on Mailman 2.0rc2.
--
Phil Barnett mailto:midnight at the-oasis.net
WWW http://www.the-oasis.net/
FTP Site ftp://ftp.the-oasis.net
_______________________________________________
HarbourTalk mailing list
HarbourTalk at lists.harbour-project.org
http://www.matrixlist.com/mailman/listinfo/harbourtalk
--
Phil Barnett mailto:midnight at the-oasis.net
WWW http://www.the-oasis.net/
FTP Site ftp://ftp.the-oasis.net
--__--__--
------------------------------------------------------
Mailman-Users maillist - Mailman-Users at python.org
http://www.python.org/mailman/listinfo/mailman-users
End of Mailman-Users Digest
More information about the Mailman-Users
mailing list