CRITICAL Maximum execution time of 30 seconds exceeded on

  • Resolved raha1988ab

    (@raha1988ab)


    11 months ago

    Hello

    Merry christmas

    I found many errors in error_log file in my cpanel host, and in WooCommerce status report

    I set these settings in my php.ini and .user.ini file, so this is not about my host configuration (this is not shared hosting, it’s dedicated server and there is only single site on it)

    [PHP]
display_errors = Off
max_execution_time = 300
max_input_time = 600
max_input_vars = 25000
memory_limit = 1G
post_max_size = 200M
session.gc_maxlifetime = 1440
session.save_path = "/var/cpanel/php/sessions/ea-php81"
upload_max_filesize = 200M
zlib.output_compression = Off
allow_url_fopen = On
enable_dl = Off
file_uploads = On

    wc-status&tabs=log

    2023-11-26T13:25:05+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-includes/class-wp-term-query.php on line 1178

2023-11-26T13:39:53+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T13:41:05+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T13:42:46+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T13:49:06+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T13:50:36+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T13:52:23+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object.lib.php on line 617

2023-11-26T13:55:05+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-includes/class-wpdb.php on line 2349

2023-11-26T13:57:22+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T14:03:12+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T14:05:10+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-includes/plugin.php on line 288

2023-11-26T14:05:15+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T14:09:21+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 579

2023-11-26T14:15:08+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T14:22:12+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T14:22:27+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T14:24:55+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T14:30:18+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 434

2023-11-26T14:31:45+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T14:45:01+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T14:54:01+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 434

2023-11-26T14:59:35+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object.lib.php on line 597

2023-11-26T15:00:05+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 604

2023-11-26T15:00:40+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T15:01:36+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 482

2023-11-26T19:35:53+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-includes/class-wpdb.php on line 2349

2023-11-26T19:50:52+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object.lib.php on line 805

2023-11-26T19:56:40+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-includes/formatting.php on line 1170

2023-11-26T20:05:00+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-includes/class-wpdb.php on line 2349

2023-11-26T20:07:59+00:00 CRITICAL Maximum execution time of 30 seconds exceeded on /home/site/public_html/wp-content/plugins/litespeed-cache/src/object.lib.php on line 812

    error_log file

    [25-Dec-2023 15:36:44 UTC] Cron reschedule event error for hook: litespeed_task_imgoptm_pull, Error code: could_not_set, The cron event list could not be saved. {"schedule":"litespeed_filter","args":[],"interval":60}

    Report number: NAJATPPM

    Report date:?12/27/2023 13:36:33

    Also it is not cache the pages at all, It shows the “cache: miss” I saw the youtube video and configured the plugin like that said in video

    I used the php snippet in my function.php file

    add_filter( 'litespeed_const_DONOTCACHEPAGE', '__return_false' );

    *Please don’t share my site name or reports of the domain address in public

    Thanks for all

    • This topic was modified 11 months ago by raha1988ab.
Viewing 15 replies - 1 through 15 (of 17 total)
  • Thread Starter raha1988ab

    (@raha1988ab)

    I found this code was in htaccess file, I removed the Litespeed cache plugin, I delete the table of this plugin form database, then installed,

    Also, I removed the htaccess file and from WordPress permalink created a new one, but LiteSpeed cache could not add the code in htaccess, so I found and changed that

    RewriteEngine On
RewriteRule .* - [E=Cache-Control:no-cache]

    and I changed to this:

    RewriteEngine On
RewriteRule ^(.*)$ - [E=Cache-Control:max-age=3600]

    now it cached the pages, but for the first time, it took too much to load the page, after the first try, it opened the page so fast

    this is just for caching, the error still remain I asked bout before,

    please cheek that

    Thanks

    Plugin Support qtwrk

    (@qtwrk)

    no , please don’t use that rule , that will unconditionally cache everything including wp-admin page, and give you no means to auto-purge

    it looks like you enabled object cache but without properly connect to it , so plugin is keep trying and trying and hit timeout , please try disable the object cache.

    Thread Starter raha1988ab

    (@raha1988ab)

    Okay, I remove that rules and turned off the object cache,

    Now it’s not hit, it just miss the cache

    What now?

    Thread Starter raha1988ab

    (@raha1988ab)

    The speed broken again…

    When those rules were added to the htaccess file, the Speed Index in Google Page Speed Insight was gone! but now I have removed that code, it appears

    I add it again until to find a way to hitting the cache

    Plugin Support qtwrk

    (@qtwrk)

    let’s try this , undo or revert all the manual change you have done

    then go to LiteSpeed Cache -> Toolbox -> Import/Export -> reset to default , see how thing goes on default setting.

    Thread Starter raha1988ab

    (@raha1988ab)

    I did, the hit not showing, it just show me the miss

    Plugin Support qtwrk

    (@qtwrk)

    please provide the report number after reset.

    Thread Starter raha1988ab

    (@raha1988ab)

    Report number: SLQWQFVG

    Report date: 12/28/2023 01:56:20

    Plugin Support qtwrk

    (@qtwrk)

    you put RewriteRule .* - [E=Cache-Control:no-cache] , this will mes up with plugin

    Thread Starter raha1988ab

    (@raha1988ab)

    I removed and now it hit the cache

    Why should I turn off the object cache? Does it not help me in this case?

    Thread Starter raha1988ab

    (@raha1988ab)

    Whit this :

    RewriteEngine On
RewriteRule ^(.*)$ - [E=Cache-Control:max-age=3600]

    Speed Index go to 1S and without this, the SI is 10s

    Thread Starter raha1988ab

    (@raha1988ab)

    Hi @qtwrk

    it looks like you enabled object cache but without properly connect to it , so plugin is keep trying and trying and hit timeout , please try disable the object cache.

    I need to activate the Object Cache in litespeed plugin, How should I solve that issue? is there any changes needed in my webserver?

    Plugin Support qtwrk

    (@qtwrk)

    the object cache needs the server-side to have a running Redis or Memcached, if you don’t have that and keep it enabled, it will slow thing down.

    Thread Starter raha1988ab

    (@raha1988ab)

    Memcache is enabled but it show that error

    Plugin Support qtwrk

    (@qtwrk)

    did it show “connection test passed” ?

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘CRITICAL Maximum execution time of 30 seconds exceeded on’ is closed to new replies.