View Issue Details

IDProjectCategoryView StatusLast Update
0011655mantisbtbugtrackerpublic2010-06-09 03:45
Reporteralitvak Assigned Togiallu  
PriorityimmediateSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Summary0011655: Accessing issue 00004286 causes crash
Description

I tried various ways accessing issue 0004286 it returns error 500. It didn't happen a week ago and other issues here earlier or later seem to be accessible just fine.

TagsNo tags attached.

Relationships

related to 0008561 closedgiallu THIS INSTALLATION: timeout on adding bugnote to issue4286 
has duplicate 0011664 closeddhx Visiting issue 4286 on www.mantisbt.org causes internal server error 
has duplicate 0011660 closeddhx Changelog throws "Internal Server Error" at this tracker 
has duplicate 0011669 closeddhx Get a 500 error when trying to access issue 4286 
has duplicate 0011670 closeddhx Mantis.org's Mantis's Change Log page is returning 500 error 

Activities

alitvak

alitvak

2010-03-14 15:20

reporter   ~0024736

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@mantisbt.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

alitvak

alitvak

2010-03-15 10:38

reporter   ~0024753

Any updates? This is something I have never seen before as access to simple issues causes internal server error.

jreese

jreese

2010-03-15 13:55

reporter   ~0024758

The 500 ISE is a problem with out-of-memory in PHP. 0004286 has so many bugnotes attached to it that it exceeds the memory limits of PHP on the server while trying to fetch all of the bugnotes. MantisBT should be recognizing this situation and either paginating the bugnotes, or splitting note retrieval into multiple SQL queries to prevent the OOM situation.

alitvak

alitvak

2010-03-15 15:16

reporter   ~0024760

Can anything be done for this now? Can memory allocation in php.ini be increased? I realize it is probably not a vital issue but I am following the bug which created a feature that makes mantis more attractive to use around here and unfortunately the only way to access latest information would be the bug note. I hope eventually developers will post it to some mantis forum and keep code in git.

Thanks for response.

alitvak

alitvak

2010-03-18 05:09

reporter   ~0024790

Any updates? It seems that I am not the only one interested in seeing this resolved. If it difficult to fix or just not enough resources, can someone contact plugin developers and ask them to post a a forum topic or any other means of support / contribution to plugin.

Thanks,

giallu

giallu

2010-03-18 06:01

reporter   ~0024792

I tried raising php memory limit to 128M but was still borken so I put it back to the original value (50M !)

giallu

giallu

2010-03-18 06:10

reporter   ~0024793

I found the culprit, it went something like this:

  • someone renamed the mod_security.conf file as a mean to disable the module
  • the last update had newer mod_security rpm
  • rpm duly reinstalled mod_security.conf
  • at first apache restart the module started
  • fail

Now I removed the package, that's the safest way to disable it...