wp_cache_postload: backend detected, not running

  • Resolved juutmuijs

    (@juutmuijs)


    9 months ago

    I have searched, but can not find the answer, I am also a noob, so please have some patience with me. WP Super Cache is not caching pages, it comes up 0 or 1 page. When using debug mode, the following comes up, and I can not find the answer to solve it. Please help me out, any guidance is appreciated.

    09:57:36 4050942 /wp-cron.php?doing_wp_cron=1709200656.5915200710296630859375 wp_cache_postload: backend detected, not running
    09:58:07 4057043 /wp-cron.php?doing_wp_cron=1709200687.6882710456848144531250 wp_cache_postload: backend detected, not running
    09:59:22 4063221 /wp-cron.php?doing_wp_cron=1709200762.9151830673217773437500 wp_cache_postload: backend detected, not running
    10:00:22 4067697 /wp-cron.php?doing_wp_cron=1709200822.1279110908508300781250 wp_cache_postload: backend detected, not running
    10:01:24 4068799 /wp-cron.php?doing_wp_cron=1709200884.0949800014495849609375 wp_cache_postload: backend detected, not running
    10:02:25 4078673 /wp-cron.php?doing_wp_cron=1709200945.0685660839080810546875 wp_cache_postload: backend detected, not running
    10:04:05 4080533 /wp-cron.php?doing_wp_cron=1709201045.4372611045837402343750 wp_cache_postload: backend detected, not running
    10:05:06 4081596 /wp-cron.php?doing_wp_cron=1709201105.9553949832916259765625 wp_cache_postload: backend detected, not running
    10:07:06 4084852 /wp-cron.php?doing_wp_cron=1709201226.8523290157318115234375 wp_cache_postload: backend detected, not running
    10:09:08 4087086 /wp-cron.php?doing_wp_cron=1709201348.2506430149078369140625 wp_cache_postload: backend detected, not running
    10:09:08 4087086 /wp-cron.php?doing_wp_cron=1709201348.2506430149078369140625 maybe_stop_gc: GC flag not found. GC will go ahead..
    10:09:08 4087086 /wp-cron.php?doing_wp_cron=1709201348.2506430149078369140625 wp_cache_gc_cron: Set GC Flag. (ABSPATH/wp-content/cache/stepbystepdiyseo.com_wp_cache_gc.txt)
    10:09:08 4087086 /wp-cron.php?doing_wp_cron=1709201348.2506430149078369140625 Cache garbage collection.
    10:09:08 4087086 /wp-cron.php?doing_wp_cron=1709201348.2506430149078369140625 Cleaning expired cache files in ABSPATH/wp-content/cache/
    10:09:08 4087086 /wp-cron.php?doing_wp_cron=1709201348.2506430149078369140625 GC completed. GC flag deleted.
    10:09:08 4087086 /wp-cron.php?doing_wp_cron=1709201348.2506430149078369140625 scheduled wp_cache_gc for 10 seconds time.
    10:11:09 4089324 /wp-cron.php?doing_wp_cron=1709201469.1097409725189208984375 wp_cache_postload: backend detected, not running
    10:11:28 4089677 /wp-cron.php?doing_wp_cron=1709201488.3315949440002441406250 wp_cache_postload: backend detected, not running
    10:12:32 4090575 /wp-cron.php?doing_wp_cron=1709201552.4899199008941650390625 wp_cache_postload: backend detected, not running
    10:13:07 4091246 /wp-cron.php?doing_wp_cron=1709201587.4906270503997802734375 wp_cache_postload: backend detected, not running

Viewing 1 replies (of 1 total)
  • Plugin Author Donncha O Caoimh (a11n)

    (@donncha)

    /wp-cron.php is the jobs system. That isn’t supposed to be cached. Look at the logs when you load the front page of your site. Visit in a private window to make sure it’s caching.

Viewing 1 replies (of 1 total)
  • The topic ‘wp_cache_postload: backend detected, not running’ is closed to new replies.