-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZenCache + PHP 5.6 FASTCGI = Internal Server Error #624
Comments
ZenCache uses output buffering which can exacerbate problems in some buggy versions of PHP. I'd suggest a review of this thread, followed by attempts to alter the PHP configuration in subtle ways. Or, perhaps upgrading to a slightly newer (or slightly older) version of PHP to see if that resolves this. Note: I'm not seeing anything in the log that points to a bug in ZenCache, but it does sound like ZenCache being active is increasing the odds of a memory leak in what may already be a problematic PHP configuration. |
Also reported here (internal ticket): https://websharks.zendesk.com/agent/tickets/9635 |
Also reported here (internal ticket): https://websharks.zendesk.com/agent/tickets/9774 (note that this was with ZenCache Lite v151107) |
Related PHP bug reports that could be the underlying cause of this:
See also: https://bugs.php.net/search.php?cmd=display&search_for=zend_mm_heap&x=0&y=0 |
Another possible PHP bug that could cause this: |
Next Pro Release Changelog:
|
ZenCache Pro v151220 has been released and includes changes worked on as part of this GitHub Issue. See the release announcement for further details. This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#624). |
Reference: https://websharks.zendesk.com/agent/tickets/9600
User reported an
Internal Server Error
when running ZenCache with PHP 5.6 FASTCGI. User determined the issue was ZenCache and PHP 5.6 FASTCGI using sound troubleshooting techniques (see referenced ticket). Error logs summarized below:The text was updated successfully, but these errors were encountered: