Using RAM as cache directory + Generic 500 error + Rename failure when saving changes #630
Comments
|
@MarioKnight Thanks for this detailed report. I'm tagging this so that we can run some additional tests to see if there are any problems that we can work around in relation to a RAM disk and atomic cache writes. |
|
@MarioKnight @jaswsinc This is almost certainly a dupe of #624. |
|
@MarioKnight If possible, would you be able to try some of @jaswsinc's suggestions in #624 (comment) and see if that resolves the Error 500 issue? We've received several similar reports with PHP 5.6 but we haven't been able to pin down what's actually causing the issue, so anything you could do to help here would be hugely appreciated. 😄 |
|
It doesn't look like any of the suggestions in the linked comment helped. WP memory limit is already set to an absurdly high value (apparently I never lowered this back to a reasonable one pending various upload tests a year and a half or so ago, oops), and I don't appear to have opcache installed or configured on this server. I still put in the line to disable it just in case, however this did not change the behavior or error logs in apache. |
|
Also, if this helps, here is the phpinfo() output for the site showing this behavior: https://missdream.org/phpinfo.php |
|
I just installed opcache, checked the behavior which remained the same. I retried the suggestions however nothing changed in the browser or error logs. |
|
@MarioKnight The error you're seeing consistently in your error logs is |
|
Correct, the error log block in my initial post has remained consistent. That message block only occurs when I click the save changes button within the plugin options. I did have other errors in my logs, but I was able to address them separately, and watched the live logs following to confirm. I also updated WP core to 4.4 this morning, and there was no change in this behavior. |
|
@MarioKnight Great. Thank you. In that case my feeling is that the issue you're experiencing is not related to the issue in #624 (which we suspect is related to a bug in Opcache), but rather more likely related to configuring your cache directory to use a RAM disk. The next step that I would suggest for narrowing this issue down would be to temporarily switch back to using the regular disk for the cache directory and see if the issue persists. |
raamdev
changed the title
|
I unmounted the cache directory and the 500 error is gone! I will keep it unmounted for the time being, however if you have anything you'd like to test for this issue, I'll be happy to test. |
raamdev
changed the title
raamdev
changed the title
|
@MarioKnight Thank you! I've updated the title of this GitHub issue to reflect that his appears to be specific to using RAM as the cache directory. |
|
@MarioKnight A new version of ZenCache was just released that includes many bug fixes and enhancements. You might want to give this release candidate a try to see if it addresses any of the issues you were having here. See http://zencache.com/zencache-pro-v151216-rc-release-candidate/ |
|
Thank you for the heads up on the RC posting. I've gone ahead installed the RC, and sadly it doesn't seem to address the issues in this and in #613 (or perhaps a different issue since the cron event was not actually removed from what I was able to tell, will make separate issue after this post). I re-mounted the cache directory to tmpfs, and the 500 error returned when saving changes. As from the error logs: One thing I noticed that I hadn't before, was the mention of The first segments of the PHP warning and fatal error appear to have been unchanged. To make things more interesting (though I can understand the logic here), is when I disable ZC and hit save before un-mounting, there's no 500. |
|
@MarioKnight Thank you for the update and the additional information. That will definitely help us when we take a closer look at this during the next development cycle. For now, I recommend not using the RAM disk. |
I touched upon this in #613 , however I believe this is unrelated so I am making a separate report. Whenever I save changes to ZenCache Pro options, I ger a generic 500 error in my browser. When I navigate back to the options page, the changes I made are present. When making one just a few minutes ago, I decided to check the apache error log for the domain for any hints. I was able to find this block in the logs:
This is for a site on my personal server, running PHP 5.6.16, WP core 4.3.1. It's appeared consistently since the most recent Pro release. This was also the first update to ZCP following the move to my cache directory to RAM as per the KB article on http://zencache.com/kb-article/how-to-use-ram-memory-for-your-cache-directory/ . Please let me know if you need any more information from my end. Thank you.
The text was updated successfully, but these errors were encountered: