I have two different views which have one display returning an HTTP Error 500 (Internal Server Error)

These were working as of August 30th 2011 and we discovered yesterday they had stopped working on the production site. The development site on the same server still functions fine. No changes were made to the view or Drupal installation during that time. The displays work in the views preview. Views 6.x-2.12 with Ctools 6.x-1.8

I've searched the issue queues and documentation, but don't find anything specific on how to troubleshoot or fix this issue.

Looking for suggestions,

Thanks!

Bob Snodgrass

Comments

davemaxg’s picture

davemaxg commented

Sounds like it could be a memory issue. Check your memory utilization on prod.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

Let's see whether it's a memory isuse.

bsnodgrass’s picture

bsnodgrass commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Turned out there WAS a change in module code posted to the site. This was not supposed to have been posted to production yet and a php function was being called from a missing include file.

Thanks to the folks at Hot Drupal who helped me find this! And thanks for the responses!

droshani’s picture

droshani commented

I have same issue with SimpleNews dependent posts, I can not open them in editing mode. As soon I click create or edit I can Error 500. Any idea how I can solve this issue?

I did upgrade some module like imageFields when this happened. I put back the older version but it did not help.

theohawse’s picture

theohawse commented

Well i had this issue, not sure if my solution will help at all.

problem : Certain view displays, (and panel nodes, weird) would return error 500.
clearing the cache ($ drush cc all) and reloading would fix only one page, problem then re-appears on another.

what worked for me: Disabled APC at /etc/php5/conf.d/apc-config.ini
from apc.enabled = 1 to apc.enabled = 0
then /etc/init.d/apache2 restart

now off to troubleshoot apc being ridiculous, monkey chasing the weasel.

Update: Still unsure as to what was the real problem, re-enabled apc and restarted apache - the 500 errors haven`t come back yet.