• Resolved SLV

    (@dwnl)


    Hello,

    This file: /private_html/wp-cron.php uses 90-100% of my server CPU. action_scheduler_run_queue [ “WP Cron” ] ActionScheduler_QueueRunner->run() Every minute.

    I do not know how to fix this…

    I have deactivated all plugins and activated the standard Twenty Twenty-Four theme.
    Result: no diverence.

    I added: define(‘DISABLE_WP_CRON’, true); to the wp-config.php
    added: wget -q -O – https://###/wp-cron.php?doing_wp_cron >/dev/null 2>&1 on the server.
    Result: no diverence.

    Can anybody help me please?

    ### wp-core ###
    
    version: 6.4.2
    site_language: nl_NL
    user_language: nl_NL
    timezone: Europe/Amsterdam
    permalink: /%postname%/
    https_status: true
    multisite: false
    user_registration: 0
    blog_public: 1
    default_comment_status: closed
    environment_type: production
    user_count: 660
    dotorg_communication: true
    
    ### wp-paths-sizes ###
    
    wordpress_path: /home/###/domains/###.nl/public_html
    wordpress_size: 92,13 MB (96600847 bytes)
    uploads_path: /home/###/domains/###.nl/public_html/wp-content/uploads
    uploads_size: 2,81 GB (3016602109 bytes)
    themes_path: /home/###/domains/###.nl/public_html/wp-content/themes
    themes_size: 54,35 MB (56989663 bytes)
    plugins_path: /home/###/domains/###.nl/public_html/wp-content/plugins
    plugins_size: 268,28 MB (281309730 bytes)
    database_size: 540,33 MB (566575104 bytes)
    total_size: 3,74 GB (4018077453 bytes)
    
    ### wp-dropins (1) ###
    
    object-cache.php: true
    
    ### wp-active-theme ###
    
    name: Electro Child (electro-child)
    version: 2.3.3
    author: MadrasThemes
    author_website: https://madrasthemes.com/
    parent_theme: Electro (electro)
    theme_features: core-block-patterns, post-thumbnails, automatic-feed-links, html5, custom-background, site-logo, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, title-tag, post-formats, custom-logo, menus, widgets
    theme_path: /home/###/domains/###.nl/public_html/wp-content/themes/electro-child
    
    ### wp-parent-theme ###
    
    name: Electro (electro)
    version: 3.3.15
    author: MadrasThemes
    author_website: https://madrasthemes.com/
    theme_path: /home/###/domains/###.nl/public_html/wp-content/themes/electro
    
    ### wp-themes-inactive (1) ###
    
    Twenty Twenty-Four: version: 1.0, author: the WordPress team
    
    ### wp-mu-plugins (1) ###
    
    WordPress automation by Installatron: author: (undefined), version: (undefined)
    
    ### wp-plugins-active (45) ###
    
    Advanced AJAX Product Filters for WooCommerce: version: 1.6.4.6, author: BeRocket
    Advanced Woo Labels: version: 1.85, author: ILLID
    Advanced Woo Search: version: 2.98, author: ILLID
    Booster Plus for WooCommerce: version: 7.1.5, author: Pluggabl LLC
    Code Snippets: version: 3.6.2, author: Code Snippets Pro
    Complianz | GDPR/CCPA Cookie Consent: version: 6.5.6, author: Really Simple Plugins
    Conditional Shipping for WooCommerce: version: 3.1.3, author: Lauri Karisola / WP Trio
    Electro Extensions: version: 3.3.15, author: MadrasThemes
    Elementor: version: 3.18.3, author: Elementor.com
    Envato Market: version: 2.0.11, author: Envato
    Facebook for WooCommerce: version: 3.1.9, author: Facebook
    Google Language Translator: version: 6.0.20, author: Translate AI Multilingual Solutions
    GTM4WP: version: 1.19.1, author: Thomas Geiger
    Kadence WooCommerce Email Designer: version: 1.5.12, author: Kadence WP
    Limit Login Attempts Reloaded: version: 2.25.29, author: Limit Login Attempts Reloaded
    LiteSpeed Cache: version: 6.0.0.1, author: LiteSpeed Technologies
    Loco Translate: version: 2.6.6, author: Tim Whitlock
    Mailchimp for WooCommerce: version: 3.6, author: Mailchimp
    Mail logging - WP Mail Catcher: version: 2.1.7, author: James Ward
    MAS Static Content: version: 1.0.6, author: MadrasThemes
    MC4WP: Mailchimp for WordPress: version: 4.9.11, author: ibericode
    Min Max Quantity & Step Control for WooCommerce: version: 6.1, author: CodeAstrology Team
    OMGF: version: 5.7.13, author: Daan from Daan.dev
    Pay. Payment Methods for WooCommerce: version: 3.18.2, author: Pay.
    Product Feed Manager for WooCommerce: version: 7.3.26, author: RexTheme
    Product Feed Manager for WooCommerce PRO: version: 6.4.10, author: RexTheme
    Redux Framework: version: 4.4.11, author: Team Redux
    Related Products for WooCommerce: version: 1.5.2, author: WebToffee
    Replace Image: version: 1.1.8, author: WP Zone
    Trusted Shops Easy Integration for WooCommerce: version: 2.0.0, author: vendidero
    User Roles and Capabilities: version: 1.2.6, author: mahabub
    Variation Swatches for WooCommerce: version: 2.0.30, author: Emran Ahmed
    Variation Swatches for WooCommerce - Pro: version: 2.0.30, author: Emran Ahmed
    WooCommerce: version: 8.5.2, author: Automattic
    WooCommerce Deposits: version: 4.3.3, author: Webtomizer
    WooCommerce Sale Category: version: 0.2, author: Webikon (Juraj Kiss)
    Woo Custom Stock Status: version: 1.4.3, author: Softound Solutions
    Woo Custom Stock Status Pro: version: 1.0.7, author: Softound Solutions (latest version: 1.0.7)
    WooMultistore: version: 5.2.6, author: Lykke Media AS
    WPC Composite Products for WooCommerce: version: 7.2.0, author: WPClever
    WP Crontrol: version: 1.16.1, author: John Blackbourn & crontributors
    WPForms Lite: version: 1.8.6.3, author: WPForms
    YITH WooCommerce Badge Management: version: 3.3.0, author: YITH
    YITH WooCommerce Product Add-ons & Extra Options: version: 4.5.0, author: YITH
    Yoast SEO: version: 21.9.1, author: Team Yoast
    
    ### wp-plugins-inactive (1) ###
    
    Discount Rules and Dynamic Pricing for WooCommerce: version: 8.4.0, author: Discount Team
    
    ### code-snippets (17) ###
    
    snippet-21: name: disable the default payment option and shipping option on the "view cart", scope: global, modified: 2024-01-19 09:09:27
    snippet-24: name: Vanaf 99,95 ipv 99,95 - 112,25, scope: global, modified: 2021-03-25 10:02:33
    snippet-31: name: Aanbetaling vanaf €500, scope: global, modified: 2024-01-19 09:16:20
    snippet-38: name: Levertijden op categorie pagina's, scope: global, modified: 2022-02-08 14:22:49
    snippet-41: name: Nieuwe bestelmelding opnieuw naar klant versturen als nieuwe bestelactie, scope: global, modified: 2023-09-21 07:48:43
    snippet-43: name: + meer varianten op categorie pagina's, scope: global, modified: 2022-02-15 10:29:59
    snippet-47: name: Niet laten syncen door Multistore, scope: global, modified: 2023-11-14 10:12:48
    snippet-50: name: Producten filteren op tags, scope: global, modified: 2024-01-19 09:22:36
    snippet-51: name: Reguliere en sale prijzen in de winkelwagen, scope: global, modified: 2024-01-19 09:31:55
    snippet-52: name: Reguliere en sale prijzen in betalen, scope: global, modified: 2024-01-05 09:19:30
    snippet-54: name: Ook submenus op mobiel, scope: global, modified: 2024-01-19 09:33:21
    snippet-59: name: Onbeschikbare swatches wel blurren, scope: global, modified: 2024-01-19 09:37:24
    snippet-62: name: Update Cart Automatically on Quantity Change, scope: global, modified: 2023-01-06 20:03:43
    snippet-65: name: Hide shipping rates when free shipping is available, but keep "Local pickup" , scope: global, modified: 2023-02-03 13:20:36
    snippet-66: name: Auto Add Image Attributes From Image Filename , scope: global, modified: 2023-02-06 12:21:29
    snippet-72: name: PHP Warning: Trying to access array offset on value of type bool 1610, 1611, 1612, 1613, 1622, scope: global, modified: 2024-01-19 10:12:38
    snippet-76: name: 5% afhaalkorting AI, scope: global, modified: 2024-01-20 08:40:32
    
    ### wp-media ###
    
    image_editor: WP_Image_Editor_Imagick
    imagick_module_version: 1809
    imagemagick_version: ImageMagick 7.1.1-25 Q16-HDRI x86_64 054b98c80:20231230 https://imagemagick.org
    imagick_version: 3.7.0
    file_uploads: 1
    post_max_size: 256M
    upload_max_filesize: 128M
    max_effective_size: 128 MB
    max_file_uploads: 20
    imagick_limits: 
    	imagick::RESOURCETYPE_AREA: 14 GB
    	imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
    	imagick::RESOURCETYPE_FILE: 491512
    	imagick::RESOURCETYPE_MAP: 7 GB
    	imagick::RESOURCETYPE_MEMORY: 4 GB
    	imagick::RESOURCETYPE_THREAD: 1
    	imagick::RESOURCETYPE_TIME: 0
    imagemagick_file_formats: 3FR, 3G2, 3GP, A, AAI, AI, APNG, ART, ARW, ASHLAR, AVI, AVS, B, BAYER, BAYERA, BGR, BGRA, BGRO, BMP, BMP2, BMP3, BRF, C, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUBE, CUR, CUT, DATA, DCM, DCR, DCRAW, DCX, DDS, DFONT, DNG, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, FARBFELD, FAX, FF, FILE, FITS, FL32, FLV, FRACTAL, FTP, FTS, FTXT, G, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, HALD, HDR, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, JNG, JNX, JPE, JPEG, JPG, JPS, JSON, K, K25, KDC, LABEL, M, M2V, M4V, MAC, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPEG, MPG, MPO, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, O, ORA, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PHM, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PS, PS2, PS3, PSB, PSD, PTIF, PWP, QOI, R, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGB565, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCREENSHOT, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, STRIMG, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TM2, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMV, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, Y, YAML, YCbCr, YCbCrA, YUV
    gd_version: bundled (2.1.0 compatible)
    gd_formats: GIF, JPEG, PNG, WebP, BMP
    ghostscript_version: unknown
    
    ### wp-server ###
    
    server_architecture: Linux 4.18.0-477.27.2.el8_8.x86_64 x86_64
    httpd_software: LiteSpeed
    php_version: 8.1.27 64bit
    php_sapi: litespeed
    max_input_variables: 10000
    time_limit: 600
    memory_limit: 1024M
    max_input_time: 1000
    upload_max_filesize: 128M
    php_post_max_size: 256M
    curl_version: 7.61.1 OpenSSL/1.1.1k
    suhosin: false
    imagick_availability: true
    pretty_permalinks: true
    htaccess_extra_rules: true
    current: 2024-01-26T09:40:27+00:00
    utc-time: Friday, 26-Jan-24 09:40:27 UTC
    server-time: 2024-01-26T10:40:13+01:00
    
    ### wp-database ###
    
    extension: mysqli
    server_version: 10.6.16-MariaDB
    client_version: mysqlnd 8.1.27
    max_allowed_packet: 67108864
    max_connections: 151
    
    ### wp-constants ###
    
    WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /home/###/domains/###.nl/public_html/wp-content
    WP_PLUGIN_DIR: /home/###/domains/###.nl/public_html/wp-content/plugins
    WP_MEMORY_LIMIT: 40M
    WP_MAX_MEMORY_LIMIT: 1024M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: true
    WP_DEBUG_LOG: false
    SCRIPT_DEBUG: false
    WP_CACHE: true
    CONCATENATE_SCRIPTS: undefined
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_ENVIRONMENT_TYPE: Ongedefinieerd
    WP_DEVELOPMENT_MODE: undefined
    DB_CHARSET: utf8
    DB_COLLATE: undefined
    
    ### wp-filesystem ###
    
    wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable
    mu-plugins: writable
    0: Writable
    
    ### redux-framework ###
    
    version: 4.4.11
    installation: plugin
    data directory: /home/###/domains/###.nl/public_html/wp-content/plugins/redux-framework/redux-core/
    browser: 
    	Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
    	Browser: Chrome
    	Version: 120.0.0.0
    	Platform: Windows
    
    ### redux-instance-electro_options ###
    
    opt_name: electro_options
    global_variable: electro_options
    dev_mode: false
    ajax_save: true
    page_slug: theme_options
    page_permissions: manage_options
    menu_type: menu
    page_parent: themes.php
    compiler: true
    output: true
    output_tag: true
    templates_path: undefined
    extensions: 
    	Accordion: 4.3.16
    	Custom Fonts: 4.4.2
    	Customizer: 4.4.11
    	Datetime: 4.3.15
    	Google Maps: 4.4.0
    	Icon Select: 4.4.2
    	Import Export: 4.0.0
    	Js Button: 4.3.16
    	Metaboxes: 4.2.0
    	Multi Media: 4.4.1
    	Options Object: 4.0.0
    	Repeater: 4.3.13
    	Search: 3.4.5
    	Shortcodes: 4.3.6
    	Social Profiles: 4.3.17
    	Tabbed: 4.4.8
    	Taxonomy: 4.4.6
    	Users: 4.4.1
    	Widget Areas: 4.3.20
    
    ### wpforms ###
    
    version: 1.8.6.3
    lite: 21 april 2023 op 07:55
    upload_dir: Beschrijfbaar
    total_forms: 1
    total_submissions: 132
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support anastas10s (woo-hc)

    (@anastas10s)

    Hi there @dwnl 👋

    Thanks for reaching out about this. Let’s troubleshoot it together!

    This file: /private_html/wp-cron.php uses 90-100% of my server CPU. action_scheduler_run_queue [ “WP Cron” ] ActionScheduler_QueueRunner->run() Every minute.

    From what I gather, the reported issue is to do with Cron jobs at the site.

    Just to clarify, did this start happening recently (after a theme/plugin update, perhaps), or otherwise?

    Among the active plugins, WP Crontrol can be found. Did you already have a chance to utilize it for editing the timings of said cron jobs, and see if the server resource usage changes, or otherwise?

    Moreover, I’d recommend considering replacing WordPress cron with a real cron job.

    I hope this is helpful! Please let us know if you have any further questions or concerns.
    We will be happy to help you further.

    Thread Starter SLV

    (@dwnl)

    “Just to clarify, did this start happening recently (after a theme/plugin update, perhaps), or otherwise?”

    I don’t know really… yesterday everything was fine and this morning the shop would not load, and I got the error:

    Request Timeout
    This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase ‘Connection Timeout’.


    Maybe the problem is active longer? But I noticed only this morning?
    My hosting pointed me to the /private_html/wp-cron.php.

    Among the active plugins, WP Crontrol can be found. Did you already have a chance to utilize it for editing the timings of said cron jobs, and see if the server resource usage changes, or otherwise?
    I am sorry, I don’t know what you mean with this… Can you explain more?

    I already did this: replacing WordPress cron with a real cron job. It does not have any effect.

    • This reply was modified 5 months, 3 weeks ago by SLV.
    Thread Starter SLV

    (@dwnl)

    This is what is in the wp-cron.php file btw:

    <?php
    /**
     * A pseudo-cron daemon for scheduling WordPress tasks.
     *
     * WP-Cron is triggered when the site receives a visit. In the scenario
     * where a site may not receive enough visits to execute scheduled tasks
     * in a timely manner, this file can be called directly or via a server
     * cron daemon for X number of times.
     *
     * Defining DISABLE_WP_CRON as true and calling this file directly are
     * mutually exclusive and the latter does not rely on the former to work.
     *
     * The HTTP request to this file will not slow down the visitor who happens to
     * visit when a scheduled cron event runs.
     *
     * @package WordPress
     */
    
    ignore_user_abort( true );
    
    if ( ! headers_sent() ) {
    	header( 'Expires: Wed, 11 Jan 1984 05:00:00 GMT' );
    	header( 'Cache-Control: no-cache, must-revalidate, max-age=0' );
    }
    
    // Don't run cron until the request finishes, if possible.
    if ( PHP_VERSION_ID >= 70016 && function_exists( 'fastcgi_finish_request' ) ) {
    	fastcgi_finish_request();
    } elseif ( function_exists( 'litespeed_finish_request' ) ) {
    	litespeed_finish_request();
    }
    
    if ( ! empty( $_POST ) || defined( 'DOING_AJAX' ) || defined( 'DOING_CRON' ) ) {
    	die();
    }
    
    /**
     * Tell WordPress the cron task is running.
     *
     * @var bool
     */
    define( 'DOING_CRON', true );
    
    if ( ! defined( 'ABSPATH' ) ) {
    	/** Set up WordPress environment */
    	require_once __DIR__ . '/wp-load.php';
    }
    
    // Attempt to raise the PHP memory limit for cron event processing.
    wp_raise_memory_limit( 'cron' );
    
    /**
     * Retrieves the cron lock.
     *
     * Returns the uncached doing_cron transient.
     *
     * @ignore
     * @since 3.3.0
     *
     * @global wpdb $wpdb WordPress database abstraction object.
     *
     * @return string|int|false Value of the doing_cron transient, 0|false otherwise.
     */
    function _get_cron_lock() {
    	global $wpdb;
    
    	$value = 0;
    	if ( wp_using_ext_object_cache() ) {
    		/*
    		 * Skip local cache and force re-fetch of doing_cron transient
    		 * in case another process updated the cache.
    		 */
    		$value = wp_cache_get( 'doing_cron', 'transient', true );
    	} else {
    		$row = $wpdb->get_row( $wpdb->prepare( "SELECT option_value FROM $wpdb->options WHERE option_name = %s LIMIT 1", '_transient_doing_cron' ) );
    		if ( is_object( $row ) ) {
    			$value = $row->option_value;
    		}
    	}
    
    	return $value;
    }
    
    $crons = wp_get_ready_cron_jobs();
    if ( empty( $crons ) ) {
    	die();
    }
    
    $gmt_time = microtime( true );
    
    // The cron lock: a unix timestamp from when the cron was spawned.
    $doing_cron_transient = get_transient( 'doing_cron' );
    
    // Use global $doing_wp_cron lock, otherwise use the GET lock. If no lock, try to grab a new lock.
    if ( empty( $doing_wp_cron ) ) {
    	if ( empty( $_GET['doing_wp_cron'] ) ) {
    		// Called from external script/job. Try setting a lock.
    		if ( $doing_cron_transient && ( $doing_cron_transient + WP_CRON_LOCK_TIMEOUT > $gmt_time ) ) {
    			return;
    		}
    		$doing_wp_cron        = sprintf( '%.22F', microtime( true ) );
    		$doing_cron_transient = $doing_wp_cron;
    		set_transient( 'doing_cron', $doing_wp_cron );
    	} else {
    		$doing_wp_cron = $_GET['doing_wp_cron'];
    	}
    }
    
    /*
     * The cron lock (a unix timestamp set when the cron was spawned),
     * must match $doing_wp_cron (the "key").
     */
    if ( $doing_cron_transient !== $doing_wp_cron ) {
    	return;
    }
    
    foreach ( $crons as $timestamp => $cronhooks ) {
    	if ( $timestamp > $gmt_time ) {
    		break;
    	}
    
    	foreach ( $cronhooks as $hook => $keys ) {
    
    		foreach ( $keys as $k => $v ) {
    
    			$schedule = $v['schedule'];
    
    			if ( $schedule ) {
    				$result = wp_reschedule_event( $timestamp, $schedule, $hook, $v['args'], true );
    
    				if ( is_wp_error( $result ) ) {
    					error_log(
    						sprintf(
    							/* translators: 1: Hook name, 2: Error code, 3: Error message, 4: Event data. */
    							__( 'Cron reschedule event error for hook: %1$s, Error code: %2$s, Error message: %3$s, Data: %4$s' ),
    							$hook,
    							$result->get_error_code(),
    							$result->get_error_message(),
    							wp_json_encode( $v )
    						)
    					);
    
    					/**
    					 * Fires when an error happens rescheduling a cron event.
    					 *
    					 * @since 6.1.0
    					 *
    					 * @param WP_Error $result The WP_Error object.
    					 * @param string   $hook   Action hook to execute when the event is run.
    					 * @param array    $v      Event data.
    					 */
    					do_action( 'cron_reschedule_event_error', $result, $hook, $v );
    				}
    			}
    
    			$result = wp_unschedule_event( $timestamp, $hook, $v['args'], true );
    
    			if ( is_wp_error( $result ) ) {
    				error_log(
    					sprintf(
    						/* translators: 1: Hook name, 2: Error code, 3: Error message, 4: Event data. */
    						__( 'Cron unschedule event error for hook: %1$s, Error code: %2$s, Error message: %3$s, Data: %4$s' ),
    						$hook,
    						$result->get_error_code(),
    						$result->get_error_message(),
    						wp_json_encode( $v )
    					)
    				);
    
    				/**
    				 * Fires when an error happens unscheduling a cron event.
    				 *
    				 * @since 6.1.0
    				 *
    				 * @param WP_Error $result The WP_Error object.
    				 * @param string   $hook   Action hook to execute when the event is run.
    				 * @param array    $v      Event data.
    				 */
    				do_action( 'cron_unschedule_event_error', $result, $hook, $v );
    			}
    
    			/**
    			 * Fires scheduled events.
    			 *
    			 * @ignore
    			 * @since 2.1.0
    			 *
    			 * @param string $hook Name of the hook that was scheduled to be fired.
    			 * @param array  $args The arguments to be passed to the hook.
    			 */
    			do_action_ref_array( $hook, $v['args'] );
    
    			// If the hook ran too long and another cron process stole the lock, quit.
    			if ( _get_cron_lock() !== $doing_wp_cron ) {
    				return;
    			}
    		}
    	}
    }
    
    if ( _get_cron_lock() === $doing_wp_cron ) {
    	delete_transient( 'doing_cron' );
    }
    
    die();
    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @dwnl, thank you for sharing the code above.

    The code is the standard wp-cron.php file that comes with every WordPress installation.

    In order to be able to troubleshoot the issue further, could you reach out to your host and ask to have any server logs that are generated from your site?

    You can then paste them in your reply here.

    Thread Starter SLV

    (@dwnl)

    (@ckadenge) What logs do you need?

    Plugin Support anastas10s (woo-hc)

    (@anastas10s)

    Hi there 👋

    I don’t know really… yesterday everything was fine and this morning the shop would not load, and I got the error:

    Request Timeout
    This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase ‘Connection Timeout’.

    Just to clarify, there is no record of plugin/theme code being updated, from when everything was fine until the issue occurred?

    Moreover, did you already have a chance to create a staging/clone of the site, for testing, with only the WooCommerce plugin active, or otherwise?

    Could you please provide us with a screenshot so that we can see what you are describing?

    If you don’t already have a screenshot service installed, here are a few free options:

    https://snipboard.io
    http://skitch.com/
    http://getcloudapp.com/
    http://awesomescreenshot.com/

    There is also a walkthrough guide here: https://en.support.wordpress.com/make-a-screenshot/

    ### wp-server ###
    
    max_input_variables: 10000
    time_limit: 600
    memory_limit: 1024M
    max_input_time: 1000
    upload_max_filesize: 128M
    php_post_max_size: 256M

    By the way, did you already have a chance to edit these settings, to higher ones, and see if the issue persists (preferably on a staging site), or otherwise?

    I am sorry, I don’t know what you mean with this… Can you explain more?

    As the WP Crontrol has its own settings, I was wondering if any of the Cron jobs were edited using it.

    What logs do you need?

    The WordPress Error Logs, to Detect Issues, as detailed here.

    I trust that points you in the right direction, but if you have more questions, let us know.

    We’re happy to help.

    Thread Starter SLV

    (@dwnl)

    The hosting says there have been many times lately that the system load is maxed out for a few moments.
    It has to do with: /private_html/index.php and /private_html/wp-cron.php

    But last Friday, I think I updated the WooCommerce plugin to version 8.5.2, and after that the whole webshop did not function anymore. This was the first time this ever happened…

    In WP Crontrol Cron jobs were deleted after noting else had worked…
    So my hosting had to put back a backup from my webshop, and now I have Woocommerce plugin to version 8.5.1 and the problem with the wp-cron.php seems to be gone…
    So I can not provide you with a screenshot.
    And I do not dare to update that Woocommerce plugin again on my live webshop.

    The settings were already:
    max_execution_time 600
    max_input_time 1000
    max_input_vars 10000
    memory_limit 1024M
    upload_max_filesize 128M

    Time_limit: 600 does not exist…

    I do not have the change to make a staging/clone of this shop right now…
    My hosting package is too small for another clone at this moment.
    The error log does not go back so far, but at that time there were no errors in it.

    • This reply was modified 5 months, 3 weeks ago by SLV.
    Plugin Support Shameem (woo-hc)

    (@shameemreza)

    Hi @dwnl,

    It’s good to hear that reverting to version 8.5.1 resolved the problem with wp-cron.php.

    However, have you had a chance to disable the Order Attribution feature? You can find it under WooCommerce > Settings > Advanced > Features. After disabling it, check if it resolves the issue.

    Rest assured, I’ve tried to replicate the issue on my hosting account, which has a very low configuration with more than 1000 demo products. But I couldn’t find any issues – everything appears to be working fine on my end.

    Let us know how that goes. Looking forward to helping you.

    Thread Starter SLV

    (@dwnl)

    The problem has magically disappeared…
    Some days ago, I reverted the WooCommerce plugin to version 8.5.1.
    Today I updated it again to 8.5.2 and the problem seems to be gone.

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @dwnl,

    Glad to hear it – thanks for letting us know!

    If you have a few minutes, we’d love if you could leave us a review: https://wordpress.org/support/plugin/woocommerce/reviews/

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.