Re: [Mailman-Users] bug adding user, and archiving gets shunted
On Thu, 31 Mar 2011, Mark Sapiro wrote: This error is due to one of several known incompatibilities between Mailman versions older than 2.1.12 and Python 2.6 or later. See the FAQ at http://wiki.list.org/x/pYA9. I read the FAQ, which was however last updated in 2009. This MIGHT not be a problem, because I'm running tests (as a sort of power user) on my machine (suse 11.3 installed last december), but this is NOT the target system. I'm pretty sure the target system will have suse 11.4 which came out recently. suse 11.3 bundles mailman 2.1.11-13.2 and python 2.6.5-2.11 (however they provide separately mailman 2.1.14-21.1 and python 2.7-43.1) suse 11.4 bundles mailman 2.1.14-4.7.1 and python 2.7-8.2 (and provides also 2.7-43.1) I am really confused by all these minor subsubversions. Is the suse 11.4 mm/python coupling sound ? If so I will tell our sysadm to proceed, and pass on my test experience. I might do a few further tests on my machine and occasionally report problems here (be free to reply usual 2.1.11/2.6 incompatibility). Eventually I could upgrade mailman on my test machine (but not python) if that is likely to work (just to test also the upgrade procedure). If suse is packaging Mailman 2.1.11 with the Python 2.6.5 that you are apparently using, this is a serious suse packaging problem. I could report a bug, however if their 11.4 packaging is sound, they are likely to consider it irrelevant. -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] bug adding user, and archiving gets shunted
Lucio Chiappetti wrote: On Thu, 31 Mar 2011, Mark Sapiro wrote: This error is due to one of several known incompatibilities between Mailman versions older than 2.1.12 and Python 2.6 or later. See the FAQ at http://wiki.list.org/x/pYA9. I read the FAQ, which was however last updated in 2009. Yes, but the key part in this case is Update - March 2009: Mailman 2.1.12 has been released and requires Python 2.4.x or later. It is the *first* Mailman release compatible with Python 2.6. (emphasis mine). This MIGHT not be a problem, because I'm running tests (as a sort of power user) on my machine (suse 11.3 installed last december), but this is NOT the target system. I'm pretty sure the target system will have suse 11.4 which came out recently. suse 11.3 bundles mailman 2.1.11-13.2 and python 2.6.5-2.11 (however they provide separately mailman 2.1.14-21.1 and python 2.7-43.1) suse 11.4 bundles mailman 2.1.14-4.7.1 and python 2.7-8.2 (and provides also 2.7-43.1) I am really confused by all these minor subsubversions. Everything to the right of the hyphen (-) is a designation by the packager of build, patch level, whatever. Only suse can tell you what it means. I strongly suggest that for a fair test, you upgrade the Mailman on your test platform to the 2.1.14 package. The suse 11.3 bundle has the compatibility issues you have already seen and others as well. Is the suse 11.4 mm/python coupling sound ? It should be, but I don't think the combination of Mailman 2.1.14 and Python 2.7.x has seen much use, so there may be as yet undiscovered issues. If so I will tell our sysadm to proceed, and pass on my test experience. I might do a few further tests on my machine and occasionally report problems here (be free to reply usual 2.1.11/2.6 incompatibility). Eventually I could upgrade mailman on my test machine (but not python) if that is likely to work (just to test also the upgrade procedure). I would recommend that. If suse is packaging Mailman 2.1.11 with the Python 2.6.5 that you are apparently using, this is a serious suse packaging problem. I could report a bug, however if their 11.4 packaging is sound, they are likely to consider it irrelevant. I suggest you report it anyway, if for no other reason than to document the issue with suse. -- Mark Sapiro m...@msapiro.netThe 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://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] bug adding user, and archiving gets shunted
On Wed, 30 Mar 2011, Mark Sapiro wrote: Lucio Chiappetti wrote: - when subscribing an user (myself) to [any] list via the web interface I get the message on the screen Bug in Mailman version 2.1.11 We're sorry, we hit a bug! 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 find this information in the Mailman error logs. I confirm that despite the fact this message is shown on the web page, I receive the regular confirmation message, and if I click on the provided URL I am regularly subscribed. The logs show nothing strange except /var/lib/mailman/logs/error I cleared all logs and qfiles before restarting mailman, and did a single subscribe test on a new list (creation goes ok). I attach the error log (I hope an attachment is ok for the list policy) The error is generated at the same time the confirmation request is sent. -- Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html Mar 31 18:25:40 2011 admin(23714): admin(23714): [- Mailman Version: 2.1.11 -] admin(23714): [- Traceback --] admin(23714): Traceback (most recent call last): admin(23714): File /usr/lib/mailman/scripts/driver, line 101, in run_main admin(23714): main() admin(23714): File /usr/lib/mailman/Mailman/Cgi/subscribe.py, line 96, in main admin(23714): process_form(mlist, doc, cgidata, language) admin(23714): File /usr/lib/mailman/Mailman/Cgi/subscribe.py, line 176, in process_form admin(23714): mlist.AddMember(userdesc, remote) admin(23714): File /usr/lib/mailman/Mailman/MailList.py, line 916, in AddMember admin(23714): raise Errors.MMSubscribeNeedsConfirmation admin(23714): TypeError: exceptions must be old-style classes or derived from BaseException, not str admin(23714): [- Python Information -] admin(23714): sys.version = 2.6.5 (r265:79063, Jul 5 2010, 11:46:13) [GCC 4.5.0 20100604 [gcc-4_5-branch revision 160292]] admin(23714): sys.executable = /usr/bin/python admin(23714): sys.prefix = /usr admin(23714): sys.exec_prefix = /usr admin(23714): sys.path= /usr admin(23714): sys.platform= linux2 admin(23714): [- Environment Variables -] admin(23714): HTTP_COOKIE: prova+admin=280200695ac7914d73280030393831343564643362396466653434626237313463323738353632353733373339666139663662; provalist+admin=28020069dc49934d7328006135656264616138396438386330396233353361393430376264346334353931333839336332; mailman+admin=28020069684d934d73280062393365343830383463303965306238623666353732343637643131393962396432306561613135; newprova+user+lucio--at--lambrate.inaf.it=28020069b063934d7328003363623437316130336235303038643264386231636364653535303832333239343331656438; SESSIONID=To1011mC44031660979444665At admin(23714): SERVER_SOFTWARE: Apache/2.2.15 (Linux/SUSE) admin(23714): SCRIPT_NAME: /mailman/subscribe admin(23714): SERVER_SIGNATURE: addressApache/2.2.15 (Linux/SUSE) Server at sax.iasf-milano.inaf.it Port 80/address admin(23714): admin(23714): REQUEST_METHOD: POST admin(23714): HTTP_KEEP_ALIVE: 115 admin(23714): SERVER_PROTOCOL: HTTP/1.1 admin(23714): QUERY_STRING: admin(23714): CONTENT_LENGTH: 133 admin(23714): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(23714): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 admin(23714): HTTP_CONNECTION: keep-alive admin(23714): HTTP_REFERER: http://sax.iasf-milano.inaf.it/mailman/listinfo/altraprova admin(23714): SERVER_NAME: sax.iasf-milano.inaf.it admin(23714): REMOTE_ADDR: 155.253.16.87 admin(23714): PATH_TRANSLATED: /poseidon/WWW/Primary/htdocs/altraprova admin(23714): SERVER_PORT: 80 admin(23714): SERVER_ADDR: 155.253.16.87 admin(23714): DOCUMENT_ROOT: /poseidon/WWW/Primary/htdocs/ admin(23714): PYTHONPATH: /usr/lib/mailman admin(23714): SCRIPT_FILENAME: /usr/lib/mailman/cgi-bin/subscribe admin(23714): SERVER_ADMIN: nos...@lambrate.inaf.it admin(23714): SCRIPT_URI: http://sax.iasf-milano.inaf.it/mailman/subscribe/altraprova admin(23714): HTTP_HOST: sax.iasf-milano.inaf.it admin(23714): SCRIPT_URL: /mailman/subscribe/altraprova admin(23714): REQUEST_URI: /mailman/subscribe/altraprova admin(23714): HTTP_ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 admin(23714): GATEWAY_INTERFACE: CGI/1.1 admin(23714): REMOTE_PORT: 48993 admin(23714): HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5 admin(23714): CONTENT_TYPE: application/x-www-form-urlencoded admin(23714):
Re: [Mailman-Users] bug adding user, and archiving gets shunted
Lucio Chiappetti wrote: I confirm that despite the fact this message is shown on the web page, I receive the regular confirmation message, and if I click on the provided URL I am regularly subscribed. This error is due to one of several known incompatibilities between Mailman versions older than 2.1.12 and Python 2.6 or later. See the FAQ at http://wiki.list.org/x/pYA9. If suse is packaging Mailman 2.1.11 with the Python 2.6.5 that you are apparently using, this is a serious suse packaging problem. If you have upgraded your Python independent of suse, perhaps you can also install Mailman 2.1.14-1 or even the head of the Bazaar lp:mailman/2.1 branch. As you have observed, this particular error only results in the bug page rather than the appropriate subscription results page, but other errors due to this incompatibility will be more disruptive. -- Mark Sapiro m...@msapiro.netThe 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://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] bug adding user, and archiving gets shunted
On Wed, 30 Mar 2011, Lucio Chiappetti wrote in thread starting at http://mail.python.org/pipermail/mailman-users/2011-March/071332.html and ran bin/withlist -l -a -r fix_url I still have some problems when subscribing a new user, and concerning message archiving. I will post a separate request for clarity. After I fixed the problems described in the thread quoted above, I had the following problems. - when subscribing an user (myself) to the mailman list via the web interface I get the message on the screen Bug in Mailman version 2.1.11 We're sorry, we hit a bug! 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 find this information in the Mailman error logs. after a while *root* (not me as mailman-owner !!) receives a message to visit the list control page to accept the subscription request, but such page has no pending requests - when subscribing an user (myself) to any other list via the web interface I get the same bug message, but after a while I receive the confirmation message, and if I confirm the welcome message, and are subscribed - I removed ALL lists, because mailman was created with newlist before I ran fix_url. When I recreate it with newlist, also mailman behaves as any other list i.e. - bug message on the screen - nevertheless confirmation e-mail - and regular welcome if I confirm what stuff in /var/lib/mailman/logs/error is relevant ? The other question is that if I send a message to a list, the member receive it, but the message is NOT archived. I see that a file appears in qfiles/shunt/ Note that I did not install any crontab (since my machine is just a test arrangement). Are crontabs necessary for the archiver ? Is there any FAQ or doc which describes what is in logs and qfiles, and how to interpret and dispose of it ? In particular how do I get rid of all old stuff there (other than doing it manually), so that I'll have only errors after a fresh restart ? What material from logs/error or qfiles/shunt should be posted to this list for diagnostics (if any) ? -- Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy) L'Italia ripudia la guerra [...] Italy repudiates war [...] come mezzo di risoluzione delle as a way of resolution of controversie internazionali international controversies [Art. 11 Constitution of the Italian Republic] For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] bug adding user, and archiving gets shunted
Lucio Chiappetti wrote: On Wed, 30 Mar 2011, Lucio Chiappetti wrote in thread starting at http://mail.python.org/pipermail/mailman-users/2011-March/071332.html and ran bin/withlist -l -a -r fix_url I still have some problems when subscribing a new user, and concerning message archiving. I will post a separate request for clarity. After I fixed the problems described in the thread quoted above, I had the following problems. - when subscribing an user (myself) to the mailman list via the web interface I get the message on the screen Bug in Mailman version 2.1.11 We're sorry, we hit a bug! 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 find this information in the Mailman error logs. after a while *root* (not me as mailman-owner !!) receives a message to visit the list control page to accept the subscription request, but such page has no pending requests - when subscribing an user (myself) to any other list via the web interface I get the same bug message, but after a while I receive the confirmation message, and if I confirm the welcome message, and are subscribed - I removed ALL lists, because mailman was created with newlist before I ran fix_url. When I recreate it with newlist, also mailman behaves as any other list i.e. - bug message on the screen - nevertheless confirmation e-mail - and regular welcome if I confirm what stuff in /var/lib/mailman/logs/error is relevant ? Potentially all of it from one such error, but most problems can be diagnosed with just the python traceback from the error. In some cases, the web server information is helpful for errors in CGIs. The other question is that if I send a message to a list, the member receive it, but the message is NOT archived. I see that a file appears in qfiles/shunt/ Here again, there will be an error and a python traceback associated with the shunted message. Archiving issues are often permission problems. Have you run Mailman's bin/check_perms? In any case, the traceback is needed to say more. Note that I did not install any crontab (since my machine is just a test arrangement). Are crontabs necessary for the archiver ? No. None of the cron jobs are required for Mailman's basic operation. There should be a crontab.in file in Mailman's cron/ directory that has more detail as to what the individual crons do. Is there any FAQ or doc which describes what is in logs and qfiles, and how to interpret and dispose of it ? There's probably some, but not collected in one place :( See the mmdsr script in the contrib/ directory for a daily log analysis program. In particular how do I get rid of all old stuff there (other than doing it manually), so that I'll have only errors after a fresh restart ? There should be no old stuff other than logs which are normally handled by logrotate. On my test/development system, I have a shell script to copy /dev/null to all the logs, but you can simply rm them as they will be automatically created when written. There is a cron job called cull_bad_shunt if your MM is recent enough. See the documentation for BAD_SHUNT_* settings in Defaults.py. What material from logs/error or qfiles/shunt should be posted to this list for diagnostics (if any) ? Most likely nothing from qfiles/shunt. These are the messages that couldn't be completely processed due to some exception. After the underlying issue is fixed, you can finish processing the message by running bin/unshunt. If you run bin/unshunt before fixing the underlying issue, the message will be shunted again. To view the files use bin/show_qfiles or bin/dumpdb. show_qfiles displays only the message and accepts multiple file arguments. dumpdb only accepts a single file, but also dumps the metadata associated with the queue entry. For logs/error, for a shunted message, post the python exception and the entire traceback. For a CGI error, it's safest to post everything with the timestamp of the error, but if there is sensitive information in the web server or python configuration sections, it is OK to mung it as long as the munging is obvious. You don't have to post more than one traceback if they are the same. -- Mark Sapiro m...@msapiro.netThe 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://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
