Re: [Mailman-Users] invites for large user list fails
Mark Sapiro wrote: Anne Ramey wrote: admin(10796): [- Mailman Version: 2.1.9rc1 -] admin(10796): [- Traceback --] admin(10796): Traceback (most recent call last): admin(10796): File /usr/local/mailman/scripts/driver, line 101, in run_main admin(10796): main() admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 117, in main admin(10796): subscription_confirm(mlist, doc, cookie, cgidata) admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 350, in subscription_confirm admin(10796): userdesc = mlist.pend_confirm(cookie, expunge=False)[1] admin(10796): TypeError: unsubscriptable object snip The above traceback is not from the error in inviting. It is from an error that occurred in trying to accept (or possibly not accept) an invitation or some other subscription confirmation. It was generated by the confirm CGI, not the admin CGI. I don't have time to look at it in more detail for a couple of days, but I will. It could be due to some corruption in the list's pending database caused by the invite error. I've looked at the code in confirm.py, and what it does is get the information for the cookie from the pending database, determines it's a subscription confirmation, locks the list and gets the user description information from the pending database. In this case, it successfully retrieved the pending data the first time, but then when it went back with the list locked, the pending data for the cookie was not there. This could happen if the cookie were expired, and another process evicted the expired cookies between the first retrieval and the locking of the list, or if two confirmations (say by email and web) were occurring at the same time with this cookie. In any case, the error seems to be an unlikely coincidence. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] invites for large user list fails
Anne Ramey wrote: Thank you very much for the script. It didn't throw any errors that I could see...just a lot of entries that look like this: cookie: 796cc3d566c11147296cd748690a972a364a479c type: S data: UserDesc [EMAIL PROTECTED] () [amekando] [digest? no] [en] These are the invitations. You would know if it threw an exception becaus it would quit with a traceback. So, the pending.pck database is OK. I increased this time on my server # Timeout: The number of seconds before receives and sends time out. # Timeout 1000 from 300 to 1000 and managed to enter 1000 invites at once. It did the same thing with 2000. I think you were right about apache terminating the process. Is anyone else running lists that process large #s of invites at once? What should my apache limit be to be effective? Is this correct? I.e. it was taking 5 minutes before producing the error, and now it can do 1000 invitations in under about 17 minutes, but with 2000, it produces the error after about 17 minutes. Given the size of your pending database (thousands of outstanding invitations), I suppose it could take over 0.5 seconds to process an invitation (includes adding the info to the pending database and queueing the user notice in the virgin queue). As far as a 'reasonable' value for timeout is concerned, I, personally, would be unlikely to wait even 5 minutes for response to a button click from a web page. Is inviting thousands of users at a time to join this list a regular occurrence? One thing that might help is reducing the size of the qfiles/virgin/ directory. Even though it is normally empty, it's size on disk may be quite large. This makes adding new entries a slower process than necessary because the entire disk directory must be searched each time a new entry is added to be sure it doesn't already exist. To reduce the size, stop Mailman just to be sure nothing is lost, verify that qfiles/virgin/ is empty, remove it and recreate it with the same ownership and permissions and start Mailman. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] invites for large user list fails
Mark Sapiro wrote: Anne Ramey wrote: Is there a known problem with inviting relatively large groups of addresses at once, ex. 6K at a time? I usually just subscribe, so I haven't run into this before, but I have a list owner who gets an error when trying to subscribe a list of 6000 addresses, but I've been breaking it up to smaller groups (400) and they seem to work fine. But when I get up to 1000+ it fails. If we try to invite the whole list we get: Server error! The server encountered an internal error and was unable to complete your request. Error message: Premature end of script headers: admin If you think this is a server error, please contact the webmaster mailto:[EMAIL PROTECTED]. Error 500 on the screen and: admin(10796): [- Mailman Version: 2.1.9rc1 -] admin(10796): [- Traceback --] admin(10796): Traceback (most recent call last): admin(10796): File /usr/local/mailman/scripts/driver, line 101, in run_main admin(10796): main() admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 117, in main admin(10796): subscription_confirm(mlist, doc, cookie, cgidata) admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 350, in subscription_confirm admin(10796): userdesc = mlist.pend_confirm(cookie, expunge=False)[1] trimmed The above traceback is not from the error in inviting. It is from an error that occurred in trying to accept (or possibly not accept) an invitation or some other subscription confirmation. It was generated by the confirm CGI, not the admin CGI. I don't have time to look at it in more detail for a couple of days, but I will. It could be due to some corruption in the list's pending database caused by the invite error. It appears you are correct and there is no log for the error from the admin invite except the premature end of headers from apache (see below). This error didn't really tell me what was wrong, but I guess I'm just not reading it right. This was the only thing I could find that seemed to be an error: TypeError: unsubscriptable object Does this mean there was just one address on the list that freaked it out? f it is one email address, how do I tell which one? They all look OK to me when I scroll through. I think the 'invite large list' error is the CGI running into an Apache imposed CPU time limit and thus being killed and not given a chance to log any error. You may find more info in the apache error_log. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.018.htp which has to do with memory limits and MemoryError from Mailman/Python, but in this case, you would be looking for an RLimitCPU directive in your Apache config, not RLimitMEM. I see neither RLimitCPU nor RLimitMem in my apache config. The error in my apache log is pretty much just what shows on the screen: [Wed Sep 12 16:17:54 2007] [error] Premature end of script headers: admin, referer: http ://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:21:10 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/6aa1c93a87faa005a204269528bab4968eeda7f3 [Wed Sep 12 16:23:05 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/88534c254d1e0e5d4866814e7a4e3da15d75580a [Wed Sep 12 16:34:08 2007] [error] Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:37:54 2007] [error] Premature end of script headers: options, referer: ht tp://lists.domain.tld/mailman/options/listname [Wed Sep 12 16:38:28 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/0abdea7d85f4df17e7007b00f86f3901421292aa [Wed Sep 12 16:38:40 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/d1a76914852c2a8a920e1a6836adadb41e36d99e [Wed Sep 12 16:52:35 2007] [error] user 9944 not found: /NCMail/index.html [Wed Sep 12 17:34:16 2007] [error]Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add It looks like this list is having problems with both confirms and invites, but not every time. This appears to be the only list (out of several hundred) having this problem. But this is probably only one of a few that is sending out large quantities of invites. Anne -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy:
Re: [Mailman-Users] invites for large user list fails
Anne Ramey wrote: I see neither RLimitCPU nor RLimitMem in my apache config. The error in my apache log is pretty much just what shows on the screen: [Wed Sep 12 16:17:54 2007] [error] Premature end of script headers: admin, referer: http ://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:21:10 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/6aa1c93a87faa005a204269528bab4968eeda7f3 [Wed Sep 12 16:23:05 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/88534c254d1e0e5d4866814e7a4e3da15d75580a [Wed Sep 12 16:34:08 2007] [error] Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:37:54 2007] [error] Premature end of script headers: options, referer: ht tp://lists.domain.tld/mailman/options/listname [Wed Sep 12 16:38:28 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/0abdea7d85f4df17e7007b00f86f3901421292aa [Wed Sep 12 16:38:40 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/d1a76914852c2a8a920e1a6836adadb41e36d99e [Wed Sep 12 16:52:35 2007] [error] user 9944 not found: /NCMail/index.html [Wed Sep 12 17:34:16 2007] [error]Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add It looks like this list is having problems with both confirms and invites, but not every time. This appears to be the only list (out of several hundred) having this problem. But this is probably only one of a few that is sending out large quantities of invites. I suspect there may be a problem with the pending database for this list. Download http://veenet.value.net/~msapiro/scripts/list_pending (mirrored at http://fog.ccsf.edu/~msapiro/scripts/list_pending), save it in Mailman's bin/ directory and run it on the offending list and see what happens. It will probably throw the TypeError: unsubscriptable object exception. If so, there is at least one bad entry in the pending.pck file. In that case, I can provide a modified script which will delete the bad entries. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] invites for large user list fails
Mark Sapiro wrote: Anne Ramey wrote: I see neither RLimitCPU nor RLimitMem in my apache config. The error in my apache log is pretty much just what shows on the screen: [Wed Sep 12 16:17:54 2007] [error] Premature end of script headers: admin, referer: http ://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:21:10 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/6aa1c93a87faa005a204269528bab4968eeda7f3 [Wed Sep 12 16:23:05 2007] [error] Premature end of script headers: confirm, referer: h ttp://lists.domain.tld/mailman/confirm/listname/88534c254d1e0e5d4866814e7a4e3da15d75580a [Wed Sep 12 16:34:08 2007] [error] Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add [Wed Sep 12 16:37:54 2007] [error] Premature end of script headers: options, referer: ht tp://lists.domain.tld/mailman/options/listname [Wed Sep 12 16:38:28 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/0abdea7d85f4df17e7007b00f86f3901421292aa [Wed Sep 12 16:38:40 2007] [error] Premature end of script headers: confirm, referer: ht tp://lists.domain.tld/mailman/confirm/listname/d1a76914852c2a8a920e1a6836adadb41e36d99e [Wed Sep 12 16:52:35 2007] [error] user 9944 not found: /NCMail/index.html [Wed Sep 12 17:34:16 2007] [error]Premature end of script headers: admin, referer: htt p://lists.domain.tld/mailman/admin/listname/members/add It looks like this list is having problems with both confirms and invites, but not every time. This appears to be the only list (out of several hundred) having this problem. But this is probably only one of a few that is sending out large quantities of invites. I suspect there may be a problem with the pending database for this list. Download http://veenet.value.net/~msapiro/scripts/list_pending (mirrored at http://fog.ccsf.edu/~msapiro/scripts/list_pending), save it in Mailman's bin/ directory and run it on the offending list and see what happens. It will probably throw the TypeError: unsubscriptable object exception. If so, there is at least one bad entry in the pending.pck file. In that case, I can provide a modified script which will delete the bad entries. Thank you very much for the script. It didn't throw any errors that I could see...just a lot of entries that look like this: cookie: 796cc3d566c11147296cd748690a972a364a479c type: S data: UserDesc [EMAIL PROTECTED] () [amekando] [digest? no] [en] I increased this time on my server # Timeout: The number of seconds before receives and sends time out. # Timeout 1000 from 300 to 1000 and managed to enter 1000 invites at once. It did the same thing with 2000. I think you were right about apache terminating the process. Is anyone else running lists that process large #s of invites at once? What should my apache limit be to be effective? Thanks, Anne -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] invites for large user list fails
Anne Ramey sent the message below at 13:14 9/13/2007: I increased this time on my server # Timeout: The number of seconds before receives and sends time out. # Timeout 1000 from 300 to 1000 and managed to enter 1000 invites at once. It did the same thing with 2000. I think you were right about apache terminating the process. Is anyone else running lists that process large #s of invites at once? What should my apache limit be to be effective? End original message. - Why not just process it in batches? If a thousand works fine, then do a thousand at a time. Why is it so important to do it in one gulp? Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] invites for large user list fails
Is there a known problem with inviting relatively large groups of addresses at once, ex. 6K at a time? I usually just subscribe, so I haven't run into this before, but I have a list owner who gets an error when trying to subscribe a list of 6000 addresses, but I've been breaking it up to smaller groups (400) and they seem to work fine. But when I get up to 1000+ it fails. If we try to invite the whole list we get: Server error! The server encountered an internal error and was unable to complete your request. Error message: Premature end of script headers: admin If you think this is a server error, please contact the webmaster mailto:[EMAIL PROTECTED]. Error 500 on the screen and: admin(10796): [- Mailman Version: 2.1.9rc1 -] admin(10796): [- Traceback --] admin(10796): Traceback (most recent call last): admin(10796): File /usr/local/mailman/scripts/driver, line 101, in run_main admin(10796): main() admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 117, in main admin(10796): subscription_confirm(mlist, doc, cookie, cgidata) admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 350, in subscription_confirm admin(10796): userdesc = mlist.pend_confirm(cookie, expunge=False)[1] admin(10796): TypeError: unsubscriptable object admin(10796): [- Python Information -] admin(10796): sys.version = 2.3.4 (#1, Jan 9 2007, 16:40:18) [GCC 3.4.6 20060404 (Red Hat 3.4.6-3)] admin(10796): sys.executable = /usr/bin/python admin(10796): sys.prefix = /usr admin(10796): sys.exec_prefix = /usr admin(10796): sys.path= /usr admin(10796): sys.platform= linux2 admin(10796): [- Environment Variables -] admin(10796): HTTP_REFERER: http://lists.domain.tld/mailman/confirm/listname/88534c254d1e0e5d4866814e 7a4e3da15d75580a admin(10796): SERVER_SOFTWARE: Apache/2.0.52 (Red Hat) admin(10796): SCRIPT_NAME: /mailman/confirm admin(10796): SERVER_SIGNATURE: addressApache/2.0.52 (Red Hat) Server at lists.domain.tld Port 80/address admin(10796): admin(10796): REQUEST_METHOD: POST admin(10796): PATH_INFO: /dma.npi.listserv admin(10796): SERVER_PROTOCOL: HTTP/1.1 admin(10796): QUERY_STRING: admin(10796): CONTENT_LENGTH: 122 admin(10796): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; Inf oPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30) admin(10796): HTTP_CONNECTION: Keep-Alive admin(10796): SERVER_NAME: lists.domain.tld admin(10796): REMOTE_ADDR: 11.22.12.123 admin(10796): PATH_TRANSLATED: /var/www/content/listname admin(10796): SERVER_PORT: 80 admin(10796): SERVER_ADDR: 123.22.11.32 admin(10796): DOCUMENT_ROOT: /var/www/content admin(10796): PYTHONPATH: /usr/local/mailman admin(10796): SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/confirm admin(10796): SERVER_ADMIN: [EMAIL PROTECTED] admin(10796): HTTP_HOST: lists.domain.tld admin(10796): HTTP_CACHE_CONTROL: no-cache admin(10796): REQUEST_URI: /mailman/confirm/dma.npi.listserv admin(10796): HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash , application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/xaml+xml, applicatio n/vnd.ms-xpsdocument, application/x-ms-xbap, application/x-ms-application, */* admin(10796): GATEWAY_INTERFACE: CGI/1.1 admin(10796): REMOTE_PORT: 14506 admin(10796): HTTP_ACCEPT_LANGUAGE: en-us admin(10796): CONTENT_TYPE: application/x-www-form-urlencoded admin(10796): HTTP_ACCEPT_ENCODING: gzip, deflate This error didn't really tell me what was wrong, but I guess I'm just not reading it right. This was the only thing I could find that seemed to be an error: TypeError: unsubscriptable object Does this mean there was just one address on the list that freaked it out? f it is one email address, how do I tell which one? They all look OK to me when I scroll through. Help? Anne -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] invites for large user list fails
Anne Ramey wrote: Is there a known problem with inviting relatively large groups of addresses at once, ex. 6K at a time? I usually just subscribe, so I haven't run into this before, but I have a list owner who gets an error when trying to subscribe a list of 6000 addresses, but I've been breaking it up to smaller groups (400) and they seem to work fine. But when I get up to 1000+ it fails. If we try to invite the whole list we get: Server error! The server encountered an internal error and was unable to complete your request. Error message: Premature end of script headers: admin If you think this is a server error, please contact the webmaster mailto:[EMAIL PROTECTED]. Error 500 on the screen and: admin(10796): [- Mailman Version: 2.1.9rc1 -] admin(10796): [- Traceback --] admin(10796): Traceback (most recent call last): admin(10796): File /usr/local/mailman/scripts/driver, line 101, in run_main admin(10796): main() admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 117, in main admin(10796): subscription_confirm(mlist, doc, cookie, cgidata) admin(10796): File /usr/local/mailman/Mailman/Cgi/confirm.py, line 350, in subscription_confirm admin(10796): userdesc = mlist.pend_confirm(cookie, expunge=False)[1] admin(10796): TypeError: unsubscriptable object admin(10796): [- Python Information -] admin(10796): sys.version = 2.3.4 (#1, Jan 9 2007, 16:40:18) [GCC 3.4.6 20060404 (Red Hat 3.4.6-3)] admin(10796): sys.executable = /usr/bin/python admin(10796): sys.prefix = /usr admin(10796): sys.exec_prefix = /usr admin(10796): sys.path= /usr admin(10796): sys.platform= linux2 admin(10796): [- Environment Variables -] admin(10796): HTTP_REFERER: http://lists.domain.tld/mailman/confirm/listname/88534c254d1e0e5d4866814e 7a4e3da15d75580a admin(10796): SERVER_SOFTWARE: Apache/2.0.52 (Red Hat) admin(10796): SCRIPT_NAME: /mailman/confirm admin(10796): SERVER_SIGNATURE: addressApache/2.0.52 (Red Hat) Server at lists.domain.tld Port 80/address admin(10796): admin(10796): REQUEST_METHOD: POST admin(10796): PATH_INFO: /dma.npi.listserv admin(10796): SERVER_PROTOCOL: HTTP/1.1 admin(10796): QUERY_STRING: admin(10796): CONTENT_LENGTH: 122 admin(10796): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; Inf oPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30) admin(10796): HTTP_CONNECTION: Keep-Alive admin(10796): SERVER_NAME: lists.domain.tld admin(10796): REMOTE_ADDR: 11.22.12.123 admin(10796): PATH_TRANSLATED: /var/www/content/listname admin(10796): SERVER_PORT: 80 admin(10796): SERVER_ADDR: 123.22.11.32 admin(10796): DOCUMENT_ROOT: /var/www/content admin(10796): PYTHONPATH: /usr/local/mailman admin(10796): SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/confirm admin(10796): SERVER_ADMIN: [EMAIL PROTECTED] admin(10796): HTTP_HOST: lists.domain.tld admin(10796): HTTP_CACHE_CONTROL: no-cache admin(10796): REQUEST_URI: /mailman/confirm/dma.npi.listserv admin(10796): HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash , application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/xaml+xml, applicatio n/vnd.ms-xpsdocument, application/x-ms-xbap, application/x-ms-application, */* admin(10796): GATEWAY_INTERFACE: CGI/1.1 admin(10796): REMOTE_PORT: 14506 admin(10796): HTTP_ACCEPT_LANGUAGE: en-us admin(10796): CONTENT_TYPE: application/x-www-form-urlencoded admin(10796): HTTP_ACCEPT_ENCODING: gzip, deflate The above traceback is not from the error in inviting. It is from an error that occurred in trying to accept (or possibly not accept) an invitation or some other subscription confirmation. It was generated by the confirm CGI, not the admin CGI. I don't have time to look at it in more detail for a couple of days, but I will. It could be due to some corruption in the list's pending database caused by the invite error. This error didn't really tell me what was wrong, but I guess I'm just not reading it right. This was the only thing I could find that seemed to be an error: TypeError: unsubscriptable object Does this mean there was just one address on the list that freaked it out? f it is one email address, how do I tell which one? They all look OK to me when I scroll through. I think the 'invite large list' error is the CGI running into an Apache imposed CPU time limit and thus being killed and not given a chance to log any error. You may find more info in the apache error_log. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.018.htp which has to do with memory limits and MemoryError from Mailman/Python, but in this case, you would be looking for an RLimitCPU directive in your Apache config, not RLimitMEM. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, California
