Problem with disabling preload

  • Resolved erik81

    (@erik81)


    3 years, 10 months ago

    wp 5.9.3
    wp-cloudflare-page-cache 4.6.1
    wp-multi-network

    I had problem with preload, probably is running per site and after restart 2 weeks ago, it’s overload server with lot of requests. I disable it but requests from localhost “POST wp-admin/admin-ajax.php?action=wp_swcfpc_cache_preloader_background_process” persist. I need comment main instance in libs/preloader.class.php. 

    root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220620.gz  | wc -l
87
root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220621.gz  | wc -l
45
root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220622.gz  | wc -l
26347
root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220623.gz  | wc -l
58601
root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220624.gz  | wc -l
86017
root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220625.gz  | wc -l
105195
root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220626.gz  | wc -l
117709
root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220627.gz  | wc -l
123248
root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220628.gz  | wc -l
145156
root@wpp:/var/log/nginx# zgrep "wp_swcfpc_cache_preloader_background_process" access.log-20220629.gz  | wc -l
145355
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    3 years, 10 months ago

    Huh! That seems wired. As if you have disabled preloaderinside the plugin settings i.e. https://i.imgur.com/19R4vWM.jpeg – it won’t run.

    Beside preloader is something I never recommend running if you have a big and good traffic site. It is mainly for small sites which doesn’t get much visitor and it is also very resource intensive as it uses cURL.

    So, if you have disabled the preloader from the plugin settings check if you have any cronjob set that might be triggering the preloader.

    Finally also just do enable/disable page caching form inside the plugin settings page.

    Thread Starter erik81

    (@erik81)

    3 years, 10 months ago

    I disabled preloader (this remove get /autor/feed requests) and disk cache over gui, but didn’t resolve problem.

    I look into cron and I found there is swcfpc_purge_cache_cron_interval, but it’s related to disabled disk cache. cf_disable_cache_purging_queue is 1 and i did’t find purge_cache_queue_start_cronjob string in logs.

    Plugin Contributor iSaumya

    (@isaumya)

    3 years, 10 months ago

    Have you tried disabling and deleting the plugin complete via wp-admin and then adding it as fresh? Does that solve the issue?

    Thread Starter erik81

    (@erik81)

    3 years, 10 months ago

    I tried disable plugin and update it from 4.5.X to 4.6.1, but doesn’t help.

    Plugin Contributor iSaumya

    (@isaumya)

    3 years, 10 months ago

    I honestly have no idea how the background process can be running if preloader is turned off in the plugin settings and you have not set preload via cronjob.

    Also when you turn on the preloader option inside the list of sitemaps to mention – that section is blank right? I mean nothing is there and then you have disabled preloader?

    Honestly, I don’t know what I am saying… I’ve checked the code multiple times and see no way of this being possible while preloader is off in the plugin settings.

    Thread Starter erik81

    (@erik81)

    3 years, 10 months ago

    I disable option as you requested:
    from “cf_preloader_nav_menus\”;a:2:{i:0;s:1:\”2\”;i:1;s:1:\”3\”;}” to “cf_preloader_nav_menus\”;a:0:{}”

    from “cf_preloader_start_on_purge\”;s:1:\”1\” to “cf_preloader_start_on_purge\”;s:1:\”0\”

    from “cf_preload_last_urls\”;s:1:\”1\” to “cf_preload_last_urls\”;s:1:\”0\”

    The problem persists.

    I found that POST request loop is begin only when site is accessed.

    I try to revert back developer instance to last functional state and “problem” is in DB (php files are same). I found only relevant difference in table wp_612_options :

    —ok system:
    swcfpc_preloader_lock 0
    —problem system:
    swcfpc_preloader_lock 1656681270

    ---ok system:
swcfpc_fc_ttl_registry  a:13:{s:45:"2a4daf02ee401d39b073bf19998168e82a8d91cb.html";i:0;s:45:"5ed00a8580dec03034cc38b774928e40337f50df.html";i:0;s:45:"1025099994c316d2165ee5d2868aa0900bb26362.html";i:0;s:45:"2659565867cb2c65d5c33aab1e2963c6aebdc271.html";i:0;s:45:"a10b514ebc3770eaecf8108619cb396d1e3c2fc1.html";i:0;s:45:"21b3ec0d77afacfe7a86c1a1d315ff25591fd7a4.html";i:0;s:45:"ce613673f5be96b9b9355d0060765f96e1937c4e.html";i:0;s:45:"5f86fb506fcef17549bf94e6b76a7c88810855a4.html";i:0;s:45:"e56c377d40761c4182f721ecdab0154a66e2fe39.html";i:0;s:45:"9800a7e4116ea70476bf1b6302f9213025917157.html";i:0;s:45:"237257eddfa644d6333f1108cfe166164bea302d.html";i:0;s:45:"7657e16365bff669943dc7cffa8099fea8637efe.html";i:0;s:45:"e575dccc71140754dd85beda5965b6a358150309.html";i:0;}
---problem system:
swcfpc_fc_ttl_registry  a:13:{s:45:"2a4daf02ee401d39b073bf19998168e82a8d91cb.html";i:0;s:45:"5ed00a8580dec03034cc38b774928e40337f50df.html";i:0;s:45:"1025099994c316d2165ee5d2868aa0900bb26362.html";i:0;s:45:"2659565867cb2c65d5c33aab1e2963c6aebdc271.html";i:0;s:45:"a10b514ebc3770eaecf8108619cb396d1e3c2fc1.html";i:0;s:45:"21b3ec0d77afacfe7a86c1a1d315ff25591fd7a4.html";i:0;s:45:"ce613673f5be96b9b9355d0060765f96e1937c4e.html";i:0;s:45:"5f86fb506fcef17549bf94e6b76a7c88810855a4.html";i:0;s:45:"9800a7e4116ea70476bf1b6302f9213025917157.html";i:0;s:45:"237257eddfa644d6333f1108cfe166164bea302d.html";i:0;s:45:"7657e16365bff669943dc7cffa8099fea8637efe.html";i:0;s:45:"e56c377d40761c4182f721ecdab0154a66e2fe39.html";i:0;s:45:"e575dccc71140754dd85beda5965b6a358150309.html";i:0;}
    Plugin Contributor iSaumya

    (@isaumya)

    3 years, 10 months ago

    The swcfpc_preloader_lock will only invoke when the preloader is enabled in the plugin settings. If the preloader is off in the plugin settings then this should not invoke.

    Thread Starter erik81

    (@erik81)

    3 years, 10 months ago

    It looks like the problem is fixed, with :

    update wp_612_options set option_value = ‘0’ where option_name = ‘swcfpc_preloader_lock’;

    Thank you for your help and your time.

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

The topic ‘Problem with disabling preload’ is closed to new replies.