• Resolved jdwf0658

    (@jdwf0658)


    aiowps_hourly_cron_event when running gives a php memory limit error. How can I go about debugging this? I’ve tried increasing my memory limit multiple times to see if it would process but it still gets hung up.

    • This topic was modified 4 years, 7 months ago by jdwf0658.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, can you share the memory limit error message you receive?

    Thank you

    Thread Starter jdwf0658

    (@jdwf0658)

    Here is the due now cron list.

    
    action_scheduler_run_queue | 2020-04-01 17:30:13 | now | 1 minute
    wsal_detect_file_changes | 2020-04-01 17:30:15 | now | 10 minutes 
    smush_check_for_conflicts | 2020-04-01 17:30:29 | now | Non-repeating
    aiowps_hourly_cron_event | 2020-04-01 17:33:29 | now | 1 hour 
    

    Then this is during execution through CLI

    
    Executed the cron event 'action_scheduler_run_queue' in 0.463s.
    Executed the cron event 'wsal_detect_file_changes' in 0.031s.
    Executed the cron event 'smush_check_for_conflicts' in 0.097s.
    Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 16777224 bytes) in /public_html/wp-includes/wp-db.php on line 1996
    Error: There has been a critical error on your website.Learn more about debugging in WordPress. There has been a critical error on your website.
    

    I tried increasing memory limit in wp-config but couldn’t get it to execute fully.

    • This reply was modified 4 years, 7 months ago by jdwf0658.
    • This reply was modified 4 years, 7 months ago by jdwf0658.
    Thread Starter jdwf0658

    (@jdwf0658)

    Also if this helps the log files contain
    cron-log

    
    [2020-04-01 02:30:05] - SUCCESS : DB Backup - Scheduled backup is enabled. Checking if a backup needs to be done now...
    [2020-04-01 03:30:09] - SUCCESS : DB Backup - Scheduled backup is enabled. Checking if a backup needs to be done now...
    [2020-04-01 17:34:31] - SUCCESS : DB Backup - Scheduled backup is enabled. Checking if a backup needs to be done now...
    

    and normal log

    
    [2020-04-01 14:39:23] - NOTICE : The following IP address range has been locked out for exceeding the maximum login attempts: 150.95.55
    [2020-04-01 17:14:12] - NOTICE : The following IP address range has been locked out for exceeding the maximum login attempts: 186.64.118
    [2020-04-01 17:34:31] - SUCCESS : DB Backup - Deleting all but 2 latest backup file(s) in /public_html/wp-content/aiowps_backups directory.
    [2020-04-01 17:45:03] - NOTICE : The following IP address range has been locked out for exceeding the maximum login attempts: 153.92.6
    

    From looking at the code, I’m guessing it’s failing during the aiowps_perform_fcd_scan_tasks action? I manually cleaned the tables to 5,000 entries like suggested in the DB cleanup maintenance.

    EDIT: I disabled db backup and was able to get it to run completely. Still diving into the code but it’s failing somewhere in execute_backup(). I added more debug prints to find a more concise placement and it’s during the write to back up file function.

    • This reply was modified 4 years, 7 months ago by jdwf0658.
    Thread Starter jdwf0658

    (@jdwf0658)

    After further investigation its due to my wp_options table being too large.
    Working on cleaning this up, then it should perform as expected.
    After cleaning wp_options to only 300,000 bytes (bad mailer plugin that was deleted long ago made it almost 1,000,000 bytes). and my php limit set to 512M, you’d think it’d work?

    • This reply was modified 4 years, 7 months ago by jdwf0658.
    Thread Starter jdwf0658

    (@jdwf0658)

    Okay final tests, it runs out of memory while doing the wp_options table.
    these are the last lines it wrote (Note: my wp_options table is only 1743 total) size significantly smaller.

    
    [2020-04-01 21:15:07] - FAILURE : Writing table row: 3434909 in _transient_timeout_aiowps_captcha_string_info_9xrpb3y990
    [2020-04-01 21:15:07] - FAILURE : Writing table row: 3434910 in _transient_aiowps_captcha_string_info_9xrpb3y990
    [2020-04-01 21:15:07] - FAILURE : Writing table row: 3434911 in _transient_timeout_aiowps_captcha_string_info_a6c2be76ou
    [2020-04-01 21:15:07] - FAILURE : Writing table row: 3434912 in _transient_aiowps_captcha_string_info_a6c2be76ou
    

    I wanted to see if I could backup my site at all, which I ran the WP CLI

    
    wp db export ../my_wordpress_db.sql 
    

    which it exported my database properly.
    Going to turn off automatic backup’s through AIOWPS and schedule backups with WP CLI and Cron.

    • This reply was modified 4 years, 7 months ago by jdwf0658.
    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi,

    Going to turn off automatic backup’s through AIOWPS and schedule backups with WP CLI and Cron.

    Looks like our plugins automatic backup does not work in your site. Have you tried testing a manual backup?

    Thank you

    Thread Starter jdwf0658

    (@jdwf0658)

    Yea, manually through AIOWPS resulted in same errors. it creates the file, and fills a portion before it reaches a memory limit. I’m not sure what the difference is. I don’t mind setting it up through cron, I have it checking for file changes and cleaning up transients still.

    Thanks!

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, your server might be reaching a max execution time limit. Check to make sure your server max_excution_time setting has plenty of time to execute this action.

    Kind regards

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘aiowps_hourly_cron_event fatal error when running.’ is closed to new replies.