Random cache miss without purge

1. before it starts or reach the end
2. yes, first case means cache on QC, second case means cache on origin but miss on QC
3. it should, unless something purged it

you may need to monitor the purge log for longer period

Thank you.

I have a purge log from another website from over a week, and there are no purges there other than wp-login, wp-load (updating websites from ManageWP) or purges after I worked on the website.

I am monitoring the debug/purge logs on 4 websites, on and off, every time I check a website and the cache misses, there is no purge in the logs (after a crawl, so should be cached)…

hmm? on and off may not be enough , you need to keep log enabled for a while , in order not to miss any log

and by any chance, your other sites are within same user + different virtual host? or different user + different virtualhost ?

Log is enabled, I don’t switch it off, by on and off I meant I check it like 2/3 times a week. Used the wrong words.

All websites are on the same user, same hosting. I contacted my hosting and did some testing on different websites with crawlers while checking the resources used on the hosting. While I had once that my IOPS and RAM limits were hit (during a crawl), I also had multiple times that crawling had very little impact on the resources…

On one occasion a website was crawled, no resource limits were hit during crawling, or the entire 24h after. And still after the 24h I had a cache: miss. (no purges in the log, no resources limit hit).

I am trying to check with my hosting to be 100% sure that it is not my resources that are causing this entire problem, but they are not very helpful yet and I don’t have enough knowledge to check it myself…

please also try to increase the debug log size , default is 3MBt, the early/earlier entries could be easily overwritten if you hold it as for week or more log.

This is happening between every crawl, my dots are always blue when I check a website. And I have crawling set on most websites every 28 – 48h. I have logs from over 10 days on a website, there are no purges other than mentioned earlier…

I have set the log size to 5mb on two websites. Hoe long should I check the purge log when this problem is happening every time between crawling?

wait a second , I noticed something

in crawler -> sitemap setting -> Drop Domain from Sitemap set it to ON , then cralw again.

That sounds promising, haha. I’ve set Drop Domain from Sitemap to ON, on 4 different websites, purged all, and crawled them.

For testing purposes I will wait until these websites get crawled again in 1/2 days to see what happens and if the dots will be green this time… Do you need me to do anything else?

no, that’s only thing , please let me know how it goes.

Update after 24 hours (after crawl):
Website 1: Home page on first load: miss. Other pages: miss. (I waited 2 more hours for the automatic crawl: most crawl dots are blue)
Website 2: Home page on first load: miss. Other pages: bkd.
Website 3: Home page on first load: miss. Other pages: bkd.
Website 4: Home page: hit. Other pages: bkd. (Some were: hit (X-Qc-Cache))

I am not touching website 4 until tomorrow, when the crawlers will automatically start again, to see if the dots will be green this time. But I don’t have much hope.

-No purges in all 4 website logs
-No resource limits are hit in hosting

Additional info, no idea if this has any value for you:

Sometimes the crawling process on a website takes weirdly long, and this also seems pretty random. For example I have this one simple website, 11 pages in total, and I took 21821 seconds to crawl today. During the same time another website was crawled, 19 pages, and it only took 3511 seconds. Same hosting, no resource spikes. This happens on all websites, sometimes it take just around an hour, and sometimes it can even take up to 10 hours.

please record the x-litespeed-cache , not x-qc-cache header

I am. There is no x-litespeed-cache header when x-qc-cache is: hit. It’s either both miss, or x-litespeed-cache: bkd, when x-qc-cache: miss.

New update:

Website 1: After it got crawled again: All dots, except the first crawler/cron (Guest, WebP, Mobile), are green!
Website 2: Not been crawled again yet since last update, but cache is still hit right now, after 2 days.
Website 3: After crawl, all dots, except the first crawler/cron (Guest, WebP, Mobile), are green. Update couple hours later: cache miss again. No purges in log…
Website 4: After crawl, all dots, except the first crawler/cron (Guest, WebP, Mobile), are green!

I was excited this morning to see all the green dots at the crawler meaning the cache survived until the next crawl. Yet all my excitement vanished a couple hours later when the cache was miss again at one of the websites. I will monitor it for a couple more days to be sure.

It looks like the issue is still there unfortunately. After several days of checking every day, it looks like it did kind of improve, because I have seen the crawler green dots more often. But there are still times where all the dots are blue – or cache miss after crawl. Purge logs from more than 10 days: no purges other than wp-login.

Maybe it’s dumb, but; could me working on a website (making updates, purges in lscache, etc.) in the same hosting, same user, have any effect on the cache of another website on this server? (no resource limits hit in the hosting).

Is there anything else I can try?