UpdraftPlus Home › Forums › Paid support forum – UpdraftPlus backup plugin › Intermittent failures seemingly due to timeout issues
- This topic has 4 replies, 3 voices, and was last updated 7 months ago by Vanessa.
-
AuthorPosts
-
May 14, 2024 at 3:24 pm #2130459Ryan SchulzParticipant
Hello, I am having intermittent failure issues due to timeout errors. We tried troubleshooting with our hosting provider and they recommended reaching out for support:
”
The cron failed because the request in question took over > 60 seconds to complete and our max execution time is 60 seconds.From what I understand, other backups have been taken fine but some don’t work, Am I right?
I can also see a little spike in the CPU during that request but nothing prior or after the request, that would indicate the server isn’t the cause of the slowness. If the process was too slow to run at the time and caused it to fail, this would indicate a possible slowness in the plugin process either caused by the request itself or conflict with other plugins or themes.
My recommendation would be to reach out to Updraft for further advise on how to optimize this process and for further troubleshooting steps.
”Here are the logs from the server and from the plugin:
UPDRAFT LOGS:
4942.984 (8) File exists (/nas/content/live/redacted/wp-content/updraft/backup_2024-05-12-0005_redacted_4046d68bf47f-plugins.zip.tmp), but was not modified within the last 30 seconds, so we assume that any previous run has now terminated (time_mod=1715490726, time_now=1715495247, diff=4521)
4943.022 (8) Terminate: backup_2024-05-12-0005_redacted_4046d68bf47f-plugins.zip.tmp.d0dny4 exists with activity within the last 30 seconds (time_mod=2790522880, time_now=1715495247, diff=-1075027633, size=0KB). This likely means that another UpdraftPlus run is at work; so we will exit.
4943.044 (8) Rescheduling resumption 9: moving to 420 seconds from now (1715495667)
4943.077 (8) To decrease the likelihood of overlaps, increasing resumption interval to: 300 + 120 = 420
5398.988 (9) Opened log file at time: Sun, 12 May 2024 06:35:03 +0000 on https://redacted
5399.003 (9) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 2.24.2.26 WP: 5.9.9 PHP: 8.2.14 (apache2handler, Linux web-96419-i-0f699cd82fb82cfdb:apache2_82:v0.3.5 5.4.0-1083-aws #90~18.04.1-Ubuntu SMP Fri Aug 5 08:12:44 UTC 2022 x86_64) MySQL: 8.0.35 (max packet size=16777216) WPLANG: en_US Server: Apache safe_mode: 0 max_execution_time: 900 memory_limit: 512M (used: 10.8M | 12M) multisite: N openssl: OpenSSL 3.0.2 15 Mar 2022 mcrypt: N LANG: C ZipArchive::addFile: Y
5399.013 (9) Free space on disk containing Updraft’s temporary directory: Unknown
5399.025 (9) Requesting backup semaphore lock (4046d68bf47f)
5399.044 (9) [Info] Lock (updraft_lock_4046d68bf47f, wp_options) acquired
5399.063 (9) Backup run: resumption=9, nonce=4046d68bf47f, file_nonce=4046d68bf47f begun at=1715490304 (5399s ago), job type=backup, previous check-in=0.31s
5399.082 (9) The current run is resumption number 9, and there was nothing useful done on the last run (last useful run: 1) – will not schedule a further attempt until we see something useful happening this time
5399.100 (9) Scheduling a resumption (10) after 420 seconds (1715496123); but the job will then be aborted unless something happens this time
5399.120 (9) Creation of backups of directories: had begun; will resume
5399.185 (9) Beginning creation of dump of plugins (split every: 100 MB)
5399.215 (9) File exists (/nas/content/live/redacted/wp-content/updraft/backup_2024-05-12-0005_redacted_4046d68bf47f-plugins.zip.tmp), but was not modified within the last 30 seconds, so we assume that any previous run has now terminated (time_mod=1715490726, time_now=1715495703, diff=4977)
5399.236 (9) Terminate: backup_2024-05-12-0005_redacted_4046d68bf47f-plugins.zip.tmp.d0dny4 exists with activity within the last 30 seconds (time_mod=2790522880, time_now=1715495703, diff=-1075027177, size=0KB). This likely means that another UpdraftPlus run is at work; so we will exit.
5399.255 (9) Rescheduling resumption 10: moving to 540 seconds from now (1715496243)
5399.288 (9) To decrease the likelihood of overlaps, increasing resumption interval to: 420 + 120 = 540
5939.040 (10) Opened log file at time: Sun, 12 May 2024 06:44:03 +0000 on https://redacted
5939.051 (10) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 2.24.2.26 WP: 5.9.9 PHP: 8.2.14 (apache2handler, Linux web-96419-i-0587e057dcce82b37:apache2_82:v0.3.5 5.4.0-1107-aws #115~18.04.1-Ubuntu SMP Wed Jul 19 19:15:11 UTC 2023 x86_64) MySQL: 8.0.35 (max packet size=16777216) WPLANG: en_US Server: Apache safe_mode: 0 max_execution_time: 900 memory_limit: 512M (used: 11.1M | 14M) multisite: N openssl: OpenSSL 3.0.2 15 Mar 2022 mcrypt: N LANG: C ZipArchive::addFile: Y
5939.067 (10) Free space on disk containing Updraft’s temporary directory: Unknown
5939.077 (10) Requesting backup semaphore lock (4046d68bf47f)
5939.099 (10) [Info] Lock (updraft_lock_4046d68bf47f, wp_options) acquired
5939.128 (10) Backup run: resumption=10, nonce=4046d68bf47f, file_nonce=4046d68bf47f begun at=1715490304 (5939s ago), job type=backup, previous check-in=0.24s
5939.158 (10) [Updraftplus] The backup is being aborted for a repeated failure to progress.
5939.167 (10) An error condition has occurred for the first time during this job
5939.185 (10) [Info] Lock option (updraft_lock_4046d68bf47f, wp_options) released
5939.204 (10) An email has been scheduled for this job, because we are in debug mode
5939.238 (10) Sending email (‘Incomplete’) report (attachments: 1, size: 31.8 KB) to: WPEng…SERVER PROVIDER LOGS:
52.252.48.204 redacted.com – [08/May/2024:06:29:06 +0000] “GET /wp-cron.php?doing_wp_cron HTTP/1.0” 502 1175 “-” “Mozilla/5.0 (Windows NT; Windows NT 10.0; en-US) WindowsPowerShell/5.1.17763.5696”
May 14, 2024 at 3:24 pm #2130460Ryan SchulzParticipantThis reply has been marked as moderator-only.May 15, 2024 at 5:20 pm #2131460Paul BevanKeymasterHello,
Thank you for your message. Would it be possible to share the full log files via pastebin.com please?
Best,
Paul
May 15, 2024 at 7:11 pm #2131544Ryan SchulzParticipantThis reply has been marked as private.May 16, 2024 at 6:55 pm #2132520VanessaModeratorHi,
60 is an insanely low max execution time, can you try increasing it by adding the following to your wp-config.php
set_time_limit(300);
Reducing your archive split right down to 25 might also help (I can see that you have already reduced it to 100)
-
AuthorPosts
- The topic ‘Intermittent failures seemingly due to timeout issues’ is closed to new replies.