Recent content by guneetnarula

Thanks for the response!

I am curious, how did you solve the problem? I am planning to do this soon.

I am managing a large WP website (40GB uploads) with OLS and the litespeed cache plugin. Recently I saw that the /../lsws/cachedata directory size is 47GB. Purging cache from the plugin does not do anything. Two questions: 1. Why is this directory so huge? 2. Is it safe to remove all files...

I switched on debug mode, and found this on the bottom of the generated HTML page: Object Cache [total] 11320 [hit_incall] 10349 [hit] 0 [miss_incall] 400 [miss] 571 [set] 944 Does this mean LSMCD is working as intended?

So right now, using phpinfo() on all three sites, I can see that memcached support is enabled. The only problem is that the connection test in litespeed cache plugin on all of them says "failed"

I was able to enable the service by switching to UDS instead of TCP, but the connection test fails on all vhosts now. See: systemctl status lsmcd.service ● lsmcd.service - LiteSpeed LSMCD Daemon Loaded: loaded (/etc/systemd/system/lsmcd.service; enabled; vendor preset: enabled)...

Yes I checked that. For the vhost with the suExec enabled, it is not. For the other two, memcached is on it.

Until recently, I was not using the suExec mode (lsapi external app) on any of the three virtual hosts on my server. But I recently turned it on for one of them. Things look good except the memcached extension is showing disabled in the wp plugin object cache screen. On the other two vhost...

@ronaldst I have seen this before. Check GSC whether this is related to certain URLs or the entire site. I have mostly seen this with a limited set of URLs. And usually an updated sitemap helps when you press the "fix" button