Dear MM developers, we had activated mailman 2.1.4 this morning, and things (at least e-mail) seemed to work fine.
Only later we found that with the web interface we get a big problems, for administrative things, both user subscription or adminstrator login.
Our setup: Mail server is on Solaris 8; Web server (apache) on Linux Redhat 9. This had worked fine with Mailman 2.1.3. to which we had to revert ASAP.
We got the following in a browser window. Do you have any ideas what could have gone wrong?
Regards, Martin Maechler <maechler@stat.math.ethz.ch> http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <><
Bug in Mailman version 2.1.4
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 (most recent call last): File "/sfs/s/solaris/8/app/mailman-sfs/2.1.4/scripts/driver", line 87, in run_main main() File "/sfs/s/solaris/8/app/mailman-sfs/2.1.4/Mailman/Cgi/admindb.py", line 176, in main mlist.Save() File "/sfs/s/solaris/8/app/mailman-sfs/2.1.4/Mailman/MailList.py", line 526, in Save self.__save(dict) File "/sfs/s/solaris/8/app/mailman-sfs/2.1.4/Mailman/MailList.py", line 485, in __save if mm_cfg.SYNC_AFTER_WRITE: AttributeError: 'module' object has no attribute 'SYNC_AFTER_WRITE'
Python information:
Variable Value sys.version 2.3 (#1, Oct 16 2003, 05:04:34) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] sys.executable /scratch/local/bin/python sys.prefix /scratch/local/app/python/current sys.exec_prefix /scratch/local/app/python/current sys.path /scratch/local/app/python/current sys.platform linux2
Environment variables:
Variable Value SSL_VERSION_INTERFACE mod_ssl/2.0.40 SSL_SERVER_I_DN_OU Department of Mathematics SSL_CIPHER_EXPORT false SSL_SERVER_S_DN_Email webmaster@math.ethz.ch SERVER_SOFTWARE Apache/2.0.40 (Red Hat Linux) SCRIPT_NAME /mailman/admindb SSL_SERVER_A_KEY rsaEncryption SSL_SERVER_S_DN_ST Switzerland SERVER_SIGNATURE Apache/2.0.40 Server at www.stat.math.ethz.ch Port 443 REQUEST_METHOD GET HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 SSL_SERVER_S_DN /C=CH/ST=Switzerland/L=Zurich/O=ETH Zurich/OU=Seminar for Statistics/CN=www.stat.math.ethz.ch/emailAddress=webmaster@math.ethz.ch HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 SSL_CIPHER DHE-RSA-AES256-SHA SSL_SERVER_V_START Feb 7 16:20:08 2003 GMT SSL_SESSION_ID B3A4068B5FE1BF5724E1A013A8D807BEA289E9C2707F87655F146278FF232E04 SSL_CLIENT_VERIFY NONE SSL_SERVER_I_DN_ST Switzerland HTTP_CONNECTION keep-alive HTTP_COOKIE bioconductor+admin=2802000000695287f93f732800000035346463373631326663616634306662353561373066346663323939393332316662336230396362 SERVER_NAME www.stat.math.ethz.ch REMOTE_ADDR 155.52.45.201 SSL_CIPHER_ALGKEYSIZE 256 SSL_SERVER_I_DN /C=CH/ST=Switzerland/L=Zurich/O=ETH Zurich/OU=Department of Mathematics/CN=ISG D-MATH/emailAddress=webmaster@math.ethz.ch SSL_SERVER_I_DN_C CH SSL_SERVER_M_VERSION 1 SSL_SERVER_I_DN_O ETH Zurich SSL_SERVER_M_SERIAL 07 SERVER_ADDR 129.132.148.136 DOCUMENT_ROOT /var/www/vhosts/sfs/htdocs SSL_SERVER_S_DN_OU Seminar for Statistics SERVER_PORT 443 SSL_SERVER_I_DN_Email webmaster@math.ethz.ch SSL_VERSION_LIBRARY OpenSSL/0.9.7a PYTHONPATH /sfs/s/solaris/8/app/mailman-sfs/2.1.4 SCRIPT_FILENAME /var/www/vhosts/sfs/mailman/admindb SERVER_ADMIN webmaster@math.ethz.ch SSL_SERVER_S_DN_O ETH Zurich SSL_SERVER_A_SIG md5WithRSAEncryption SSL_SERVER_S_DN_L Zurich HTTP_HOST www.stat.math.ethz.ch SCRIPT_URL /mailman/admindb/bioconductor HTTPS on SSL_SERVER_I_DN_L Zurich PATH_TRANSLATED /var/www/vhosts/sfs/htdocs/bioconductor HTTP_CACHE_CONTROL max-age=0 SSL_SERVER_S_DN_C CH REQUEST_URI /mailman/admindb/bioconductor HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 SCRIPT_URI https://www.stat.math.ethz.ch/mailman/admindb/bioconductor SSL_SERVER_S_DN_CN www.stat.math.ethz.ch HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314 GATEWAY_INTERFACE CGI/1.1 SSL_PROTOCOL TLSv1 REMOTE_PORT 44320 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 SSL_SERVER_V_END Feb 4 16:20:08 2013 GMT SSL_SERVER_I_DN_CN ISG D-MATH QUERY_STRING SSL_CIPHER_USEKEYSIZE 256 HTTP_ACCEPT_ENCODING gzip,deflate,compress;q=0.9 UNIQUE_ID kvDr3oGElIIAAE4-T6UAAAAZ PATH_INFO /bioconductor
On Tuesday, Jan 6, 2004, at 12:09 US/Eastern, Martin Maechler wrote:
Dear MM developers, we had activated mailman 2.1.4 this morning, and things (at least e-mail) seemed to work fine.
Only later we found that with the web interface we get a big problems, for administrative things, both user subscription or adminstrator login.
For what it's worth, I upgraded a single-server installation yesterday and did not have this problem. It's probably something unusual in your setup.
if mm_cfg.SYNC_AFTER_WRITE:AttributeError: 'module' object has no attribute 'SYNC_AFTER_WRITE'
Your new Mailman/Defaults.py (and Defaults.pyc) should contain a SYNC_AFTER_WRITE setting (the default is No, which you'd override in mm_cfg.py). If you had previously write-protected Defaults.py or Defaults.pyc, or somehow overwrote the new one with an old one, then the attribute would be missing because the file wasn't updated. Otherwise it's not obvious how that would occur, maybe your mm_cfg.py fails to import everything from Defaults?
--Robby
On Tue, 2004-01-06 at 12:43, Robby Griffin wrote:
Only later we found that with the web interface we get a big problems, for administrative things, both user subscription or adminstrator login.
For what it's worth, I upgraded a single-server installation yesterday and did not have this problem. It's probably something unusual in your setup.
Neither did I, although there was one report of a problem with authentication that is fixed in CVS and which I think only affects sites under very uncommon situations. I need more detail about these "big problems" before I'll know whether this is related.
if mm_cfg.SYNC_AFTER_WRITE:AttributeError: 'module' object has no attribute 'SYNC_AFTER_WRITE'
Your new Mailman/Defaults.py (and Defaults.pyc) should contain a SYNC_AFTER_WRITE setting (the default is No, which you'd override in mm_cfg.py). If you had previously write-protected Defaults.py or Defaults.pyc, or somehow overwrote the new one with an old one, then the attribute would be missing because the file wasn't updated. Otherwise it's not obvious how that would occur, maybe your mm_cfg.py fails to import everything from Defaults?
I'm pretty sure the release notes said that you MUST re-run configure before installing. Defaults.py gets generated from Defaults.py.in by the configure script, so if you don't re-run configure, you won't get the new defaults such as SYNC_AFTER_WRITE.
-Barry
"Barry" == Barry Warsaw <barry@python.org> on Tue, 06 Jan 2004 13:43:55 -0500 writes:
Barry> On Tue, 2004-01-06 at 12:43, Robby Griffin wrote:
>> > Only later we found that with the web interface we get
>> a big > problems, for administrative things, both user
>> subscription or > adminstrator login.
>>
>> For what it's worth, I upgraded a single-server
>> installation yesterday and did not have this
>> problem. It's probably something unusual in your setup.
Barry> Neither did I, although there was one report of a
Barry> problem with authentication that is fixed in CVS and
Barry> which I think only affects sites under very uncommon
Barry> situations. I need more detail about these "big
Barry> problems" before I'll know whether this is related.
>> > if mm_cfg.SYNC_AFTER_WRITE:
>> > AttributeError: 'module' object has no attribute 'SYNC_AFTER_WRITE'
>> Your new Mailman/Defaults.py (and Defaults.pyc) should
>> contain a SYNC_AFTER_WRITE setting (the default is No,
>> which you'd override in mm_cfg.py). If you had previously
>> write-protected Defaults.py or Defaults.pyc, or somehow
>> overwrote the new one with an old one, then the attribute
>> would be missing because the file wasn't updated.
>> Otherwise it's not obvious how that would occur, maybe
>> your mm_cfg.py fails to import everything from Defaults?
Barry> I'm pretty sure the release notes said that you MUST
Barry> re-run configure before installing. Defaults.py gets
Barry> generated from Defaults.py.in by the configure
Barry> script, so if you don't re-run configure, you won't
Barry> get the new defaults such as SYNC_AFTER_WRITE.We did rerun it in one place (mail server), but forgot in the other place (web server).
Thanks a lot for your help, and for mailman in general (and do apologize for having disturbed you!)
BTW: It seems 2.1.4 did catch much more bounce messages than 2.1.3: In about 10 hours, I didn't have one of the "Uncaught bounce notification" messages that I usually get about one per hour!
Thanks a lot!
Martin Maechler <maechler@stat.math.ethz.ch> http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <><
participants (3)
-
Barry Warsaw -
Martin Maechler -
Robby Griffin