• Resolved balticcharge

    (@balticcharge)


    Hi

    Very frequently, I believe it could be every ~1h (1h was the shortest amount of time I noticed that it loads all pages again) the cache is purged without any actions, scheduled actions or even without a trace in logs.

    After enabling logs with advanced debug level, there is nothing related in Debug log and purge log is completely empty (it populates with manual actions, but I’m clearing it before proceeding with test).

    – Site is currently in development and there is no traffic (and orders that could somehow triger purge).
    – TTLs are default, so for public pages 1 week
    – Auto-updated are disabled
    – Latest LiteSpeed cache plugin version

    This wasn’t a case with WP Fastest Cache, but I would really like to stick with LiteSpeed as it performs much better except this issue.

    Any ideas?

    • This topic was modified 1 year, 8 months ago by balticcharge.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter balticcharge

    (@balticcharge)

    Not sure if this is related with the described issues got one record in purge log

    09/15/24 18:29:16.272 [=CLI=balticch 1 mNR] X-LiteSpeed-Purge: public,004_Po.3971,004_URL./,004_W.recent-posts-1,004_FD,004_F,004_H,004_PGS,004_PGSRP,004_REST,004_Po.4230 => LiteSpeed\LSC->send_headers()@624 => WP_Hook->apply_filters(,ARRAY)@324 => WP_Hook->do_action(ARRAY)@348 =>
    /home4/balticch/public_html/wp-includes/load.php@517


    ID 4230 is autogenerated coupon code from WooCommerce Cart Abandonment Recovery. I will disable this and see if the issue persit.

    Thread Starter balticcharge

    (@balticcharge)

    It happened again, without any trace in logs.

    Plugin Support qtwrk

    (@qtwrk)

    please share the full log on 09/15/24 18:29:16.272 [=CLI=balticch 1 mNR]

    and it seems coming from a WP CLI , did you run wp cli for something ? like check update ?

    Thread Starter balticcharge

    (@balticcharge)

    Thanks @qtwrk.

    I was too lazy and didn’t check cache info in the bottom of page. So the problem was with Logged in users for Woocommerce (while website is closed for public, I didn’t test with guest user).

    As woocommerce customer is a logged in user, to them litespeed cache serves private cache where TTL is 30 minutes.

    To solve this I have enabled ESI and I will test it how it performs and caches, for example, minicart.

    Sorry for causing the trouble, but perhaps this info will help someone in the same situation in the future. Closing.

    Thanks

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Cache purged without intention’ is closed to new replies.