Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Had FlyWheel support verify they rebooted the instance after clearing and it has settled down, no more cron jobs generating. v2.0.3 does seem to fix this, just remember to reboot to kill any lingering process.

    So, this is odd. Even with the plugin completely disabled and moved out of the /plugins folder, cron jobs are still getting generated. Flywheel support had to temporarily cancel cronjobs so it’s not tanking website performance.

    Here’s the response from host support (DB truncated for privacy):

    Hi there Jeff, 
     
    Thanks for the follow-up. 
     
    We've tested running that 
    wp eval command as well as the OPTIMIZE TABLE wp_xxxxx_options SQL statement and even a DELETE FROM wp_xxxxx_options WHERE option_name = 'cron' AND option_value LIKE '%lc_twicedaily_refresh_req%';  statement to remove all of those crons but it seems they get regenerated immediately, even with the leadconnector plugin moved out of the /plugins folder.
     
    In this case you'll want to follow-up with the plugin authors to see if they have any suggestions on terminating these crons. Alternatively, you could try restoring a backup from before this issue arose and that should help get things stabilized. 
     

    I just ran into this yesterday. Our site dropped offline and troubleshooting identified the LeadConnector plugin had eaten all the instance memory. I had updated to v2.0 about a week ago, so not sure why it took so long for the issue to occur.

    We were able to update the plugin to the latest, but the performance issue persisted so I disabled the plugin, to no effect. Flywheel hosting support was able to identify the issue as the massive amount of cronjobs.

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