Re: [Mailman-Users] New apache is causing my mailman to fail...
Still having troubles... I thought I'd start somewhat from scratch this time. Since mailman is failing with python errors that reference ssl, I've cleared out the ssl directory so that the ssl dir had nothing from a prior version in it. I rebuilt ssl (openssl-0.9.6g), and then, I rebuilt python 2.2.2, so that python, when being built, will only see the fresh openssl. Afterwords, I bring up mailman/listinfo via our web server, and once again received the error in the browser about a bug in Mailman 2.08 The logs from mailman this time indicate something different from last time. If you recall, last time, I was receiving: admin(3540): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 Clearly, ssl looked involved. But, this go around led to different errors, not related to ssl (as far as I can see.) admin(3771): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/lib/python2.2/lib-dynload/_socket.so: bad ELF flags value: 256 Can anyone help out with this? The full error listing is below. Thanks! Steve admin(3771): [- Mailman Version: 2.0.8 -] admin(3771): [- Traceback --] admin(3771): Traceback (most recent call last): admin(3771): File /home/mailman/scripts/driver, line 80, in run_main admin(3771): import Mailman.pythonlib.cgi admin(3771): File ../Mailman/pythonlib/cgi.py, line 31, in ? admin(3771): import urllib admin(3771): File /usr/local/lib/python2.2/urllib.py, line 26, in ? admin(3771): import socket admin(3771): File /usr/local/lib/python2.2/socket.py, line 41, in ? admin(3771): from _socket import * admin(3771): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/lib/python2.2/lib-dynload/_socket.so: bad ELF flags value: 256 admin(3771): [- Python Information -] admin(3771): sys.version= 2.2.2 (#1, Nov 25 2002, 15:28:57) [GCC 2.95.2 19991024 (release)] admin(3771): sys.executable = /usr/local/bin/python admin(3771): sys.prefix = /usr/local admin(3771): sys.exec_prefix= /usr/local admin(3771): sys.path = /usr/local admin(3771): sys.platform = sunos5 admin(3771): [- Environment Variables -] admin(3771):PYTHONPATH: /home/mailman admin(3771):SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(3771):SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(3771):SERVER_ADMIN: [EMAIL PROTECTED] admin(3771):SCRIPT_NAME: /mailman/listinfo admin(3771):SCRIPT_URI: http://www.cs.jhu.edu/mailman/listinfo admin(3771):SERVER_SIGNATURE: ADDRESSApache/1.3.27 Server at www.cs.jhu.edu Port 80/ADDRESS admin(3771):REQUEST_METHOD: GET admin(3771):HTTP_HOST: www.cs.jhu.edu admin(3771):SCRIPT_URL: /mailman/listinfo admin(3771):SERVER_PROTOCOL: HTTP/1.1 admin(3771):QUERY_STRING: admin(3771):HTTP_CONNECTION: keep-alive admin(3771):HTTP_CACHE_CONTROL: max-age=0 admin(3771):REQUEST_URI: /mailman/listinfo admin(3771):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,text/css,*/*;q=0.1 admin(3771):HTTP_ACCEPT_CHARSET: ISO-8859-1, utf-8;q=0.66, *;q=0.66 admin(3771):HTTP_USER_AGENT: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020829 admin(3771):TZ: US/Eastern admin(3771):SERVER_NAME: www.cs.jhu.edu admin(3771):REMOTE_ADDR: 128.220.13.39 admin(3771):REMOTE_PORT: 42200 admin(3771):HTTP_ACCEPT_LANGUAGE: en-us, en;q=0.50 admin(3771):SERVER_PORT: 80 admin(3771):GATEWAY_INTERFACE: CGI/1.1 admin(3771):DOCUMENT_ROOT: /users/httpd/htdocs admin(3771):HTTP_ACCEPT_ENCODING: gzip, deflate, compress;q=0.9 admin(3771):SERVER_ADDR: 128.220.13.101 admin(3771):HTTP_KEEP_ALIVE: 300 -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] New apache is causing my mailman to fail...
Hi All! I'm currently running Mailman version 2.0.8. Until last week, our Apache webserver (1.3.14) interfaced with our Mailman just fine. Last week, we needed to upgrade our Apache Web server to 1.3.27. We also had to upgrade our openssl to the latest version (version OpenSSL 0.9.6g 9 Aug 2002) We're also running Python version 2.2.2. Since then, we've been getting the following error attempting to access mailman lists from our website: = Bug in Mailman version 2.0.8 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 even tried reinstalling Python to make sure it saw the updated OPENSSL stuff. Anyway, from the web, when we do a mailman/listinfo and get the above error, the mailman error log reports: Nov 21 11:03:35 2002 admin(18834): admin(18834): [- Mailman Version: 2.0.8 -] admin(18834): [- Traceback --] admin(18834): Traceback (most recent call last): admin(18834): File /home/mailman/scripts/driver, line 80, in run_main admin(18834): import Mailman.pythonlib.cgi admin(18834): File ../Mailman/pythonlib/cgi.py, line 31, in ? admin(18834): import urllib admin(18834): File /usr/local/lib/python2.2/urllib.py, line 26, in ? admin(18834): import socket admin(18834): File /usr/local/lib/python2.2/socket.py, line 41, in ? admin(18834): from _socket import * admin(18834): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 admin(18834): [- Python Information -] admin(18834): sys.version= 2.2.2 (#1, Nov 20 2002, 18:28:42) [GCC 2.95.2 19991024 (release)] admin(18834): sys.executable = /usr/local/bin/python admin(18834): sys.prefix = /usr/local admin(18834): sys.exec_prefix= /usr/local admin(18834): sys.path = /usr/local admin(18834): sys.platform = sunos5 admin(18834): [- Environment Variables -] admin(18834): HTTP_PRAGMA: no-cache admin(18834): PYTHONPATH: /home/mailman admin(18834): SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(18834): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(18834): SERVER_ADMIN: [EMAIL PROTECTED] admin(18834): SCRIPT_NAME: /mailman/listinfo admin(18834): SCRIPT_URI: http://www.cs.jhu.edu/mailman/listinfo admin(18834): SERVER_SIGNATURE: ADDRESSApache/1.3.27 Server at www.cs.jhu.edu Port 80/ADDRESS Note the Import error above. So... again, it worked until we installed the new Apache and new openssl. Then, it stopped working giving the above errors. Rebuilding python did not help. Any ideas of what I can try? Is there really a bug in our version of Mailman? And should I be reinstalling Mailman? or is there an easier fix? Thanks a bunch in advance, and if you could seperately CC: me on your post to the mailman list, that would be much appreciated. Thanks! Steve [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] New apache is causing my mailman to fail...
From this line in the traceback, /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 I looks like you have a problem with your new install of openssl. How did you install it? A package? and what OS are you using. You might reinstall openssl from source if possible. I'm not entirely sure what the 'bad ELF flags value' means but it sounds like you're using a precompiled openssl library on a system that doesn't support it. Use the source, Luke ==Tom== -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Rifkin Sent: Thursday, November 21, 2002 1:04 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [Mailman-Users] New apache is causing my mailman to fail... Hi All! I'm currently running Mailman version 2.0.8. Until last week, our Apache webserver (1.3.14) interfaced with our Mailman just fine. Last week, we needed to upgrade our Apache Web server to 1.3.27. We also had to upgrade our openssl to the latest version (version OpenSSL 0.9.6g 9 Aug 2002) We're also running Python version 2.2.2. Since then, we've been getting the following error attempting to access mailman lists from our website: = Bug in Mailman version 2.0.8 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 even tried reinstalling Python to make sure it saw the updated OPENSSL stuff. Anyway, from the web, when we do a mailman/listinfo and get the above error, the mailman error log reports: Nov 21 11:03:35 2002 admin(18834): admin(18834): [- Mailman Version: 2.0.8 -] admin(18834): [- Traceback --] admin(18834): Traceback (most recent call last): admin(18834): File /home/mailman/scripts/driver, line 80, in run_main admin(18834): import Mailman.pythonlib.cgi admin(18834): File ../Mailman/pythonlib/cgi.py, line 31, in ? admin(18834): import urllib admin(18834): File /usr/local/lib/python2.2/urllib.py, line 26, in ? admin(18834): import socket admin(18834): File /usr/local/lib/python2.2/socket.py, line 41, in ? admin(18834): from _socket import * admin(18834): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 admin(18834): [- Python Information -] admin(18834): sys.version= 2.2.2 (#1, Nov 20 2002, 18:28:42) [GCC 2.95.2 19991024 (release)] admin(18834): sys.executable = /usr/local/bin/python admin(18834): sys.prefix = /usr/local admin(18834): sys.exec_prefix= /usr/local admin(18834): sys.path = /usr/local admin(18834): sys.platform = sunos5 admin(18834): [- Environment Variables -] admin(18834): HTTP_PRAGMA: no-cache admin(18834): PYTHONPATH: /home/mailman admin(18834): SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(18834): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(18834): SERVER_ADMIN: [EMAIL PROTECTED] admin(18834): SCRIPT_NAME: /mailman/listinfo admin(18834): SCRIPT_URI: http://www.cs.jhu.edu/mailman/listinfo admin(18834): SERVER_SIGNATURE: ADDRESSApache/1.3.27 Server at www.cs.jhu.edu Port 80/ADDRESS Note the Import error above. So... again, it worked until we installed the new Apache and new openssl. Then, it stopped working giving the above errors. Rebuilding python did not help. Any ideas of what I can try? Is there really a bug in our version of Mailman? And should I be reinstalling Mailman? or is there an easier fix? Thanks a bunch in advance, and if you could seperately CC: me on your post to the mailman list, that would be much appreciated. Thanks! Steve [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/tomoakes%40usa.net -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] New apache is causing my mailman to fail...
Hi Tom! Sorry, left out the server info... Installing on Solaris 2.6 using the: * 2170570 Aug 9 13:54:01 2002 openssl-0.9.6g.tar.gz [LATEST] * from openssl.org. For openssl source, I ncompressed and did (as INSTALL suggested): $ ./config $ make $ make test $ make install Nothing failed along the way. If I reinstalled openssl again (although, since there were no failures when I first installed it, I wouldn't expect there to be now), would I need to reinstall python, since python likes to configure itself with ssl, if ssl exists? Steve From: Thomas Oakes [EMAIL PROTECTED] To: Steve Rifkin [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: [Mailman-Users] New apache is causing my mailman to fail... Date: Thu, 21 Nov 2002 13:55:47 -0500 From this line in the traceback, /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 I looks like you have a problem with your new install of openssl. How did you install it? A package? and what OS are you using. You might reinstall openssl from source if possible. I'm not entirely sure what the 'bad ELF flags value' means but it sounds like you're using a precompiled openssl library on a system that doesn't support it. Use the source, Luke ==Tom== -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Rifkin Sent: Thursday, November 21, 2002 1:04 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [Mailman-Users] New apache is causing my mailman to fail... Hi All! I'm currently running Mailman version 2.0.8. Until last week, our Apache webserver (1.3.14) interfaced with our Mailman just fine. Last week, we needed to upgrade our Apache Web server to 1.3.27. We also had to upgrade our openssl to the latest version (version OpenSSL 0.9.6g 9 Aug 2002) We're also running Python version 2.2.2. Since then, we've been getting the following error attempting to access mailman lists from our website: = Bug in Mailman version 2.0.8 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 even tried reinstalling Python to make sure it saw the updated OPENSSL stuff. Anyway, from the web, when we do a mailman/listinfo and get the above error, the mailman error log reports: Nov 21 11:03:35 2002 admin(18834): admin(18834): [- Mailman Version: 2.0.8 -] admin(18834): [- Traceback --] admin(18834): Traceback (most recent call last): admin(18834): File /home/mailman/scripts/driver, line 80, in run_main admin(18834): import Mailman.pythonlib.cgi admin(18834): File ../Mailman/pythonlib/cgi.py, line 31, in ? admin(18834): import urllib admin(18834): File /usr/local/lib/python2.2/urllib.py, line 26, in ? admin(18834): import socket admin(18834): File /usr/local/lib/python2.2/socket.py, line 41, in ? admin(18834): from _socket import * admin(18834): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 admin(18834): [- Python Information -] admin(18834): sys.version= 2.2.2 (#1, Nov 20 2002, 18:28:42) [GCC 2.95.2 19991024 (release)] admin(18834): sys.executable = /usr/local/bin/python admin(18834): sys.prefix = /usr/local admin(18834): sys.exec_prefix= /usr/local admin(18834): sys.path = /usr/local admin(18834): sys.platform = sunos5 admin(18834): [- Environment Variables -] admin(18834): HTTP_PRAGMA: no-cache admin(18834): PYTHONPATH: /home/mailman admin(18834): SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(18834): SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(18834): SERVER_ADMIN: [EMAIL PROTECTED] admin(18834): SCRIPT_NAME: /mailman/listinfo admin(18834): SCRIPT_URI: http://www.cs.jhu.edu/mailman/listinfo admin(18834): SERVER_SIGNATURE: ADDRESSApache/1.3.27 Server at www.cs.jhu.edu Port 80/ADDRESS Note the Import error above. So... again, it worked until we installed the new Apache and new openssl. Then, it stopped working giving the above errors. Rebuilding python did not help. Any ideas of what I can try? Is there really a bug in our version of Mailman? And should I be reinstalling Mailman? or is there an easier fix? Thanks a bunch in advance, and if you could seperately CC: me on your post to the mailman list, that would be much appreciated. Thanks! Steve [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable
RE: [Mailman-Users] New apache is causing my mailman to fail...
Hmmm... Actually, I need to modify one of my earlier statements... Last week, we needed to upgrade our Apache Web server to 1.3.27. Mailman failed with errors I submitted earlier (that error log entry was from last night, but it was similar to what we got a week ago, which you'll find below). At that time (last week), though, we were running an older version of openssl (plain 'ol 0.9.6, if I recall). ** Before the Apache install last week, mailman worked fine with the Apache 1.3.14 and the older openssl. With the newer Apache and the older openssl, mailman's web interface broke with the errors I submitted. ** We also had to upgrade our openssl to the latest version (version OpenSSL 0.9.6g 9 Aug 2002) We actually did this (upgrading to the latest openssl) recently, in an attempt to hopefully have mailman work with the latest version of Apache. ( Oh, and we upgraded to the latest openssl, too, because of the many exploits of the older openssl. :) So, even before we upgraded openssl, merely upgrading apache broke our mailman web interface. Before we even upgraded openssl, but AFTER we upgraded Apache, here are the mailman error logs: dmin(8622): [- Mailman Version: 2.0.8 -] admin(8622): [- Traceback --] admin(8622): Traceback (most recent call last): admin(8622): File /home/mailman/scripts/driver, line 80, in run_main admin(8622): import Mailman.pythonlib.cgi admin(8622): File ../Mailman/pythonlib/cgi.py, line 31, in ? admin(8622): import urllib admin(8622): File /usr/local/lib/python2.2/urllib.py, line 26, in ? admin(8622): import socket admin(8622): File /usr/local/lib/python2.2/socket.py, line 41, in ? admin(8622): from _socket import * admin(8622): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF f lags value: 768 admin(8622): [- Python Information -] admin(8622): sys.version= 2.2.2 (#1, Nov 8 2002, 16:56:01) [GCC 2.95.2 19991024 (release)] admin(8622): sys.executable = /usr/local/bin/python admin(8622): sys.prefix = /usr/local admin(8622): sys.exec_prefix= /usr/local admin(8622): sys.path = /usr/local admin(8622): sys.platform = sunos5 admin(8622): [- Environment Variables -] admin(8622):PYTHONPATH: /home/mailman admin(8622):SERVER_SOFTWARE: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 admin(8622):SCRIPT_FILENAME: /home/mailman/cgi-bin/listinfo admin(8622):SERVER_ADMIN: [EMAIL PROTECTED] admin(8622):SCRIPT_NAME: /mailman/listinfo admin(8622):SCRIPT_URI: http://www.cs.jhu.edu/mailman/listinfo admin(8622):SERVER_SIGNATURE: ADDRESSApache/1.3.27 Server at www.cs.jhu.edu Port 80/ADDRESS You;ll see these are similar to the logs we got AFTER we installed the newer openssl. Steve -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New apache is causing my mailman to fail...
Steve Rifkin wrote: admin(8622): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 My guess would be that you compiled python yourself, against the old version of openssl. now that you've upgraded openssl, python doesn't work because it can't find the old openssl. Or at least, the library isn't the same. If you tried running python by itself (just type in /usr/local/bin/python), you may find that it won't work either. You'll have to recompile python again. -- W | I haven't lost my mind; it's backed up on tape somewhere. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New apache is causing my mailman to fail...
Python worked fine before and after the openssl upgrade. Mailman worked before the openssl upgrade but only with the older Apache. With the new Apache and older ssl, mailman's web interface broke. Same errors. With the new openssl, we still get the same errors. As a precaution, I reinstalled python again. Openssl and python and apache all work, just not with mailman. Steve Date: Thu, 21 Nov 2002 12:50:38 -0700 From: Ashley M. Kirchner [EMAIL PROTECTED] X-Accept-Language: en MIME-Version: 1.0 To: Steve Rifkin [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [Mailman-Users] New apache is causing my mailman to fail... Content-Transfer-Encoding: 7bit Steve Rifkin wrote: admin(8622): ImportError: ld.so.1: /usr/local/bin/python: fatal: /usr/local/ssl/lib/libssl.so.0.9.6: bad ELF flags value: 768 My guess would be that you compiled python yourself, against the old version of openssl. now that you've upgraded openssl, python doesn't work because it can't find the old openssl. Or at least, the library isn't the same. If you tried running python by itself (just type in /usr/local/bin/python), you may find that it won't work either. You'll have to recompile python again. -- W | I haven't lost my mind; it's backed up on tape somewhere. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. Steve Rifkin - JHU CS Dept Sr. Unix Systems Administrator Technical Director [EMAIL PROTECTED] 410-516-6281 -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New apache is causing my mailman to fail...
Steve Rifkin wrote: Python worked fine before and after the openssl upgrade. Mailman worked before the openssl upgrade but only with the older Apache. With the new Apache and older ssl, mailman's web interface broke. Same errors. With the new openssl, we still get the same errors. As a precaution, I reinstalled python again. Openssl and python and apache all work, just not with mailman. Did you guys by any chance recompile mailman as well? (not that it should make any difference, but it wouldn't hurt) -- W | I haven't lost my mind; it's backed up on tape somewhere. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New apache is causing my mailman to fail...
No, we hadn't touched mailman at all. Really, all we had done was upgrade Apache. Upgrading ssl and rebuilding python happened AFTER mailman's web interface stopped working. Steve Date: Thu, 21 Nov 2002 13:47:51 -0700 From: Ashley M. Kirchner [EMAIL PROTECTED] X-Accept-Language: en MIME-Version: 1.0 To: Steve Rifkin [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] New apache is causing my mailman to fail... Content-Transfer-Encoding: 7bit Steve Rifkin wrote: Python worked fine before and after the openssl upgrade. Mailman worked before the openssl upgrade but only with the older Apache. With the new Apache and older ssl, mailman's web interface broke. Same errors. With the new openssl, we still get the same errors. As a precaution, I reinstalled python again. Openssl and python and apache all work, just not with mailman. Did you guys by any chance recompile mailman as well? (not that it should make any difference, but it wouldn't hurt) -- W | I haven't lost my mind; it's backed up on tape somewhere. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. Steve Rifkin - JHU CS Dept Sr. Unix Systems Administrator Technical Director [EMAIL PROTECTED] 410-516-6281 -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
