V4 Beta Issue

Hello @andrewgchoi43

Thank you for the reporting. I just tried to reproduce this in our local test environment but didn’t see it happen. I set a system cron job to echo the current time and append to a file every minute. Set it up based on your description, define( ‘DISABLE_WP_CRON’, true); in the wp-config.php file, and turn on the Guest Mode in v4.0, the system cronjob still runs fine.

So the phenomena you mentioned may be related to some other factors? Please verify. Or maybe it’s related to what you exactly tried to do with the server level cron?

Best regards,
Abe

Hi,

I delete the Litespeed Cache’s option table after disable the plugin, and then re-enabling the plugin actually fixes the issue.

If I see the issue again I will let you know.

Thank you for your quick reply ??

Yeah. It still causes issue. It seems the cron jobs are working after deleting option table of litespeed_config, but cron jobs are slowly not working such as 1 min cron jobs become 5 min 10 min and so on.

Here is cron jobs one server It stops at 5 hrs ago:

+--------------------------------------+---------------------+-----------------------+---------------+
| hook                                 | next_run_gmt        | next_run_relative     | recurrence    |
+--------------------------------------+---------------------+-----------------------+---------------+
| action_scheduler_run_queue           | 2021-05-04 21:55:02 | now                   | 1 minute      |
| litespeed_task_ccss                  | 2021-05-04 21:55:20 | now                   | 1 minute      |
| litespeed_task_lqip                  | 2021-05-04 21:55:20 | now                   | 1 minute      |
| litespeed_task_avatar                | 2021-05-04 21:55:20 | now                   | 1 minute      |

In case if it is coming from server, I create the new site with only LSC is on. It stucks at 4 hrs ago.

+------------------------------------+---------------------+---------------------+---------------+
| hook                               | next_run_gmt        | next_run_relative   | recurrence    |
+------------------------------------+---------------------+---------------------+---------------+
| litespeed_task_imgoptm_pull        | 2021-05-04 22:40:40 | now                 | 1 minute      |
| litespeed_task_ccss                | 2021-05-04 22:40:40 | now                 | 1 minute      |
| litespeed_task_lqip                | 2021-05-04 22:40:40 | now                 | 1 minute      |
| wp_update_comment_type_batch       | 2021-05-04 22:40:50 | now                 | Non-repeating |
| wp_privacy_delete_old_export_files | 2021-05-04 23:39:06 | now                 | 1 hour        |

Before Beta 4.0, Cron jobs run without any issue, but it stops working whenever guest mode is turned on. It does not stop at once, but slowly turning off.

I will perform another test with completely different instance without any setup on the server, but I think this is definitely a bug.

Thank you

Upon testing on New VM with new fresh site, the cron job stop working whenever Guest Mode is on. I have tested with 3 different sites, and they all behave same way. After I stop Guest Mode > Disable Plugin (or delete litespeed_config option table) > enable plugin, cron starts running.

I have confirmed the following:

1. It is not a firewall (all firewalls have been disabled and New VM did not have firewall)
2. It is not plugin conflicts. (Tested on site with only Litespeed Cache is on)
3. It is not a Cyberpanel’s Cron Job issue. (I have added the cron job with command line into contacb -e. They still behave same way)

Thank you

The cron issue is confirmed in current v4 when you have Guest mode ON. It is caused bcos the wp-cron is cached. Disabling Guest Mode will fix it for now.

Will give the fix in one day. Will update here. Thanks for your feedback.

Thank you for the confirmation.

I found another issue. It might be because of the hook moved from plugin to init.

ESI Nonce does not work correctly after the update. I use wildcard with private such as:

wsf_* private
wp_* private
rcp_* private

It was working fine before update too.

Thank you

• This reply was modified 3 years, 10 months ago by andrewgchoi43.

Separate issue please create separate topic for easier discussion and fix.

Please also make the issue in title of the topic as accurate as possible for same concern.

Got it

This is fixed in latest dev branch. Please give it a try. Will update to master branch and WP later.

All places updated.

It works fine! Great Thank you ??