Boldgrid Backup Failure with Hostinger

  • Resolved gmarsh666

    (@gmarsh666)


    4 months, 3 weeks ago

    I am trying to get clarity on how to resolve the problems I am having since I migrated to Hostinger – I can perform simple backups with few files but when I try to backup my wordpress site it fails during the write phase. I have checked the memory and diskspace and even timing settings with PHP but can’t find anything. Long running Processes have up to six minutes to complete and as you can see by the log the amount of memory used is well within the limits. My assumption is that Hostinger is killing the backup because it stops during the write phase but I am at a loss as to which setting is causing the problem.

    I can do backups with another service but it takes much longer what I am used to with Boldgrid.

    Comments are appreciated and I will post results of suggested changes.

    I have supplied my log file below with personal identifiers edited. *** * have also deleted some of the wp tables from the output below…. they were listed though.

    [2024-10-10 01:22:01 UTC] PHP Version: 8.2.21 [2024-10-10 01:22:01 UTC] WordPress Version: 6.6.2 [2024-10-10 01:22:01 UTC] Total Upkeep version: 1.16.5 [2024-10-10 01:22:01 UTC] getpgid support: Available [2024-10-10 01:22:01 UTC] Backup process initialized. [2024-10-10 01:22:01 UTC] Backup process initialized. [2024-10-10 01:22:01 UTC] Process id: 1436374 [2024-10-10 01:22:01 UTC] Backup triggered by: ) [2024-10-10 01:22:01 UTC] ——————————————————————————– [2024-10-10 01:22:01 UTC] Starting dump of database… [2024-10-10 01:22:01 UTC] Memory usage – limit / current / peak memory usage: 1536M / 17685968 (16.87 MB) / 63771528 (61 MB) [2024-10-10 01:22:01 UTC] Database info: Array ( [wp_actionscheduler_actions] => 44 [wp_actionscheduler_claims] => 0 [wp_actionscheduler_groups] => 7 [wp_actionscheduler_logs] => 127 [wp_check_email_log] => 0 [wp_commentmeta] => 200 [wp_comments] => 40 [wp_connections] => 2

    **** Deleted tables

    => 3 [wp_wpforms_tasks_meta] => 5 [wp_wr_contactform_fields] => 0 [wp_wr_contactform_form_pages] => 0 [wp_wr_contactform_submission_data] => 0 [wp_yoast_indexable] => 170 [wp_yoast_indexable_hierarchy] => 168 [wp_yoast_migrations] => 24 [wp_yoast_primary_term] => 0 [wp_yoast_seo_links] => 336 ) [2024-10-10 01:22:04 UTC] Dump of database complete! $status = 1 [2024-10-10 01:22:04 UTC] Memory usage – limit / current / peak memory usage: 1536M / 17689984 (16.87 MB) / 63771528 (61 MB)

    [2024-10-10 01:22:04 UTC] ——————————————————————————– [2024-10-10 01:22:04 UTC] Retrieving file list. [2024-10-10 01:22:09 UTC] Retrieving backup directory. [2024-10-10 01:22:09 UTC] Adding Database to file list.

    [2024-10-10 01:22:09 UTC] Database dump file added to file list: /home/u650227164/boldgrid_backup/u650227164_Y3FBG.20241010-012201.sql / 40062650 (38.21 MB)

    [2024-10-10 01:22:09 UTC] Starting archiving of files. Chosen compressor: php_zip

    [2024-10-10 01:22:09 UTC] Memory usage – limit / current / peak memory usage: 1536M / 40198392 (38.34 MB) / 63771528 (61 MB)

    [2024-10-10 01:22:10 UTC] ——————————————————————————– [2024-10-10 01:22:10 UTC] Starting to analyze filelist…

    [2024-10-10 01:22:10 UTC] Memory usage – limit / current / peak memory usage: 1536M / 40202632 (38.34 MB) / 63771528 (61 MB)

    [2024-10-10 01:22:10 UTC] Finished analyzing filelist!

    [2024-10-10 01:22:10 UTC] Memory usage – limit / current / peak memory usage: 1536M / 41255504 (39.34 MB) / 63771528 (61 MB) [2024-10-10 01:22:14 UTC] Backup process running: Yes (pgid = 1436374) [2024-10-10 01:22:14 UTC] Total files / size archived: 44248 / 4196810867 (3.91 GB)

    [2024-10-10 01:22:15 UTC] Starting to close the zip file. [2024-10-10 01:22:15 UTC] Memory usage – limit / current / peak memory usage: 1536M / 41788208 (39.85 MB) / 63771528 (61 MB)

    [2024-10-10 01:22:19 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:22:24 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:22:29 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:22:34 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:22:39 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:22:44 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:22:51 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:22:56 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:01 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:06 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:11 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:16 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:21 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:26 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:31 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:36 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:41 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:46 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:23:51 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:24:01 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:24:01 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:24:06 UTC] Backup process running: Yes (pgid = 1436374)

    [2024-10-10 01:24:11 UTC] Backup process running: No

    Dismiss this notice.DashboardBackupsTransfersToolsSettingsPreflight CheckSupportPremium FeaturesFunctionality test status:PASS

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

  • Hi @gmarsh666 ,

    It looks like you’re experiencing issues with the backup process during the writing phase while using Total Upkeep on your WordPress site hosted on Hostinger. Based on the log and the information provided, here are some common causes and solutions to help troubleshoot and resolve the issue:1. Backup Size and File Limits

    The backup process seems to be stopping during the write phase, which could be due to Hostinger’s file or resource limits. Total Upkeep is likely trying to compress a large amount of data, and Hostinger may be limiting the size of files or the resources allowed for long-running processes.Solution: Split Backup into Smaller Chunks

    Try splitting your backup into smaller chunks by excluding certain files or folders from the backup. This can reduce the size of the archive and prevent timeout issues.

    1. Go to Total Upkeep Settings → Backup Files.
    2. Exclude unnecessary files such as caching folders, logs, or other temporary files.
    3. Run the backup again to see if it completes.

    2. PHP Timeouts or Resource Limits

    Although you’ve verified that PHP settings allow processes up to 6 minutes, it’s possible that the process is hitting a server-imposed timeout before completion.Solution: Increase PHP Execution Time & Memory Limits

    Double-check your PHP settings for:

    • max_execution_time: Set this to a higher value (e.g., 600 or more).
    • memory_limit: You’re already within limits, but increasing this further (to 2GB or more) might help if the process uses additional memory.

    If you don’t have access to edit these settings directly, contact Hostinger support to increase the limits temporarily for the backup process. Some shared hosting providers (like Hostinger) apply resource throttling on long-running processes to prevent overuse. This could explain why the process stops after running for a while. Reach out to Hostinger and ask if there are any resource limits (CPU, memory, or IO) being applied that could be affecting the backup process. If possible, they might be able to adjust the limits or provide guidance on optimizing the process.

    I really hope this helps!

    Thread Starter gmarsh666

    (@gmarsh666)

    Thank you @brandonco for your very prompt and detailed reply. I will try to increase the limits as you suggested even though in theory I am within the limits (2G ram etc).
    If I find anything useful I will post it here. Cheers

    You’re very welcome @gmarsh666, even though you mentioned PHP is set for long-running processes (6 minutes), Hostinger might still have server-imposed limits. I still think the best solution would be to increase the PHP settings if possible. Try contacting Hostinger support to confirm or temporarily adjust server resource limits for the backup process.

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