Re: [Mailman-Users] We're sorry, we hit a bug!
Well, on a new implementation, I'm getting the same thing in 2.18-1. What'd you do to fix it on your end? On Tue, 1 Jul 2014 17:33:19 +0200, you wrote: Mark Sapiro m...@msapiro.net wrote: The above message indicates the traceback was written to some 'error' log, just not the one you're looking at. You can always edit (temporarily) Mailman's scripts/driver and at line 33 change STEALTH_MODE = 1 to STEALTH_MODE = 0 and that will allow the traceback and other diagnostic info to be displayed instead of the We're sorry, we hit a bug! message. Would like to show some logging, but it simply is not there. It was successfully written to an 'error' log somewhere or the We're sorry, we hit a bug! message would say: Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. Thanks Mark, the page is showing that the log location was not writeable, must be the bug. Resetting the LOG_DIR to default saved me. Apologies for the noise. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] We're sorry, we hit a bug!
On 01/10/2015 06:53 AM, Steve Matzura wrote: Well, on a new implementation, I'm getting the same thing in 2.18-1. What'd you do to fix it on your end? I think that one was a permissions error. As Mr. Wagenaar reported, he had overridden the LOG_DIR setting and it pointed to an unwritable location. -- 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 https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] We're sorry, we hit a bug!
On 07/01/2014 07:08 AM, Roel Wagenaar wrote: L.S. Bug in Mailman version 2.1.15 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 theMailman error logs. The above message shows up on the web pages, unfortunately the last log written to is qrunner, error is empty, so no info on what it is about. The above message indicates the traceback was written to some 'error' log, just not the one you're looking at. You can always edit (temporarily) Mailman's scripts/driver and at line 33 change STEALTH_MODE = 1 to STEALTH_MODE = 0 and that will allow the traceback and other diagnostic info to be displayed instead of the We're sorry, we hit a bug! message. Would like to show some logging, but it simply is not there. It was successfully written to an 'error' log somewhere or the We're sorry, we hit a bug! message would say: Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. -- 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 https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] We're sorry, we hit a bug!
Mark Sapiro m...@msapiro.net wrote: The above message indicates the traceback was written to some 'error' log, just not the one you're looking at. You can always edit (temporarily) Mailman's scripts/driver and at line 33 change STEALTH_MODE = 1 to STEALTH_MODE = 0 and that will allow the traceback and other diagnostic info to be displayed instead of the We're sorry, we hit a bug! message. Would like to show some logging, but it simply is not there. It was successfully written to an 'error' log somewhere or the We're sorry, we hit a bug! message would say: Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. Thanks Mark, the page is showing that the log location was not writeable, must be the bug. Resetting the LOG_DIR to default saved me. Apologies for the noise. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Ignorence is when you don't know anything and somebody finds out. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] We're sorry, we hit a bug!
J.R. Constance wrote: I'm hoping someone can help me figure out a problem that I've been having for some time now. For some of my lists when I try to log in and approve/discard posts using the admin function I get the following error. This is obviously a cpanel version of mailman. I am also trying to get support through my hosting company on this. We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. Looking at the error log for this particular error shows the following: Sep 07 07:56:13 2007 (19565) Uncaught runner exception: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Traceback (most recent call last): File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py, line 100, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/ Switchboard.py, line 164, in dequeue msg = email.message_from_string(msg, Message.Message) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ __init__.py, line 51, in message_from_string return Parser(_class, strict=strict).parsestr(s) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 240, in _parsebody msgobj = self.parsestr(part) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 265, in _parsebody msg = self.parse(fp) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 206, in _parsebody raise Errors.BoundaryError( BoundaryError: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Ignoring unparseable message: 1173539747.1827431+c4b30a10b02f512f3aa88e8038d6f17843cdb81b Sep 07 07:56:13 2007 (19565) Uncaught runner exception: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Traceback (most recent call last): File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py, line 100, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/local/cpanel/3rdparty/mailman/Mailman/Queue/ Switchboard.py, line 164, in dequeue msg = email.message_from_string(msg, Message.Message) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ __init__.py, line 51, in message_from_string return Parser(_class, strict=strict).parsestr(s) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 240, in _parsebody msgobj = self.parsestr(part) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 265, in _parsebody msg = self.parse(fp) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 64, in parse self._parsebody(root, fp, firstbodyline) File /usr/local/cpanel/3rdparty/mailman/pythonlib/email/ Parser.py, line 206, in _parsebody raise Errors.BoundaryError( BoundaryError: No terminating boundary and no trailing empty line Sep 07 07:56:13 2007 (19565) Ignoring unparseable message: 1187578207.7474239+de47fddadb334d46d06c9248df89448cf2a433ce The above two 'errors' and tracebacks just coincidently occurred about the same time as your 'we hit a bug' error. The above errors are due to malformed (unparseable) messages which almost certainly were spam sent to your lists (probably the same message sent to two lists). Sep 07 07:58:41 2007 admin(25812): admin(25812): [- Mailman Version: 2.1.9.cp2 -] admin(25812): [- Traceback --] admin(25812): Traceback (most recent call last):
Re: [Mailman-Users] We're sorry, we hit a bug! but no logs???
Thought I had cracked it. Click on Create to make my first list and I get: Bug in Mailman version 2.1.5 * * * I use 2.1.5 mailman version. This version has bugs ? better to use 2.1.6 ? Thanks ! antoine -- 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] We're sorry, we hit a bug! but no logs???
Brian Parish wrote: Thought I had cracked it. Click on Create to make my first list and I get: Bug in Mailman version 2.1.5 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. OK fine, but there are no files in $prefix/logs and nothing in the system log. By default, they're in $var_prefix/logs if that makes a difference. Look in mm_cfg.py for an assignment to LOG_DIR. If there isn't one, look in Defaults.py in case someone changed it there. -- 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] We're sorry, we hit a bug! but no logs???
--On 31. oktober 2005 15:20 +0100 antoine [EMAIL PROTECTED] wrote: Thought I had cracked it. Click on Create to make my first list and I get: Bug in Mailman version 2.1.5 * * * I use 2.1.5 mailman version. This version has bugs ? better to use 2.1.6 ? Thanks ! antoine I had the same error on my 2.1.6 on FreeBSD 5.4. The solution was to deinstall it and also delete directory mailman as well and the install new fresh copy. Why this happened I still don't know. But after that I haven't had any problems. Sasa pgpRFAAiLiH5q.pgp Description: PGP signature -- 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] We're sorry, we hit a bug!
Hi Dan, Thanks for the quick reply. Just found out that the Python module xml wasn't installed. After i installed it the bug was gone. Strange that this isn't checked in the update indeed! (running SuSE 9.2) Thanks anyway. Grz. Johan Op vrijdag 28 januari 2005 20:22, schreef u: On Jan 28, 2005, at 1:13 PM, Johan Barelds wrote: It seems that there is something wrong with python module xml.sax.saxutils. Anyone any clues? I don't remember the exact answer, but this has been discussed and a fix given on this list just within the last few days, so a quick search of the archives should find the answer. This is on SuSE? I believe the RPM you used to update mailman doesn't check for dependencies. Dan -- Kind Regards / Met vriendelijke groet, Johan Barelds Good-IT! Tel.+31(0)70-3965230Strijplaan 320 Mob.+31(0)6-542537502285 HZ Rijswijk(ZH) [EMAIL PROTECTED] http://www.good-it.com -- 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/
Re: [Mailman-Users] We're sorry, we hit a bug! (resolved)
Alright, I tracked down the problem and found out it had nothing to do with mailman. But in case someone has the same problem I'll post it (even though it's really really embarassing). Okay, I should I have been able to figure it out, it happened for no obvious reason, was just sitting there. It wasn't writing to the error log. Installing it fresh didn't help. That's right, I was out of disk space. I made some space and all is better. Sorry for all my trouble. -Aaron -- Original Message -- From: mailman [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Thu, 18 Oct 2001 20:23:10 -0700 I have a second email account that I use for outgoing, and it wants to wait for moderation (and I don't want to :). So sorry if this gets double posted. I checked all the processes and the only ones given to mailman is /usr/bin/python -S /home/mailman/cron/qrunner, so I cleared out the processes and still get the bug message. I've tried it on 3 different computers each with different browsers, but I tried it with netscape 4.7 and it still gives the bug message. And I checked the logs again, and there's nothing in error, but here's some stuff from the other log files: tail logs/smtp Oct 17 16:54:39 2001 (4334) All recipients refused: (111, 'Connection refused') Oct 17 16:54:39 2001 (4334) smtp for 1 recips, completed in 0.184 seconds tail logs/post Oct 17 16:54:39 2001 (4334) post to test from [EMAIL PROTECTED], size=1294, 1 failures tail logs/smtp-failure Oct 17 16:54:39 2001 (4334) -1 [EMAIL PROTECTED] (ignore)] Maybe that will help? -Aaron -- Original Message -- From: Jon Carnes [EMAIL PROTECTED] Reply-To: Jon Carnes [EMAIL PROTECTED] Date: Thu, 18 Oct 2001 18:46:53 -0400 Check the lock files in ~mailman/locks/ If there are any lock files check the processes and see if they are actually running. The process is part of the name of the lock file. Kill any processes that are frozen and then delete the lock files for them. Have you upgraded or changed your browser lately? This could cause problems when trying to access the Admin pages. Jon Carnes - Original Message - From: Ken [EMAIL PROTECTED] To: Aaron Nikula [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 18, 2001 5:44 PM Subject: Re: [Mailman-Users] We're sorry, we hit a bug! Have you just tried resetting the admin password? Ken On Wednesday 17 October 2001 11:33 pm, Aaron Nikula wrote: Hello, I setup mailman 2.0.2 and had it running for a long while. Last night for no obvious reason, it started giving this error when trying to get into admin: We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. I checked the error log and it said nothing. So I tried upgrading to 2.0.4, didn't help. I tried completely removing the old version, still no go. It is getting to the admin login page, it's when you login that it gives an error (when the wrong password is entered, it's okay, but doesn't help much :). Does anyone have ideas where I can start troubleshooting this stuff? I restarted apache, sendmail, etc. And started from a fresh installation. Thanks for any help. -Aaron -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] We're sorry, we hit a bug!
I checked all the processes and the only ones given to mailman is /usr/bin/python -S /home/mailman/cron/qrunner, so I cleared out the processes and still get the bug message. I've tried it on 3 different computers each with different browsers, but I tried it with netscape 4.7 and it still gives the bug message. And I checked the logs again, and there's nothing in error, but here's some stuff from the other log files: tail logs/smtp Oct 17 16:54:39 2001 (4334) All recipients refused: (111, 'Connection refused') Oct 17 16:54:39 2001 (4334) smtp for 1 recips, completed in 0.184 seconds tail logs/post Oct 17 16:54:39 2001 (4334) post to test from [EMAIL PROTECTED], size=1294, 1 failures tail logs/smtp-failure Oct 17 16:54:39 2001 (4334) -1 [EMAIL PROTECTED] (ignore)] Maybe that will help? -Aaron - Original Message - From: Jon Carnes [EMAIL PROTECTED] To: Aaron Nikula [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 18, 2001 3:46 PM Subject: Re: [Mailman-Users] We're sorry, we hit a bug! Check the lock files in ~mailman/locks/ If there are any lock files check the processes and see if they are actually running. The process is part of the name of the lock file. Kill any processes that are frozen and then delete the lock files for them. Have you upgraded or changed your browser lately? This could cause problems when trying to access the Admin pages. Jon Carnes - Original Message - From: Ken [EMAIL PROTECTED] To: Aaron Nikula [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 18, 2001 5:44 PM Subject: Re: [Mailman-Users] We're sorry, we hit a bug! Have you just tried resetting the admin password? Ken On Wednesday 17 October 2001 11:33 pm, Aaron Nikula wrote: Hello, I setup mailman 2.0.2 and had it running for a long while. Last night for no obvious reason, it started giving this error when trying to get into admin: We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. I checked the error log and it said nothing. So I tried upgrading to 2.0.4, didn't help. I tried completely removing the old version, still no go. It is getting to the admin login page, it's when you login that it gives an error (when the wrong password is entered, it's okay, but doesn't help much :). Does anyone have ideas where I can start troubleshooting this stuff? I restarted apache, sendmail, etc. And started from a fresh installation. Thanks for any help. -Aaron -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] We're sorry, we hit a bug!
Check the lock files in ~mailman/locks/ If there are any lock files check the processes and see if they are actually running. The process is part of the name of the lock file. Kill any processes that are frozen and then delete the lock files for them. Have you upgraded or changed your browser lately? This could cause problems when trying to access the Admin pages. Jon Carnes - Original Message - From: Ken [EMAIL PROTECTED] To: Aaron Nikula [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 18, 2001 5:44 PM Subject: Re: [Mailman-Users] We're sorry, we hit a bug! Have you just tried resetting the admin password? Ken On Wednesday 17 October 2001 11:33 pm, Aaron Nikula wrote: Hello, I setup mailman 2.0.2 and had it running for a long while. Last night for no obvious reason, it started giving this error when trying to get into admin: We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. I checked the error log and it said nothing. So I tried upgrading to 2.0.4, didn't help. I tried completely removing the old version, still no go. It is getting to the admin login page, it's when you login that it gives an error (when the wrong password is entered, it's okay, but doesn't help much :). Does anyone have ideas where I can start troubleshooting this stuff? I restarted apache, sendmail, etc. And started from a fresh installation. Thanks for any help. -Aaron -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] We're sorry, we hit a bug!
I have a second email account that I use for outgoing, and it wants to wait for moderation (and I don't want to :). So sorry if this gets double posted. I checked all the processes and the only ones given to mailman is /usr/bin/python -S /home/mailman/cron/qrunner, so I cleared out the processes and still get the bug message. I've tried it on 3 different computers each with different browsers, but I tried it with netscape 4.7 and it still gives the bug message. And I checked the logs again, and there's nothing in error, but here's some stuff from the other log files: tail logs/smtp Oct 17 16:54:39 2001 (4334) All recipients refused: (111, 'Connection refused') Oct 17 16:54:39 2001 (4334) smtp for 1 recips, completed in 0.184 seconds tail logs/post Oct 17 16:54:39 2001 (4334) post to test from [EMAIL PROTECTED], size=1294, 1 failures tail logs/smtp-failure Oct 17 16:54:39 2001 (4334) -1 [EMAIL PROTECTED] (ignore)] Maybe that will help? -Aaron -- Original Message -- From: Jon Carnes [EMAIL PROTECTED] Reply-To: Jon Carnes [EMAIL PROTECTED] Date: Thu, 18 Oct 2001 18:46:53 -0400 Check the lock files in ~mailman/locks/ If there are any lock files check the processes and see if they are actually running. The process is part of the name of the lock file. Kill any processes that are frozen and then delete the lock files for them. Have you upgraded or changed your browser lately? This could cause problems when trying to access the Admin pages. Jon Carnes - Original Message - From: Ken [EMAIL PROTECTED] To: Aaron Nikula [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 18, 2001 5:44 PM Subject: Re: [Mailman-Users] We're sorry, we hit a bug! Have you just tried resetting the admin password? Ken On Wednesday 17 October 2001 11:33 pm, Aaron Nikula wrote: Hello, I setup mailman 2.0.2 and had it running for a long while. Last night for no obvious reason, it started giving this error when trying to get into admin: We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. I checked the error log and it said nothing. So I tried upgrading to 2.0.4, didn't help. I tried completely removing the old version, still no go. It is getting to the admin login page, it's when you login that it gives an error (when the wrong password is entered, it's okay, but doesn't help much :). Does anyone have ideas where I can start troubleshooting this stuff? I restarted apache, sendmail, etc. And started from a fresh installation. Thanks for any help. -Aaron -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
