|
Size: 863
Comment:
|
← Revision 4 as of 2015-03-04 05:35:25 ⇥
Size: 783
Comment: un WikiName
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma page-filename DOC/versions/14352612 | #pragma page-filename DOC/versions/4030647 |
| Line 3: | Line 3: |
| Attempts to manipulate a 'large' post in the admindb interface and possibly other web actions like getting a roster for a 'large' list give the "We're sorry, we hit a bug!" response with an error log traceback indicating a MemoryError exception. | Attempts to manipulate a 'large' post in the admindb interface and possibly other web actions like getting a roster for a 'large' list give the "We're sorry, we hit a bug!" response with an error log traceback indicating a !MemoryError exception. |
| Line 15: | Line 16: |
| ''Last changed on Tue Mar 21 01:36:07 2006 by'' Mark Sapiro <<Color2(Converted from the Mailman FAQ Wizard, col=darkgreen)>>This is one of many [[../Frequently Asked Questions|Frequently Asked Questions]]. |
Converted from the Mailman FAQ Wizard This is one of many [[../Frequently Asked Questions|Frequently Asked Questions]]. |
6.18. MemoryError exceptions from the web interface.
Attempts to manipulate a 'large' post in the admindb interface and possibly other web actions like getting a roster for a 'large' list give the "We're sorry, we hit a bug!" response with an error log traceback indicating a MemoryError exception.
These can be caused by the web server placing a limit on the amount of memory that can be used by a CGI script. This is done in Apache with an
RLimitMEM
directive.
If you are seeing such errors, check your web server for such a limit and try raising it or removing it completely.
Converted from the Mailman FAQ Wizard
This is one of many Frequently Asked Questions.