M

I’ve upgrade to latest version and noticed the low resources scan so I gave it a try. Still same error. I also noticed and fixed the litespeed setting. I keep seeing the wp_memory_limit set to 40MB in the diagnostic page. It would be helpful to tell me where you get that value from, so I can better explain it to the hosting service support. In the wp-config the value is set to 128, and in the scan error it shows it uses 256MB.

Thank you

Not very easy to do this. I’m experiencing the issue on a production site, not a test one. I will try and let you know. Thanks

I have re-checked with the webhost and they set the memory limit to the correct value on the server. Even so, I still get the error on scan:

[May 27 06:38:36] Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 43178820 bytes) in /home/***/public_html/wp-content/plugins/wordfence/lib/wfConfig.php on line 493

I did that and the error was:
[May 26 11:47:08] Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 42141171 bytes) in /home/***/public_html/wp-content/plugins/wordfence/lib/wfConfig.php on line 493

Hi,

thanks for your reply. Didn’t go well. I got the host to change the WP limit (couldn’t confirm it though on my own..) then I went back and started a scan. It stopped with the same error:

Allowed memory size of 419430400 bytes exhausted (tried to allocate 66424769 bytes) in /home/***/public_html/wp-content/plugins/wordfence/lib/wfConfig.php on line 493

And then I tried to convert bytes to MB to see what’s wrong. And 419430400 is actually 400MB which is way beyond the 256M recommended memory. And scan was also trying to allocate another 60MB (or so).

Any suggestions are welcomed.

Many thanks

Thanks a lot for your feedback. Report already sent via email. The Options set in scan will follow shortly.

Hi @wfyann,

it eventually dissapeared (after the next completed scan). Yes, all is OK in the MySQL section and everywhere else.

Thanks for your reply

I’ve sent you an email. Thanks.

Thanks @raamdev. I’ll try discuss these things with my hosting provider.

@raamdev

I’m handling the https redirection in htaccess already, with the exact rule you wrote in your answer.

Cloud-based hosting services often use distributed or network-based filesystems that don’t play well with file-locking or heavy writes/rewrites. I suggest working with your hosting company to see if you can resolve the issue or trying a different hosting platform.

Changing the hosting environement is not an option, I’m pretty happy with the service they provide. What exactely do I need to ask them to look at? Could you please be more specific?

Many thanks.

@raamdev:
I also found this interested topic (related to temp files being left behind) here: https://github.com/websharks/comet-cache/issues/397

@raamdev:

Also, can you tell me a bit more about the hosting environment? Web server version, server OS type, PHP version, filesystem type (e.g., NFS or Cloud-based storage?); all of those would be helpful.

My site is hosted on a cloud server (shared environement) CloudLinux + KSplice, litespeed, PHP version 5.6.30 and MySQL 5.5.54-cll.

The only thing I asked my webhost provider was which directory was the one eating up the space.

I’ve been watching the space consumption and the Comet Cache directory gets at least 1GB bigger each day. I did notice the following:
– after the data deletion, there’s a directory from feb 8 called cache-589d4fa862ffd375866253-tmp which didn’t get deleted anymore. Only the most recent directories get some content deleted. I assume I can safely delete the old tmp directory, right?
– in each directory there are two folders, one for http and one for https. Why is that? My site runs on https only (a redirect is in place to handle older http indexed pages and load them on https)

PS: my site is big – over 65k posts. And thanks for taking the time to answer. Must admit such a support level makes me wonder what would the benefits be if I rand the pro version instead of the lite one.

@mpek

How did you find out how much space your cache consumes?

I wasn’t able to update a plugin due to quota beign exceeded so I started digging..

As per your other question, it appears from the article I recommended and from @raamdev answer earlier, you can safely delete those files too as long as they are in the wp-content/cache/comet-cache/cache/ directory.

@mpek there’s a very good explanation here, for your questions: https://cometcache.com/kb-article/wipe-clear-purge-terminology/

Hi Raam,

I’ve set debug to true, but none of the warnings were related to Comet Cache. And rights on the server folders are as they should be. I had seen that in other forum topics and checked it already, before opening this ticket (to make sure I don’t duplicate).

Thanks!
M

De-activate the plugin / updating / re-activate – the solution ??