Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Hello,
I have configured 25 topics per page and 30 comments per topic as far as the paging is concerned.
While everything works OK on my local XAMPP installation (PHP 5.4), all views of topics with post count equal to or greater than 23 (number deduced after a lot of tries), gives a WSOD on the production server (PHP 5.3).
Any idea as to why this happens and specifically after 23 posts?
Thank you!
P.S. Sorry for the incomplete headline...
Comments
Comment #1
troky CreditAttribution: troky commentedCheck Apache logs for error and report back.
Comment #2
marktheshark CreditAttribution: marktheshark commentedLatest log messages:
Comment #3
troky CreditAttribution: troky commentedIt looks like eaccelerator and PHP 5.4 don't play well. Try with eaccelerator disabled.
From above log I can't see anything related to AF at all.
Comment #4
marktheshark CreditAttribution: marktheshark commentedThe production server has PHP 5.3.
I also see in the error.log:
I just set my local deployment to 128M (just like the production server) to see if the problem can be reproduced, but I couldn't reproduce it.
Running cron fails though, exhausting the memory.
I agree this does not seem to be AF related, I will change area as soon as I have some indication where it belongs.
Comment #5
marktheshark CreditAttribution: marktheshark commentedTried disabling eaccelerator via .htaccess (though I'm not sure I'm doing it successfully):
Doesn't seem to make a difference.
Comment #6
marktheshark CreditAttribution: marktheshark commentedBtw, found this old similar issue from AF 6 (not an actual AF issue).
However, contrary to that issue, I cannot view the first page of posts either.
Have contacted the host to check if eaccelerator can be disabled and memory increased for this site.
Comment #7
marktheshark CreditAttribution: marktheshark commentedComment #8
hwi2 CreditAttribution: hwi2 commentedI find that a lot of the answers are right inside the log report on Drupal. That has saved me a lot of headaches.
Comment #9
marktheshark CreditAttribution: marktheshark commentedThe host has disabled Eaccelerator for me and temporarily upped the PHP memory limit to 256M, which is admittedly an insane amount of memory for a Drupal installation.
I will go through my list of modules to disable the unnecessary ones and check the memory usage with Devel.
Comment #9.0
marktheshark CreditAttribution: marktheshark commentedmore info